20240531在飞凌的OK3588-C开发板上跑原厂的Buildroot测试ETH0接口【仅供参考】

20240531在飞凌的OK3588-C开发板上跑原厂的Buildroot测试ETH0接口
2024/5/31 20:28


root@rk3588-buildroot:/# ifconfig eth0 up
root@rk3588-buildroot:/# ifconfig eth1 up
root@rk3588-buildroot:/# ifconfig
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig eth1 192.168.3.232
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig
root@rk3588-buildroot:/# ping 192.168.3.85
rootroot@rootroot-ThinkBook-16-G5-IRH:~$ ping 192.168.3.232


由于ETH0/ETH1在莫名其妙的情况下被烧毁了!【都发烫了】
硬件花费了老鼻子劲才将ETH0修好。ETH1不想搞!
直接搬家的IPC的DTS上的gmac0,而不是飞凌原厂的DTS。因此本文仅供参考!
【后果/神奇的是,eth0变成eth1通了,但是摄像头找不到了!^_】

虽然可以PING通,但是只有黄色灯在闪烁,绿色灯没有亮,更不用说常亮了!

Z:\RK3588_IPC_SDK\sysdrv\source\kernel\arch\arm64\boot\dts\rockchip\rk3588-nvr-demo.dtsi
Z:\repo_RK3588_Buildroot20240508\kernel\arch\arm64\boot\dts\rockchip\rk3588-evb7-v11.dtsi
&dsi1_panel {
    power-supply = <&vcc3v3_lcd_n>;

    /*
     * because in hardware, the two screens share the reset pin,
     * so reset-gpios need only in dsi1 enable and dsi0 disabled
     * case.
     */

    //reset-gpios = <&gpio0 RK_PD3 GPIO_ACTIVE_LOW>;
    //pinctrl-names = "default";
    //pinctrl-0 = <&lcd_rst_gpio>;
};

&gmac0 {
    /* Use rgmii-rxid mode to disable rx delay inside Soc */
    phy-mode = "rgmii-rxid";
    clock_in_out = "output";

    snps,reset-gpio = <&gpio4 RK_PB3 GPIO_ACTIVE_LOW>;
    snps,reset-active-low;
    /* Reset time is 20ms, 100ms for rtl8211f */
    snps,reset-delays-us = <0 20000 100000>;

    pinctrl-names = "default";
    pinctrl-0 = <&gmac0_miim
             &gmac0_tx_bus2
             &gmac0_rx_bus2
             &gmac0_rgmii_clk
             &gmac0_rgmii_bus>;

    tx_delay = <0x44>;
    /* rx_delay = <0x4f>; */

    phy-handle = <&rgmii_phy0>;
    status = "okay";
};

&gmac1 {
    /* Use rgmii-rxid mode to disable rx delay inside Soc */
    phy-mode = "rgmii-rxid";
    clock_in_out = "output";

    snps,reset-gpio = <&gpio3 RK_PB7 GPIO_ACTIVE_LOW>;
    snps,reset-active-low;
    /* Reset time is 20ms, 100ms for rtl8211f */
    snps,reset-delays-us = <0 20000 100000>;

    pinctrl-names = "default";
    pinctrl-0 = <&gmac1_miim
             &gmac1_tx_bus2
             &gmac1_rx_bus2
             &gmac1_rgmii_clk
             &gmac1_rgmii_bus>;

    tx_delay = <0x43>;
    /* rx_delay = <0x3f>; */

    phy-handle = <&rgmii_phy>;
    status = "okay";
};


&i2s6_8ch {
    status = "okay";
};

&i2s7_8ch {
    status = "okay";
};

&mdio0 {
    rgmii_phy0: phy@1 {
        compatible = "ethernet-phy-ieee802.3-c22";
        reg = <0x1>;
    };
};

&mdio1 {
    rgmii_phy: phy@1 {
        compatible = "ethernet-phy-ieee802.3-c22";
        reg = <0x1>;
    };
};

&mipi_dcphy0 {
    status = "okay";
};


原始LOG:
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig
lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:36 errors:0 dropped:0 overruns:0 frame:0
          TX packets:36 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2608 (2.5 KiB)  TX bytes:2608 (2.5 KiB)

root@rk3588-buildroot:/#         
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig -a
eth0      Link encap:Ethernet  HWaddr 16:B5:8E:1B:42:CB  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:88 

eth1      Link encap:Ethernet  HWaddr 12:B5:8E:1B:42:CB  
          BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)
          Interrupt:140 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:38 errors:0 dropped:0 overruns:0 frame:0
          TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:2728 (2.6 KiB)  TX bytes:2728 (2.6 KiB)

root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig eth0 up
[   34.783304] rk_gmac-dwmac fe1c0000.ethernet eth0: no phy found
ifconfig: SIOCSIFFLAGS: No such device
[   34.783342] rk_gmac-dwmac fe1c0000.ethernet eth0: stmmac_open: Cannot attach to PHY (error: -19)
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig eth1 up
[   42.914082] rk_gmac-dwmac fe1b0000.ethernet eth1: PHY [stmmac-0:01] driver [RTL8211F Gigabit Ethernet] (irq=POLL)
[   42.916074] dwmac4: Master AXI performs any burst length
[   42.916102] rk_gmac-dwmac fe1b0000.ethernet eth1: No Safety Features support found
[   42.916120] rk_gmac-dwmac fe1b0000.ethernet eth1: IEEE 1588-2008 Advanced Timestamp supported
[   42.916287] rk_gmac-dwmac fe1b0000.ethernet eth1: registered PTP clock
[   42.916649] rk_gmac-dwmac fe1b0000.ethernet eth1: configuring for phy/rgmii-rxid link mode
root@rk3588-buildroot:/# [   42.942947] rk_gmac-dwmac fe1b0000.ethernet eth1: Link is Up - 1Gbps/Full - flow control rx/tx
[   42.942978] IPv6: ADDRCONF(NETDEV_CHANGE): eth1: link becomes ready

root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig
eth1      Link encap:Ethernet  HWaddr 12:B5:8E:1B:42:CB  
          inet6 addr: fe80::10b5:8eff:fe1b:42cb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:56 errors:0 dropped:0 overruns:0 frame:0
          TX packets:7 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:7871 (7.6 KiB)  TX bytes:586 (586.0 B)
          Interrupt:140 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:50 errors:0 dropped:0 overruns:0 frame:0
          TX packets:50 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:3448 (3.3 KiB)  TX bytes:3448 (3.3 KiB)

root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig eth1 192.168.3.232
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ifconfig
eth1      Link encap:Ethernet  HWaddr 12:B5:8E:1B:42:CB  
          inet addr:192.168.3.232  Bcast:192.168.3.255  Mask:255.255.255.0
          inet6 addr: fe80::10b5:8eff:fe1b:42cb/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:533 errors:0 dropped:0 overruns:0 frame:0
          TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:79525 (77.6 KiB)  TX bytes:1328 (1.2 KiB)
          Interrupt:140 

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:65536  Metric:1
          RX packets:86 errors:0 dropped:0 overruns:0 frame:0
          TX packets:86 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:5608 (5.4 KiB)  TX bytes:5608 (5.4 KiB)

root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# ping 192.168.3.85
PING 192.168.3.85 (192.168.3.85) 56(84) bytes of data.
64 bytes from 192.168.3.85: icmp_seq=1 ttl=64 time=0.514 ms
64 bytes from 192.168.3.85: icmp_seq=2 ttl=64 time=0.457 ms
64 bytes from 192.168.3.85: icmp_seq=3 ttl=64 time=0.451 ms
64 bytes from 192.168.3.85: icmp_seq=4 ttl=64 time=0.450 ms
64 bytes from 192.168.3.85: icmp_seq=5 ttl=64 time=0.423 ms
64 bytes from 192.168.3.85: icmp_seq=6 ttl=64 time=0.411 ms
64 bytes from 192.168.3.85: icmp_seq=7 ttl=64 time=0.451 ms
64 bytes from 192.168.3.85: icmp_seq=8 ttl=64 time=0.413 ms
64 bytes from 192.168.3.85: icmp_seq=9 ttl=64 time=0.541 ms
64 bytes from 192.168.3.85: icmp_seq=10 ttl=64 time=0.430 ms
64 bytes from 192.168.3.85: icmp_seq=11 ttl=64 time=0.412 ms
64 bytes from 192.168.3.85: icmp_seq=12 ttl=64 time=0.436 ms
64 bytes from 192.168.3.85: icmp_seq=13 ttl=64 time=0.415 ms
64 bytes from 192.168.3.85: icmp_seq=14 ttl=64 time=0.426 ms
64 bytes from 192.168.3.85: icmp_seq=15 ttl=64 time=0.455 ms
64 bytes from 192.168.3.85: icmp_seq=16 ttl=64 time=0.458 ms
64 bytes from 192.168.3.85: icmp_seq=17 ttl=64 time=0.429 ms
64 bytes from 192.168.3.85: icmp_seq=18 ttl=64 time=0.429 ms
64 bytes from 192.168.3.85: icmp_seq=19 ttl=64 time=0.542 ms
64 bytes from 192.168.3.85: icmp_seq=20 ttl=64 time=0.453 ms
64 bytes from 192.168.3.85: icmp_seq=21 ttl=64 time=0.460 ms
64 bytes from 192.168.3.85: icmp_seq=22 ttl=64 time=0.474 ms
64 bytes from 192.168.3.85: icmp_seq=23 ttl=64 time=0.469 ms
64 bytes from 192.168.3.85: icmp_seq=24 ttl=64 time=0.459 ms
64 bytes from 192.168.3.85: icmp_seq=25 ttl=64 time=0.460 ms
64 bytes from 192.168.3.85: icmp_seq=26 ttl=64 time=0.445 ms
64 bytes from 192.168.3.85: icmp_seq=27 ttl=64 time=0.456 ms
64 bytes from 192.168.3.85: icmp_seq=28 ttl=64 time=0.451 ms
64 bytes from 192.168.3.85: icmp_seq=29 ttl=64 time=0.444 ms
64 bytes from 192.168.3.85: icmp_seq=30 ttl=64 time=0.539 ms
64 bytes from 192.168.3.85: icmp_seq=31 ttl=64 time=0.452 ms
64 bytes from 192.168.3.85: icmp_seq=32 ttl=64 time=0.504 ms
64 bytes from 192.168.3.85: icmp_seq=33 ttl=64 time=0.461 ms
64 bytes from 192.168.3.85: icmp_seq=34 ttl=64 time=0.533 ms
64 bytes from 192.168.3.85: icmp_seq=35 ttl=64 time=0.417 ms
64 bytes from 192.168.3.85: icmp_seq=36 ttl=64 time=0.521 ms
64 bytes from 192.168.3.85: icmp_seq=37 ttl=64 time=0.455 ms
64 bytes from 192.168.3.85: icmp_seq=38 ttl=64 time=0.241 ms
64 bytes from 192.168.3.85: icmp_seq=39 ttl=64 time=0.427 ms
64 bytes from 192.168.3.85: icmp_seq=40 ttl=64 time=0.540 ms
64 bytes from 192.168.3.85: icmp_seq=41 ttl=64 time=0.530 ms
64 bytes from 192.168.3.85: icmp_seq=42 ttl=64 time=0.542 ms
64 bytes from 192.168.3.85: icmp_seq=43 ttl=64 time=0.441 ms
64 bytes from 192.168.3.85: icmp_seq=44 ttl=64 time=0.468 ms
64 bytes from 192.168.3.85: icmp_seq=45 ttl=64 time=0.413 ms
64 bytes from 192.168.3.85: icmp_seq=46 ttl=64 time=0.443 ms
64 bytes from 192.168.3.85: icmp_seq=47 ttl=64 time=0.557 ms
64 bytes from 192.168.3.85: icmp_seq=48 ttl=64 time=0.425 ms
64 bytes from 192.168.3.85: icmp_seq=49 ttl=64 time=0.435 ms
64 bytes from 192.168.3.85: icmp_seq=50 ttl=64 time=0.425 ms
64 bytes from 192.168.3.85: icmp_seq=51 ttl=64 time=0.423 ms
64 bytes from 192.168.3.85: icmp_seq=52 ttl=64 time=0.427 ms
64 bytes from 192.168.3.85: icmp_seq=53 ttl=64 time=0.423 ms
64 bytes from 192.168.3.85: icmp_seq=54 ttl=64 time=0.430 ms
64 bytes from 192.168.3.85: icmp_seq=55 ttl=64 time=0.430 ms
64 bytes from 192.168.3.85: icmp_seq=56 ttl=64 time=0.449 ms
64 bytes from 192.168.3.85: icmp_seq=57 ttl=64 time=0.429 ms
64 bytes from 192.168.3.85: icmp_seq=58 ttl=64 time=0.444 ms
64 bytes from 192.168.3.85: icmp_seq=59 ttl=64 time=0.428 ms
64 bytes from 192.168.3.85: icmp_seq=60 ttl=64 time=0.440 ms
64 bytes from 192.168.3.85: icmp_seq=61 ttl=64 time=0.535 ms
64 bytes from 192.168.3.85: icmp_seq=62 ttl=64 time=0.412 ms
64 bytes from 192.168.3.85: icmp_seq=63 ttl=64 time=0.440 ms
64 bytes from 192.168.3.85: icmp_seq=64 ttl=64 time=0.540 ms
64 bytes from 192.168.3.85: icmp_seq=65 ttl=64 time=0.450 ms
64 bytes from 192.168.3.85: icmp_seq=66 ttl=64 time=0.532 ms
64 bytes from 192.168.3.85: icmp_seq=67 ttl=64 time=0.414 ms
64 bytes from 192.168.3.85: icmp_seq=68 ttl=64 time=0.519 ms
64 bytes from 192.168.3.85: icmp_seq=69 ttl=64 time=0.434 ms
64 bytes from 192.168.3.85: icmp_seq=70 ttl=64 time=0.531 ms
64 bytes from 192.168.3.85: icmp_seq=71 ttl=64 time=0.427 ms
64 bytes from 192.168.3.85: icmp_seq=72 ttl=64 time=0.414 ms
64 bytes from 192.168.3.85: icmp_seq=73 ttl=64 time=0.521 ms
64 bytes from 192.168.3.85: icmp_seq=74 ttl=64 time=0.436 ms
64 bytes from 192.168.3.85: icmp_seq=75 ttl=64 time=0.535 ms
64 bytes from 192.168.3.85: icmp_seq=76 ttl=64 time=0.530 ms
64 bytes from 192.168.3.85: icmp_seq=77 ttl=64 time=0.393 ms
64 bytes from 192.168.3.85: icmp_seq=78 ttl=64 time=0.408 ms
64 bytes from 192.168.3.85: icmp_seq=79 ttl=64 time=0.404 ms
64 bytes from 192.168.3.85: icmp_seq=80 ttl=64 time=0.425 ms
64 bytes from 192.168.3.85: icmp_seq=81 ttl=64 time=0.404 ms
64 bytes from 192.168.3.85: icmp_seq=82 ttl=64 time=0.437 ms
64 bytes from 192.168.3.85: icmp_seq=83 ttl=64 time=0.413 ms
64 bytes from 192.168.3.85: icmp_seq=84 ttl=64 time=0.426 ms
64 bytes from 192.168.3.85: icmp_seq=85 ttl=64 time=0.426 ms
64 bytes from 192.168.3.85: icmp_seq=86 ttl=64 time=0.436 ms
64 bytes from 192.168.3.85: icmp_seq=87 ttl=64 time=0.442 ms
64 bytes from 192.168.3.85: icmp_seq=88 ttl=64 time=0.409 ms
64 bytes from 192.168.3.85: icmp_seq=89 ttl=64 time=0.427 ms
64 bytes from 192.168.3.85: icmp_seq=90 ttl=64 time=0.456 ms
64 bytes from 192.168.3.85: icmp_seq=91 ttl=64 time=0.458 ms
64 bytes from 192.168.3.85: icmp_seq=92 ttl=64 time=0.436 ms
64 bytes from 192.168.3.85: icmp_seq=93 ttl=64 time=0.434 ms
^C
--- 192.168.3.85 ping statistics ---
93 packets transmitted, 93 received, 0% packet loss, time 93222ms
rtt min/avg/max/mdev = 0.241/0.452/0.557/0.047 ms
root@rk3588-buildroot:/# 
root@rk3588-buildroot:/# 


viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ ping 192.168.3.232
PING 192.168.3.232 (192.168.3.232) 56(84) bytes of data.
64 bytes from 192.168.3.232: icmp_seq=1 ttl=64 time=0.421 ms
64 bytes from 192.168.3.232: icmp_seq=2 ttl=64 time=0.400 ms
64 bytes from 192.168.3.232: icmp_seq=3 ttl=64 time=0.407 ms
64 bytes from 192.168.3.232: icmp_seq=4 ttl=64 time=0.411 ms
64 bytes from 192.168.3.232: icmp_seq=5 ttl=64 time=0.424 ms
64 bytes from 192.168.3.232: icmp_seq=6 ttl=64 time=0.409 ms
64 bytes from 192.168.3.232: icmp_seq=7 ttl=64 time=0.489 ms
64 bytes from 192.168.3.232: icmp_seq=8 ttl=64 time=0.418 ms
64 bytes from 192.168.3.232: icmp_seq=9 ttl=64 time=0.409 ms
64 bytes from 192.168.3.232: icmp_seq=10 ttl=64 time=0.408 ms
64 bytes from 192.168.3.232: icmp_seq=11 ttl=64 time=0.408 ms
64 bytes from 192.168.3.232: icmp_seq=12 ttl=64 time=0.408 ms
64 bytes from 192.168.3.232: icmp_seq=13 ttl=64 time=0.418 ms
64 bytes from 192.168.3.232: icmp_seq=14 ttl=64 time=0.405 ms
64 bytes from 192.168.3.232: icmp_seq=15 ttl=64 time=0.410 ms
64 bytes from 192.168.3.232: icmp_seq=16 ttl=64 time=0.407 ms
64 bytes from 192.168.3.232: icmp_seq=17 ttl=64 time=0.409 ms
64 bytes from 192.168.3.232: icmp_seq=18 ttl=64 time=0.411 ms
64 bytes from 192.168.3.232: icmp_seq=19 ttl=64 time=0.490 ms
64 bytes from 192.168.3.232: icmp_seq=20 ttl=64 time=0.413 ms
64 bytes from 192.168.3.232: icmp_seq=21 ttl=64 time=0.408 ms
64 bytes from 192.168.3.232: icmp_seq=22 ttl=64 time=0.421 ms
64 bytes from 192.168.3.232: icmp_seq=23 ttl=64 time=0.414 ms
64 bytes from 192.168.3.232: icmp_seq=24 ttl=64 time=0.405 ms
64 bytes from 192.168.3.232: icmp_seq=25 ttl=64 time=0.398 ms
64 bytes from 192.168.3.232: icmp_seq=26 ttl=64 time=0.410 ms
64 bytes from 192.168.3.232: icmp_seq=27 ttl=64 time=0.400 ms
64 bytes from 192.168.3.232: icmp_seq=28 ttl=64 time=0.424 ms
64 bytes from 192.168.3.232: icmp_seq=29 ttl=64 time=0.408 ms
64 bytes from 192.168.3.232: icmp_seq=30 ttl=64 time=0.413 ms
64 bytes from 192.168.3.232: icmp_seq=31 ttl=64 time=0.421 ms
64 bytes from 192.168.3.232: icmp_seq=32 ttl=64 time=0.410 ms
64 bytes from 192.168.3.232: icmp_seq=33 ttl=64 time=0.498 ms
64 bytes from 192.168.3.232: icmp_seq=34 ttl=64 time=0.420 ms
64 bytes from 192.168.3.232: icmp_seq=35 ttl=64 time=0.505 ms
64 bytes from 192.168.3.232: icmp_seq=36 ttl=64 time=0.452 ms
64 bytes from 192.168.3.232: icmp_seq=37 ttl=64 time=0.435 ms
64 bytes from 192.168.3.232: icmp_seq=38 ttl=64 time=0.408 ms
64 bytes from 192.168.3.232: icmp_seq=39 ttl=64 time=0.393 ms
64 bytes from 192.168.3.232: icmp_seq=40 ttl=64 time=0.391 ms
64 bytes from 192.168.3.232: icmp_seq=41 ttl=64 time=0.403 ms
64 bytes from 192.168.3.232: icmp_seq=42 ttl=64 time=0.409 ms
64 bytes from 192.168.3.232: icmp_seq=43 ttl=64 time=0.413 ms
64 bytes from 192.168.3.232: icmp_seq=44 ttl=64 time=0.401 ms
64 bytes from 192.168.3.232: icmp_seq=45 ttl=64 time=0.412 ms
64 bytes from 192.168.3.232: icmp_seq=46 ttl=64 time=0.441 ms
64 bytes from 192.168.3.232: icmp_seq=47 ttl=64 time=0.410 ms
64 bytes from 192.168.3.232: icmp_seq=48 ttl=64 time=0.400 ms
^C
--- 192.168.3.232 ping statistics ---
48 packets transmitted, 48 received, 0% packet loss, time 48139ms
rtt min/avg/max/mdev = 0.391/0.418/0.505/0.025 ms
viewpro@viewpro-ThinkBook-16-G5-IRH:~$ 

本文来自互联网用户投稿,该文观点仅代表作者本人,不代表本站立场。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如若转载,请注明出处:http://www.rhkb.cn/news/337278.html

如若内容造成侵权/违法违规/事实不符,请联系长河编程网进行投诉反馈email:809451989@qq.com,一经查实,立即删除!

相关文章

Postgresql源码(134)优化器针对volatile函数的排序优化分析

相关 《Postgresql源码&#xff08;133&#xff09;优化器动态规划生成连接路径的实例分析》 上一篇对路径的生成进行了分析&#xff0c;通过make_one_rel最终拿到了一个带着路径的RelOptInfo。本篇针对带volatile函数的排序场景继续分析subquery_planner的后续流程。 subquer…

使用 Vue 3 和 vue-print-nb 插件实现复杂申请表的打印

文章目录 1&#xff1a;创建 Vue 3 项目2&#xff1a;安装 vue-print-nb 插件3&#xff1a;配置 vue-print-nb 插件4&#xff1a;创建一个复杂的申请表5&#xff1a;使用 ApplicationForm 组件6&#xff1a;运行项目 在开发管理系统或申请表打印功能时&#xff0c;打印功能是一…

EG2106 原装正品 贴片SOP-8 大功率MOS管栅极驱动芯片耐压600V

EG2106 在电机控制中的应用非常广泛&#xff0c;下面是一些典型的应用案例&#xff1a; 1. 无刷直流电机&#xff08;BLDC&#xff09;控制&#xff1a;EG2106 可以用于驱动无刷直流电机的功率MOSFET或IGBT。在无刷电机控制器中&#xff0c;通常会用到H桥电路来控制电机的正…

云端数据提取:安全、高效地利用无限资源

在当今的大数据时代&#xff0c;企业和组织越来越依赖于云平台存储和处理海量数据。然而&#xff0c;随着数据的指数级增长&#xff0c;数据的安全性和高效的数据处理成为了企业最为关心的议题之一。本文将探讨云端数据安全的重要性&#xff0c;并提出一套既高效又安全的数据提…

【农村电商1004】 电子商务进农村示范县名单:全面数据集等你探索!

今天给大家分享的发表在国内顶级期刊金融研究的2023年论文《农村发展电子商务能减缓资本与劳动力要素外流吗&#xff1f;——以电子商务进农村综合示范案例为例》使用到的重要数据集电子商务进农村综合示范政策县数据&#xff0c;该论文采用了双重差分法和全国县域面板数据研究…

CSS--学习

CSS 1简介 1.1定义 层叠样式表 (Cascading Style Sheets&#xff0c;缩写为 CSS&#xff09;&#xff0c;是一种 样式表 语言&#xff0c;用来描述 HTML 文档的呈现&#xff08;美化内容&#xff09;。 1.2 特性 继承性 子级默认继承父级的文字控制属性。层叠性 相同的属性…

计算机视觉与模式识别实验1-1 图像的直方图平衡

文章目录 &#x1f9e1;&#x1f9e1;实验流程&#x1f9e1;&#x1f9e1;1.读入图像‘rice.png’&#xff0c;在一个窗口中显示灰度级n64&#xff0c;128和256的图像直方图。2.调解图像灰度范围&#xff0c;观察变换后的图像及其直方图的变化。3.分别对图像‘pout.tif’和‘ti…

Android加固多渠道打包和签名工具

简介 基于腾讯VasDolly最新版本3.0.6的图形界面衍生版本&#xff0c;同时增加了签名功能&#xff0c;旨在更好的帮助开发者构建多渠道包 使用说明 下载并解压最新工具包&#xff0c;找到Startup脚本并双击启动图形界面&#xff08;注意&#xff1a;需本地安装java环境&#…

【Python爬虫--scrapy+selenium框架】超详细的Python爬虫scrapy+selenium框架学习笔记(保姆级别的,非常详细)

六&#xff0c;selenium 想要下载PDF或者md格式的笔记请点击以下链接获取 python爬虫学习笔记点击我获取 Scrapyselenium详细学习笔记点我获取 Python超详细的学习笔记共21万字点我获取 1&#xff0c;下载配置 ## 安装&#xff1a; pip install selenium## 它与其他库不同…

vmware esxi虚拟化数据迁移

1、启用esxi的ssh 登录esxi的web界面&#xff0c;选择主机-》操作——》服务——》启动ssh 2.xshell登录esxi 3、找到虚拟机所在目录 blog.csdnimg.cn/direct/d57372536a4145f2bcc1189d02cc7da8.png)#### 3在传输数据前需关闭防火墙服务 查看防火墙状态&#xff1a;esxcli …

使用el-tab,el-tab-pane循环使用循环后不显示下划线问题

在vue项目中使用element-UI el-tab里的el-tab-pane是循环出来的&#xff0c;但是循环出来后选中tab不显示下划线了 文章目录 问题问题展示效果问题代码问题原因 解决方案解决后效果解决方案1代码 解决方案2代码 问题 问题展示效果 问题代码 <el-tabs v-model"activeNa…

java.lang.NoClassDefFoundError: org/dom4j/io/SAXReader

问题描述&#xff1a;在maven项目中&#xff0c;给SAXReader创建实例&#xff0c;启动tomcat服务器后报异常java.lang.NoClassDefFoundError: org/dom4j/io/SAXReader。我在pom文件中是引入了dom4j依赖得&#xff0c;但是不知道为什么在上传到web时就找不到了 解决办法&#x…

Java通过Html(ftl模板)生成PDF实战, 可支持商用

Java通过Html(freemarker模板)生成PDF实战, 可支持商用 技术架构 springboot freemarker [pdfbox] flying-saucer-pdf 生成流程&#xff1a; freemarker: 根据数据填充ftl模板文件&#xff0c;得到包含有效数据的html文件&#xff08;包含页眉页脚页码的处理&#xff0c…

迁移ISE ChipScope逻辑分析器到Vivado硬件管理器

迁移ISE ChipScope逻辑分析器到Vivado硬件管理器 介绍 本章介绍AMD Vivado™Design Suite硬件管理器&#xff0c;以及这些工具之间的关系 到ISE™设计套件ChipScope™逻辑分析器工具&#xff0c;以及如何迁移IP核 从ISE ChipScope环境到Vivado Design Suite。 Vivado硬件管理器…

前端Vue小兔鲜儿电商项目实战Day05

一、登录 - 整体认识和路由配置 1. 整体认识 登录页面的主要功能就是表单校验和登录退出业务 ①src/views/Login/index.vue <script setup></script><template><div><header class"login-header"><div class"container m-…

数组的应用-24点游戏

目录 24点游戏 游戏规则 游戏主要分为三部分 电脑出牌 用户输入算式 电脑判断胜负 总结 24点游戏 游戏规则&#xff1a; 54张扑克抽出大小王&#xff0c;剩余52张用来用于游戏&#xff1b;每一轮从52张牌中随机抽出4张&#xff1b;玩家运用加&#xff0c;减&#xff0…

尝试用智谱机器人+知识库,制作pytorch测试用例生成器

尝试用智谱机器人知识库,制作pytorch测试用例生成器 1 保存pytorch算子文档到txt2 创建知识库3 创建聊天机器人4 测试效果5 分享 背景:是否能将API的接口文档和sample放到RAG知识库,让LLM编写API相关的程序呢 小结:当前的实验效果并不理想,可以生成代码,但几乎都存在BUG 1 保存…

动态分配函数参数用二级指针的作用

文章目录 前言一、案例 前言 在一些情况下&#xff0c;我们需要在函数内部动态地分配内存来存储结构体&#xff0c;并且需要在函数外部访问该结构体。在这种情况下&#xff0c;可以使用二级指针作为函数参数来实现动态内存分配&#xff0c;并且在函数外部使用指针访问结构体。…

汽车IVI中控开发入门及进阶(二十三):i.MX8

前言: IVI市场的复杂性急剧增加,而TimeToMarket在几代产品中从5年减少到2-3年。Tier1正在接近开放系统的模型(用户可以安装应用程序),从专有/关闭源代码到标准接口/开放源代码,从软件堆栈对系统体系结构/应用层/系统验证和鉴定的完全所有权,越来越依赖第三方中间件和平…

liunx文件系统与日志分析

文章目录 一、基本概念二、日志分析三、实验 一、基本概念 文件是存储在硬盘上的&#xff0c;硬盘上的最小存储单位是扇区每个扇区大小事512字节 inode&#xff1a;元信息&#xff08;文件的属性 权限 创建者 创建日期&#xff09; block&#xff1a;块 连续八个扇区组成一块…