tobetter / linux Goto Github PK
View Code? Open in Web Editor NEWThis project forked from torvalds/linux
Linux kernel source tree
License: Other
This project forked from torvalds/linux
Linux kernel source tree
License: Other
Linux kernel ============ There are several guides for kernel developers and users. These guides can be rendered in a number of formats, like HTML and PDF. Please read Documentation/admin-guide/README.rst first. In order to build the documentation, use ``make htmldocs`` or ``make pdfdocs``. The formatted documentation can also be read online at: https://www.kernel.org/doc/html/latest/ There are various text files in the Documentation/ subdirectory, several of them using the Restructured Text markup notation. Please read the Documentation/process/changes.rst file, as it contains the requirements for building and running the kernel, and information about the problems which may result by upgrading your kernel.
dmesg:
[ 0.263690] usbcore: registered new interface driver usbfs
[ 0.263775] usbcore: registered new interface driver hub
[ 0.263944] usbcore: registered new device driver usb
[ 1.238987] usbcore: registered new interface driver usb-storage
[ 1.598565] usbcore: registered new interface driver usbhid
[ 1.603651] usbhid: USB HID core driver
[ 5.968021] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 5.971402] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[ 6.021169] exynos-ohci 12120000.usb:: USB Host Controller
[ 6.032793] exynos-ohci 12120000.usb:: new USB bus registered, assigned bus number 1
[ 6.040368] exynos-ohci 12120000.usb:: irq 130, io mem 0x12120000
[ 6.101296] usb usb1: New USB device found, idVendor=1d6b, idProduct=0001
[ 6.106601] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.113830] usb usb1: Product: USB Host Controller
[ 6.118656] usb usb1: Manufacturer: Linux 4.7.2+ ohci_hcd
[ 6.123931] usb usb1: SerialNumber: 12120000.usb:
[ 6.129286] hub 1-0:1.0: USB hub found
[ 6.137242] exynos-ehci 12110000.usb:: EHCI Host Controller
[ 6.148942] exynos-ehci 12110000.usb:: new USB bus registered, assigned bus number 2
[ 6.149048] exynos-ehci 12110000.usb:: irq 130, io mem 0x12110000
[ 6.167021] exynos-ehci 12110000.usb:: USB 2.0 started, EHCI 1.00
[ 6.172277] usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
[ 6.178462] usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.178468] usb usb2: Product: EHCI Host Controller
[ 6.178474] usb usb2: Manufacturer: Linux 4.7.2+ ehci_hcd
[ 6.178480] usb usb2: SerialNumber: 12110000.usb:
[ 6.179160] hub 2-0:1.0: USB hub found
[ 6.181027] exynos-dwc3 usb3-0:: no suspend clk specified
[ 6.183925] usb_phy_generic.0.auto supply vcc not found, using dummy regulator
[ 6.184317] usb_phy_generic.1.auto supply vcc not found, using dummy regulator
[ 6.185206] exynos-dwc3 usb3-1:: no suspend clk specified
[ 6.186802] usb_phy_generic.2.auto supply vcc not found, using dummy regulator
[ 6.187207] usb_phy_generic.3.auto supply vcc not found, using dummy regulator
[ 6.211272] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 3
[ 6.211914] usb usb3: New USB device found, idVendor=1d6b, idProduct=0002
[ 6.211921] usb usb3: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.211927] usb usb3: Product: xHCI Host Controller
[ 6.211932] usb usb3: Manufacturer: Linux 4.7.2+ xhci-hcd
[ 6.211936] usb usb3: SerialNumber: xhci-hcd.4.auto
[ 6.212537] hub 3-0:1.0: USB hub found
[ 6.213275] xhci-hcd xhci-hcd.4.auto: new USB bus registered, assigned bus number 4
[ 6.213433] usb usb4: We don't know the algorithms for LPM for this host, disabling LPM.
[ 6.213748] usb usb4: New USB device found, idVendor=1d6b, idProduct=0003
[ 6.213754] usb usb4: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.213759] usb usb4: Product: xHCI Host Controller
[ 6.213763] usb usb4: Manufacturer: Linux 4.7.2+ xhci-hcd
[ 6.213767] usb usb4: SerialNumber: xhci-hcd.4.auto
[ 6.214563] hub 4-0:1.0: USB hub found
[ 6.215385] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 5
[ 6.215988] usb usb5: New USB device found, idVendor=1d6b, idProduct=0002
[ 6.215994] usb usb5: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.216001] usb usb5: Product: xHCI Host Controller
[ 6.216006] usb usb5: Manufacturer: Linux 4.7.2+ xhci-hcd
[ 6.216010] usb usb5: SerialNumber: xhci-hcd.5.auto
[ 6.216782] hub 5-0:1.0: USB hub found
[ 6.217697] xhci-hcd xhci-hcd.5.auto: new USB bus registered, assigned bus number 6
[ 6.217848] usb usb6: We don't know the algorithms for LPM for this host, disabling LPM.
[ 6.218075] usb usb6: New USB device found, idVendor=1d6b, idProduct=0003
[ 6.218081] usb usb6: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 6.218085] usb usb6: Product: xHCI Host Controller
[ 6.218090] usb usb6: Manufacturer: Linux 4.7.2+ xhci-hcd
[ 6.218095] usb usb6: SerialNumber: xhci-hcd.5.auto
[ 6.218832] hub 6-0:1.0: USB hub found
[ 6.536996] usb 3-1: new high-speed USB device number 2 using xhci-hcd
[ 6.679531] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[ 6.684753] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 6.684756] usb 3-1: Product: USB2.0 Hub
[ 6.684759] usb 3-1: Manufacturer: GenesysLogic
[ 6.693652] hub 3-1:1.0: USB hub found
[ 6.727024] usb 5-1: new high-speed USB device number 3 using xhci-hcd
[ 6.847036] usb 1-1: new full-speed USB device number 2 using exynos-ohci
[ 6.877902] usb 5-1: New USB device found, idVendor=0bda, idProduct=8153
[ 6.883117] usb 5-1: New USB device strings: Mfr=1, Product=2, SerialNumber=6
[ 6.890279] usb 5-1: Product: USB 10/100/1000 LAN
[ 6.894900] usb 5-1: Manufacturer: Realtek
[ 6.899003] usb 5-1: SerialNumber: 000001000000
[ 6.927181] usbcore: registered new interface driver r8152
[ 6.936319] usbcore: registered new interface driver cdc_ether
[ 7.066066] usb 1-1: New USB device found, idVendor=041e, idProduct=30d3
[ 7.083736] usb 5-1: reset high-speed USB device number 3 using xhci-hcd
[ 7.083746] usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=2
[ 7.083752] usb 1-1: SerialNumber: 140113000788
[ 7.117251] input: HID 041e:30d3 as /devices/platform/12120000.usb:/usb1/1-1/1-1:1.3/0003:041E:30D3.0001/input/input0
[ 7.177171] hid-generic 0003:041E:30D3.0001: input,hidraw0: USB HID v1.00 Device [HID 041e:30d3] on usb-12120000.usb:-1/input3
[ 7.346890] usbcore: registered new interface driver snd-usb-audio
[ 7.977085] usb 3-1.1: new high-speed USB device number 3 using xhci-hcd
[ 8.118821] usb 3-1.1: New USB device found, idVendor=1e68, idProduct=008a
[ 8.124230] usb 3-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 8.131602] usb 3-1.1: Product: DS picco SSD
[ 8.135760] usb 3-1.1: Manufacturer: TrekStor
[ 8.140219] usb 3-1.1: SerialNumber: 20151111311B
[ 8.163058] usbcore: registered new interface driver uas
[ 14.177117] usb 4-1: new SuperSpeed USB device number 2 using xhci-hcd
[ 14.199768] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[ 14.204984] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 14.212147] usb 4-1: Product: USB3.0 Hub
[ 14.215988] usb 4-1: Manufacturer: GenesysLogic
[ 14.230097] hub 4-1:1.0: USB hub found
[ 260.934897] usb 3-1.1: USB disconnect, device number 3
[ 270.516023] usb 4-1: USB disconnect, device number 2
[ 270.629382] usb 3-1: reset high-speed USB device number 2 using xhci-hcd
[ 271.146121] usb 4-1: new SuperSpeed USB device number 3 using xhci-hcd
[ 271.168736] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[ 271.173999] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 271.181189] usb 4-1: Product: USB3.0 Hub
[ 271.185017] usb 4-1: Manufacturer: GenesysLogic
[ 271.206155] hub 4-1:1.0: USB hub found
[ 271.486057] usb 4-1.1: new SuperSpeed USB device number 4 using xhci-hcd
[ 271.507123] usb 4-1.1: New USB device found, idVendor=1e68, idProduct=008a
[ 271.512556] usb 4-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 271.519914] usb 4-1.1: Product: DS picco SSD
[ 271.524095] usb 4-1.1: Manufacturer: TrekStor
[ 271.528459] usb 4-1.1: SerialNumber: 20151111311B
[ 271.534158] usb 4-1.1: USB controller xhci-hcd.4.auto does not support streams, which are required by the UAS driver.
[ 271.543756] usb 4-1.1: Please try an other USB controller if you wish to use UAS.
[ 271.551182] usb-storage 4-1.1:1.0: USB Mass Storage device detected
[ 271.557924] scsi host0: usb-storage 4-1.1:1.0
[ 311.669882] usb 4-1.1: USB disconnect, device number 4
[ 323.737746] usb 3-1-port1: connect-debounce failed
[ 323.742604] usb 3-1: USB disconnect, device number 2
[ 323.856536] usb 4-1: USB disconnect, device number 3
[ 324.076455] usb 3-1: new high-speed USB device number 5 using xhci-hcd
[ 324.218979] usb 3-1: New USB device found, idVendor=05e3, idProduct=0610
[ 324.224241] usb 3-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 324.231400] usb 3-1: Product: USB2.0 Hub
[ 324.235299] usb 3-1: Manufacturer: GenesysLogic
[ 324.261856] hub 3-1:1.0: USB hub found
[ 325.546471] usb 3-1.1: new high-speed USB device number 6 using xhci-hcd
[ 325.688272] usb 3-1.1: New USB device found, idVendor=1e68, idProduct=008a
[ 325.693727] usb 3-1.1: New USB device strings: Mfr=2, Product=3, SerialNumber=1
[ 325.701092] usb 3-1.1: Product: DS picco SSD
[ 325.705239] usb 3-1.1: Manufacturer: TrekStor
[ 325.709644] usb 3-1.1: SerialNumber: 20151111311B
[ 326.446648] usb 4-1: new SuperSpeed USB device number 5 using xhci-hcd
[ 326.469403] usb 4-1: New USB device found, idVendor=05e3, idProduct=0616
[ 326.474684] usb 4-1: New USB device strings: Mfr=1, Product=2, SerialNumber=0
[ 326.481815] usb 4-1: Product: USB3.0 Hub
[ 326.485668] usb 4-1: Manufacturer: GenesysLogic
[ 326.502189] hub 4-1:1.0: USB hub found
I have a SHT20 sensor connected to the GPIO interface of an N2+. How do i get GPIO I2C working on the N2+ with the 6.6 kernel?
> i2cdetect -l
i2c-0 i2c Meson I2C adapter I2C adapter
i2c-1 i2c DesignWare HDMI I2C adapter
neither of which is the GPIO I2C interface.
Do i have to load some kernel module?
> lsmod | grep i2c
i2c_mux_gpio 12288 0
i2c_gpio 16384 0
i2c_algo_bit 12288 1 i2c_gpio
Hi and thanks for all your hard work!
This patch seems faulty: https://cgit.freedesktop.org/drm/drm-misc/commit/?id=c193a003dc46ae601f46908b41d6f485b87db1ad
My screen reports YUV422 but if I have this patch on, colors are all wrong (green/purple) ; if I leave this patch out, colors are A-OK.
Thanks in advance :-) please do ask if you need additional info!
EDIT: It's worth noting I've been discussing this with Neil on IRC, and they think the patch is correct ; it's probably (as often apparently) a case of my TV firmware reporting incorrect support for YUV422, but I seem to be unable to find a way to fix it without reverting this patch...
as described here:
http://forum.odroid.com/viewtopic.php?f=95&t=15277#p116655
i'm having problems with usb attached 2,5" harddrives. the kernel reports:
Buffer I/O error on dev sda1, logical block 121667584, lost sync page write
i'm also seeing:
Nov 22 19:08:44 nixos systemd-journal[424]: Missed 219 kernel messages
Nov 22 19:08:44 nixos kernel: Emergency Thaw on mmcblk0p2
see the forum post for more information on my configuration, kernel config, u-boot version and bug-report!
thanks for the effort in porting xu4 support into kernel 4.2.0!
Hi @tobetter where is the place to post or ask for help where you are active?
I would ask which kernel starts to supports uas on odroidxu4? I see on def_conf is istill uncommented. I have usb device controller (JMicron 567) which supports scsi + uas. Thanks!
Unlike in branch odroidxu3-3.10.y the CPU stepping is not working. This means, that the thermal_core shuts down the machine, instead of throttling the frequencies to lower values. In branch odroidxu3-3.10.y this is working correctly.
My Transcend UHS-I SDXC card is not detected as UHS-I
dmesg Odroid-XU4:
[ 1.869449] mmc1: new high speed SDXC card at address 59b4
dmesg laptop:
[21388.964579] mmc0: new ultra high speed SDR104 SDHC card at address 59b4
An update installed linux-image-5.13.0-odroid-arm64:arm64 which seems to have some bugs.
Checking journalctl reveals the following (picking the red highlighted lines and their surrounding lines):
...
kvm [1]: IPA Size Limit: 40 bits
kvm [1]: vgic interrupt IRQ9
kvm: pmu event creation failed -2
kvm [1]: VHE mode initialized
...
cpu cpu0: _opp_is_duplicate: duplicate OPPs detected. Existing: freq: 15000000000, volt: 8000000, enabled: 1. New: freq: 15000000000, volt: 8800000, enabled: 1
cpu cpu0: _of_add_opp_table_v2: Feiled to add OPP, -17
cpu cpu0: OPP table can't be empty
...
dw-pcie fc00000.pcie: IRQ index 1 not found
...
meson-pcie fc000000.pcie: ivalid resouce
meson-pcie fc000000.pcie: iATU unroll: enabled
meson-pcie fc000000.pcie: Detected iATU regions: 4 outboumd, 4 inbound
meson-pcie fc000000.pcie: error: wait linkup timeout
meson-pcie fc000000.pcie: Link up
meson-pcie fc000000.pcie: PCI host bridge to bus 0000:00
...
meson8b-dwmac ff3f0000.ethernet: eth0: PHY [0.0:00] driver [RTL8211F Gigabit Ethernet] (irq=37)
meson8b-dwmac ff3f0000.ethernet: eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
meson8b-dwmac ff3f0000.ethernet: eth0: Failed to reset the dma
meson8b-dwmac ff3f0000.ethernet: eth0: stmmac_hw_setup: DMA engine initialization failed
meson8b-dwmac ff3f0000.ethernet: eth0: stmmac_open: Hw setup failed
systed-journald[1871]: Journal started
From there on comes what I would describe as the usual system stuff. The above errors are also found in dmesg
.
I will try to return to 5.11 (from which I updated) or so, since this happened on a productive system.
I build your linux-5.15.y kernel and run it successfully on odroid XU3 lite ...
Then I put the kernel on odroid hc1 with boot on sdcard, root on hdd (sata III)
=> kernel + initrd loads successfully ....
The disk is spinning up, but the console shows usb3 problems => toggle power off, then on, but before the
hdd (samsung) spins up, the toggle power off, on restarts ....
After some time the systems gives up and only ramfs with busy box ...
The same hc1 runs with kernel 5.4.* from odroid repo (Ubuntu jammy) without any problem !
odroid_hc1.log
After some tries, it starts, but there might be some timing issue to wait for the usb3 to uas controller ?
Seems that the build fails for some staging driver of a Hardkernel TFT screen. I disabled this in my config and that avoids the problem, but I guess this is something that needs a fix if somebody wants to use this TFT screen from Hardkernel with ODROIDs?
AR drivers/iio/potentiostat/built-in.a
CC [M] drivers/target/target_core_ua.o
CC [M] drivers/staging/rtl8723bs/hal/rtl8723b_dm.o
CC [M] drivers/hid/hid-prodikeys.o
CC [M] drivers/staging/fbtft/fb_upd161704.o
CC [M] drivers/staging/rtl8188eu/hal/rtl8188eu_xmit.o
CC [M] drivers/target/target_core_rd.o
AR drivers/iio/pressure/built-in.a
CC [M] drivers/bluetooth/bcm203x.o
CC [M] drivers/iio/pressure/bmp280-core.o
CC [M] drivers/hid/hid-pl.o
make[3]: *** No rule to make target 'drivers/staging/fbtft/fb_hktft35.o', needed by 'drivers/staging/fbtft/fb_hktft35.mod'. Stop.
make[3]: *** Waiting for unfinished jobs....
CC [M] drivers/staging/fbtft/fb_watterott.o
AR drivers/iio/proximity/built-in.a
CC [M] drivers/staging/rtl8188eu/hal/usb_halinit.o
CC [M] drivers/iio/proximity/ping.o
CC [M] drivers/target/target_core_stat.o
CC [M] drivers/staging/rtl8723bs/hal/rtl8723b_hal_init.o
CC [M] drivers/hid/hid-penmount.o
CC [M] drivers/iio/pressure/bmp280-regmap.o
make[2]: *** [scripts/Makefile.build:515: drivers/staging/fbtft] Error 2
make[2]: *** Waiting for unfinished jobs....
CC [M] drivers/iio/pressure/bmp280-i2c.o
CC [M] drivers/bluetooth/bpa10x.o
CC [M] drivers/target/target_core_xcopy.o
CC [M] drivers/staging/rtl8723bs/hal/rtl8723b_phycfg.o
CC [M] drivers/iio/proximity/sx9310.o
CC [M] drivers/hid/hid-petalynx.o
CC [M] drivers/target/target_core_iblock.o
CC [M] drivers/iio/pressure/bmp280-spi.o
CC [M] drivers/staging/rtl8188eu/os_dep/ioctl_linux.o
CC [M] drivers/bluetooth/bfusb.o
CC [M] drivers/bluetooth/btusb.o
CC [M] drivers/hid/hid-picolcd_core.o
CC [M] drivers/target/target_core_file.o
CC [M] drivers/iio/pressure/dlhl60d.o
CC [M] drivers/iio/proximity/vcnl3020.o
CC [M] drivers/staging/rtl8723bs/hal/rtl8723b_rf6052.o
CC [M] drivers/staging/rtl8188eu/os_dep/mlme_linux.o
CC [M] drivers/hid/hid-picolcd_fb.o
CC [M] drivers/iio/pressure/dps310.o
CC [M] drivers/target/target_core_pscsi.o
CC [M] drivers/bluetooth/btsdio.o
LD [M] drivers/target/target_core_mod.o
CC [M] drivers/staging/rtl8188eu/os_dep/mon.o
CC [M] drivers/staging/rtl8723bs/hal/rtl8723b_rxdesc.o
CC [M] drivers/staging/rtl8723bs/hal/rtl8723bs_recv.o
CC [M] drivers/iio/pressure/hid-sensor-press.o
CC [M] drivers/hid/hid-picolcd_backlight.o
CC [M] drivers/iio/pressure/icp10100.o
CC [M] drivers/bluetooth/btintel.o
CC [M] drivers/staging/rtl8723bs/hal/rtl8723bs_xmit.o
CC [M] drivers/mux/core.o
CC [M] drivers/hid/hid-picolcd_lcd.o
CC [M] drivers/most/core.o
CC [M] drivers/staging/rtl8188eu/os_dep/os_intfs.o
AR drivers/iio/resolver/built-in.a
CC [M] drivers/staging/rtl8188eu/os_dep/osdep_service.o
CC [M] drivers/bluetooth/ath3k.o
CC [M] drivers/staging/rtl8723bs/hal/sdio_halinit.o
CC [M] drivers/hid/hid-picolcd_leds.o
LD [M] drivers/iio/pressure/bmp280.o
CC [M] drivers/bluetooth/btmrvl_main.o
CC [M] drivers/mux/adg792a.o
AR drivers/iio/temperature/built-in.a
CC [M] drivers/iio/temperature/iqs620at-temp.o
CC [M] drivers/staging/rtl8723bs/hal/sdio_ops.o
CC [M] drivers/hid/hid-picolcd_cir.o
CC [M] drivers/iio/temperature/ltc2983.o
CC [M] drivers/bluetooth/btmrvl_debugfs.o
CC [M] drivers/staging/rtl8188eu/os_dep/recv_linux.o
CC [M] drivers/iio/temperature/hid-sensor-temperature.o
CC [M] drivers/staging/rtl8723bs/hal/HalBtc8723b1Ant.o
CC [M] drivers/hid/hid-picolcd_debugfs.o
CC [M] drivers/bluetooth/btmtksdio.o
CC [M] drivers/staging/rtl8188eu/os_dep/rtw_android.o
CC [M] drivers/hid/hid-plantronics.o
CC [M] drivers/staging/rtl8723bs/hal/HalBtc8723b2Ant.o
CC [M] drivers/hid/hid-playstation.o
CC [M] drivers/staging/rtl8188eu/os_dep/usb_intf.o
AR drivers/iio/test/built-in.a
CC [M] drivers/bluetooth/btbcm.o
CC [M] drivers/staging/rtl8188eu/os_dep/usb_ops_linux.o
CC [M] drivers/hid/hid-primax.o
CC [M] drivers/staging/rtl8723bs/hal/HalHWImg8723B_BB.o
AR drivers/iio/trigger/built-in.a
CC drivers/iio/industrialio-core.o
CC [M] drivers/hid/hid-retrode.o
CC [M] drivers/bluetooth/btrtl.o
CC [M] drivers/staging/rtl8188eu/os_dep/xmit_linux.o
CC [M] drivers/hid/hid-roccat.o
CC drivers/iio/industrialio-event.o
CC [M] drivers/staging/rtl8723bs/hal/HalHWImg8723B_MAC.o
LD [M] drivers/bluetooth/hci_uart.o
LD [M] drivers/bluetooth/btmrvl.o
LD [M] drivers/staging/rtl8188eu/r8188eu.o
CC [M] drivers/hid/hid-roccat-common.o
CC drivers/iio/inkern.o
CC [M] drivers/mux/adgs1408.o
CC [M] drivers/staging/rtl8723bs/hal/HalHWImg8723B_RF.o
CC drivers/iio/industrialio-buffer.o
CC [M] drivers/hid/hid-roccat-arvo.o
CC [M] drivers/mux/gpio.o
CC [M] drivers/staging/rtl8723bs/hal/HalPhyRf_8723B.o
CC drivers/iio/industrialio-trigger.o
CC [M] drivers/hid/hid-roccat-isku.o
CC [M] drivers/iio/industrialio-triggered-event.o
CC [M] drivers/staging/rtl8723bs/os_dep/ioctl_cfg80211.o
AR drivers/iio/built-in.a
CC [M] drivers/hid/hid-roccat-kone.o
CC [M] drivers/most/configfs.o
CC [M] drivers/hid/hid-roccat-koneplus.o
CC [M] drivers/hid/hid-roccat-konepure.o
CC [M] drivers/staging/rtl8723bs/os_dep/ioctl_linux.o
CC [M] drivers/staging/rtl8723bs/os_dep/mlme_linux.o
LD [M] drivers/mux/mux-core.o
CC [M] drivers/mux/mmio.o
LD [M] drivers/mux/mux-adg792a.o
CC [M] drivers/most/most_usb.o
CC [M] drivers/hid/hid-roccat-kovaplus.o
CC [M] drivers/staging/rtl8723bs/os_dep/osdep_service.o
CC [M] drivers/hid/hid-roccat-lua.o
CC [M] drivers/vhost/vhost.o
CC [M] drivers/hid/hid-roccat-pyra.o
CC [M] drivers/staging/rtl8723bs/os_dep/os_intfs.o
CC [M] drivers/staging/rtl8723bs/os_dep/recv_linux.o
CC [M] drivers/hid/hid-roccat-ryos.o
CC [M] drivers/most/most_cdev.o
CC [M] drivers/hid/hid-roccat-savu.o
CC [M] drivers/staging/rtl8723bs/os_dep/sdio_intf.o
CC [M] drivers/hid/hid-rmi.o
CC [M] drivers/staging/rtl8723bs/os_dep/sdio_ops_linux.o
CC [M] drivers/hid/hid-saitek.o
CC [M] drivers/comedi/range.o
CC [M] drivers/comedi/drivers.o
CC [M] drivers/staging/rtl8723bs/os_dep/wifi_regd.o
CC [M] drivers/hid/hid-samsung.o
CC [M] drivers/staging/rtl8723bs/os_dep/xmit_linux.o
LD [M] drivers/mux/mux-gpio.o
LD [M] drivers/mux/mux-adgs1408.o
CC [M] drivers/comedi/comedi_buf.o
CC [M] drivers/hid/hid-sjoy.o
LD [M] drivers/staging/rtl8723bs/r8723bs.o
make[1]: *** [scripts/Makefile.build:515: drivers/staging] Error 2
make[1]: *** Waiting for unfinished jobs....
CC [M] drivers/hid/hid-sony.o
CC [M] drivers/comedi/proc.o
LD [M] drivers/mux/mux-mmio.o
CC [M] drivers/vhost/iotlb.o
CC [M] drivers/hid/hid-speedlink.o
CC [M] drivers/hid/hid-steelseries.o
LD [M] drivers/vhost/vhost_scsi.o
CC [M] drivers/hid/hid-sunplus.o
LD [M] drivers/vhost/vhost_vdpa.o
CC [M] drivers/hid/hid-gaff.o
LD [M] drivers/most/most_core.o
CC [M] drivers/hid/hid-tmff.o
CC [M] drivers/hid/hid-thrustmaster.o
CC [M] drivers/hid/hid-tivo.o
CC [M] drivers/hid/hid-topseed.o
CC [M] drivers/hid/hid-twinhan.o
CC [M] drivers/hid/hid-u2fzero.o
CC [M] drivers/hid/hid-uclogic-core.o
CC [M] drivers/hid/hid-uclogic-params.o
CC [M] drivers/hid/hid-uclogic-rdesc.o
CC [M] drivers/hid/hid-udraw-ps3.o
CC [M] drivers/hid/hid-led.o
CC [M] drivers/hid/hid-xinmo.o
CC [M] drivers/hid/hid-zpff.o
CC [M] drivers/hid/hid-zydacron.o
CC [M] drivers/hid/hid-viewsonic.o
CC [M] drivers/hid/wacom_wac.o
CC [M] drivers/hid/wacom_sys.o
CC [M] drivers/hid/hid-waltop.o
CC [M] drivers/hid/hid-wiimote-core.o
CC [M] drivers/hid/hid-wiimote-modules.o
CC [M] drivers/hid/hid-wiimote-debug.o
CC [M] drivers/hid/hid-sensor-hub.o
LD [M] drivers/vhost/vhost_iotlb.o
CC [M] drivers/hid/hid-sensor-custom.o
LD [M] drivers/hid/hid-logitech.o
LD [M] drivers/hid/hid-picolcd.o
LD [M] drivers/hid/hid-uclogic.o
LD [M] drivers/hid/wacom.o
AR drivers/hid/built-in.a
LD [M] drivers/hid/hid-wiimote.o
LD [M] drivers/comedi/comedi.o
make: *** [Makefile:1847: drivers] Error 2
make: *** Waiting for unfinished jobs....
GZIP kernel/config_data.gz
CC [M] kernel/kheaders.o
CC kernel/configs.o
AR kernel/built-in.a
Thanks much for your work here. I'm testing out the odroid-5.7.y branch against xu4 and c4 right now.
Do you have a posting anywhere I can subscribe to with the current status of these branches / known issues / etc?
Setting up an lxd cluster and found out there's no bridge support. Easy to add, painful to recompile.
$ diff newconfig oldconfig
742,744c742
< CONFIG_STP=y
< CONFIG_BRIDGE=y
< CONFIG_BRIDGE_IGMP_SNOOPING=y
---
> # CONFIG_BRIDGE is not set
748d745
< CONFIG_LLC=y
I tried to build the odroid-5.12.y
branch on a musl Alpine based system (postmarketOS).
I couldn't get it working at first until I noticed that Armbian doesn't include the overlay patches:
armbian/build#2847
I reverted them and now it builds and runs fine.
Is there something missing here?
Could support for the odroid go super be added to the odroid- branches?
I think it just needs the dts brought over.
hitting the following
drivers/pwm/pwm-gpio.c:138:10: error: ‘const struct pwm_ops’ has no member named ‘config’
138 | .config = gpio_pwm_config,
| ^~~~~~
drivers/pwm/pwm-gpio.c:138:19: error: initialization of ‘int (*)(struct pwm_chip *, struct pwm_device *)’ from incompatible pointer type ‘int (*)(struct pwm_chip *, struct pwm_device *, int, int)’ [-Werror=incompatible-pointer-types]
138 | .config = gpio_pwm_config,
| ^~~~~~~~~~~~~~~
drivers/pwm/pwm-gpio.c:138:19: note: (near initialization for ‘gpio_pwm_ops.request’)
drivers/pwm/pwm-gpio.c:139:10: error: ‘const struct pwm_ops’ has no member named ‘set_polarity’
139 | .set_polarity = gpio_pwm_set_polarity,
| ^~~~~~~~~~~~
drivers/pwm/pwm-gpio.c:139:25: error: initialization of ‘void (*)(struct pwm_chip *, struct pwm_device *)’ from incompatible pointer type ‘int (*)(struct pwm_chip *, struct pwm_device *, enum pwm_polarity)’ [-Werror=incompatible-pointer-types]
139 | .set_polarity = gpio_pwm_set_polarity,
| ^~~~~~~~~~~~~~~~~~~~~
drivers/pwm/pwm-gpio.c:139:25: note: (near initialization for ‘gpio_pwm_ops.free’)
drivers/pwm/pwm-gpio.c:140:10: error: ‘const struct pwm_ops’ has no member named ‘enable’
140 | .enable = gpio_pwm_enable,
| ^~~~~~
drivers/pwm/pwm-gpio.c:140:19: error: initialization of ‘int (*)(struct pwm_chip *, struct pwm_device *, struct pwm_capture *, long unsigned int)’ from incompatible pointer type ‘int (*)(struct pwm_chip *, struct pwm_device *)’ [-Werror=incompatible-pointer-types]
140 | .enable = gpio_pwm_enable,
| ^~~~~~~~~~~~~~~
drivers/pwm/pwm-gpio.c:140:19: note: (near initialization for ‘gpio_pwm_ops.capture’)
drivers/pwm/pwm-gpio.c:141:10: error: ‘const struct pwm_ops’ has no member named ‘disable’
141 | .disable = gpio_pwm_disable,
| ^~~~~~~
drivers/pwm/pwm-gpio.c:141:20: error: initialization of ‘int (*)(struct pwm_chip *, struct pwm_device *, const struct pwm_state *)’ from incompatible pointer type ‘void (*)(struct pwm_chip *, struct pwm_device *)’ [-Werror=incompatible-pointer-types]
141 | .disable = gpio_pwm_disable,
| ^~~~~~~~~~~~~~~~
drivers/pwm/pwm-gpio.c:141:20: note: (near initialization for ‘gpio_pwm_ops.apply’)
I've ordered USB-UART module so that I can view the boot console, but it hasn't arrived yet, so I was wondering if anyone else is having this problem with the current branch
thanks,
steps followed:
cd /usr/src
git clone --depth 1 https://github.com/tobetter/linux.git -b odroidxu4-v4.6 linux-4.6.0
cd linux-4.6.0
make distclean; make mrproper
make odroidxu4-defconfig
make -j4
make modules_install
cp arch/arm/boot/zImage /boot/zImage-
make kernelrelease``cp arch/arm/boot/dts/exynos5422-odroidxu4.dtb /boot/odroidxu4.dtb-
make kernelrelease``update-initramfs -c -k
make kernelrelease``mkimage -A arm -O linux -T ramdisk -C none -a 0 -e 0 -n uInitrd -d /boot/initrd.img-
make kernelrelease /boot/uInitrd-
make kernelrelease``setenv bootcmd "fatload mmc 0:1 0x40008000 zImage-4.6.0+; fatload mmc 0:1 0x42000000 uInitrd-4.6.0+; fatload mmc 0:1 0x44000000 odroidxu4.dtb-4.6.0+; bootz 0x40008000 0x42000000 0x44000000"
$ LC_ALL=C ARCH=arm64 CROSS_COMPILE=aarch64-unknown-linux-gnu- make -j4
CALL scripts/checksyscalls.sh
CHK kernel/kheaders_data.tar.xz
UPD include/generated/utsversion.h
CC init/version-timestamp.o
LD .tmp_vmlinux.kallsyms1
aarch64-unknown-linux-gnu-ld: Unexpected GOT/PLT entries detected!
aarch64-unknown-linux-gnu-ld: Unexpected run-time procedure linkages detected!
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha2-ce-glue.o: in function `__sha256_block_data_order':
/home/fogti/devel/linux/arch/arm64/crypto/sha2-ce-glue.c:61:(.text+0x31c): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha2-ce-glue.c:61:(.text+0x5e8): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha2-ce-glue.c:61:(.text+0x664): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha2-ce-glue.c:61:(.text+0x770): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha2-ce-glue.c:61:(.text+0x9a8): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o:/home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32: more undefined references to `sha256_block_data_order' follow
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: in function `__sha256_block_neon':
/home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:41:(.text+0x264): undefined reference to `sha256_block_neon'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: in function `__sha256_block_data_order':
/home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0x3c0): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0x43c): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0x50c): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0x58c): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0x670): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: in function `__sha256_block_neon':
/home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:41:(.text+0x754): undefined reference to `sha256_block_neon'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:41:(.text+0x7b4): undefined reference to `sha256_block_neon'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: in function `__sha256_block_data_order':
/home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0x7e8): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0x8c4): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: in function `__sha256_block_neon':
/home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:41:(.text+0x9ac): undefined reference to `sha256_block_neon'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:41:(.text+0xa0c): undefined reference to `sha256_block_neon'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: in function `__sha256_block_data_order':
/home/fogti/devel/linux/arch/arm64/crypto/sha256-glue.c:32:(.text+0xa40): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: in function `__ksymtab_sha256_block_data_order':
sha256-glue.c:(___ksymtab+sha256_block_data_order+0x0): undefined reference to `sha256_block_data_order'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/sha256-glue.o: relocation R_AARCH64_PREL32 against symbol `sha256_block_data_order' which may bind externally can not be used when making a shared object; recompile with -fPIC
sha256-glue.c:(___ksymtab+sha256_block_data_order+0x0): dangerous relocation: unsupported relocation
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/poly1305-glue.o: in function `poly1305_init_arch':
/home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:30:(.text+0x34): undefined reference to `poly1305_init_arm64'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/poly1305-glue.o: in function `poly1305_update_arch':
/home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:150:(.text+0x144): undefined reference to `poly1305_blocks_neon'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:157:(.text+0x194): undefined reference to `poly1305_blocks'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:137:(.text+0x234): undefined reference to `poly1305_blocks'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/poly1305-glue.o: in function `poly1305_final_arch':
/home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:179:(.text+0x2ac): undefined reference to `poly1305_emit'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:176:(.text+0x308): undefined reference to `poly1305_blocks'
aarch64-unknown-linux-gnu-ld: arch/arm64/crypto/poly1305-glue.o: in function `neon_poly1305_blocks':
/home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:76:(.text+0x388): undefined reference to `poly1305_blocks_neon'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:78:(.text+0x3ac): undefined reference to `poly1305_blocks'
aarch64-unknown-linux-gnu-ld: /home/fogti/devel/linux/arch/arm64/crypto/poly1305-glue.c:55:(.text+0x41c): undefined reference to `poly1305_init_arm64'
make[1]: *** [scripts/Makefile.vmlinux:35: vmlinux] Fehler 1
make: *** [Makefile:1250: vmlinux] Error 2
Some symbols appear to be missing, and the functions appear to should've been defined in ...core.S
files, but they're empty. This is on commit 5bd8024.
I saw this kernel panic happen one time, have not been able to reliably reproduce it:
[ 1569.468061] systemd-journald[30]: Received client request to flush runtime journal.
[ 1569.709490] rockchip-pm-domain fdd90000.power-management:power-controller: failed to get ack on domain 'gpu', val=0x9fe
[ 1569.710500] SError Interrupt on CPU3, code 0xbe000011 -- SError
[ 1569.710513] CPU: 3 PID: 2930 Comm: Xorg Not tainted 5.18.0-rc7 #1
[ 1569.710518] Hardware name: Hardkernel ODROID-M1 (DT)
[ 1569.710521] pstate: 204000c9 (nzCv daIF +PAN -UAO -TCO -DIT -SSBS BTYPE=--)
[ 1569.710526] pc : _regmap_bus_reg_write+0x20/0x30
[ 1569.710540] lr : _regmap_write+0x5c/0xb0
[ 1569.710544] sp : ffff80000aea3900
[ 1569.710545] x29: ffff80000aea3900 x28: ffff00009ac7d700 x27: 0000000000000000
[ 1569.710554] x26: ffff0001008a9938 x25: ffff0001001dc080 x24: ffff0001000f2298
[ 1569.710559] x23: 0000000000000001 x22: ffff0001008a3000 x21: 0000000080000000
[ 1569.710565] x20: 0000000000000008 x19: ffff0001008a3000 x18: ffffffffffffffff
[ 1569.710570] x17: 66203a72656c6c6f x16: 72746e6f632d7265 x15: 776f703a746e656d
[ 1569.710575] x14: 6567616e616d2d72 x13: 65663978303d6c61 x12: 76202c2775706727
[ 1569.710580] x11: ffff800009eb3388 x10: ffff800009eb3388 x9 : 00000000ffffefff
[ 1569.710585] x8 : ffff800009f0b388 x7 : 0000000000017fe8 x6 : 00000000fffff000
[ 1569.710590] x5 : 0000000000000000 x4 : 0000000000000000 x3 : ffff800008873cc0
[ 1569.710595] x2 : 0000000080000000 x1 : ffff80000a293008 x0 : 0000000000000000
[ 1569.710601] Kernel panic - not syncing: Asynchronous SError Interrupt
[ 1569.710604] CPU: 3 PID: 2930 Comm: Xorg Not tainted 5.18.0-rc7 #1
[ 1569.710607] Hardware name: Hardkernel ODROID-M1 (DT)
[ 1569.710609] Call trace:
[ 1569.710612] dump_backtrace.part.0+0xc8/0xe0
[ 1569.710621] show_stack+0x18/0x70
[ 1569.710625] dump_stack_lvl+0x68/0x84
[ 1569.710632] dump_stack+0x18/0x34
[ 1569.710636] panic+0x168/0x328
[ 1569.710639] nmi_panic+0x88/0x90
[ 1569.710643] arm64_serror_panic+0x6c/0x80
[ 1569.710647] arm64_is_fatal_ras_serror+0x84/0x90
[ 1569.710650] do_serror+0x34/0x60
[ 1569.710653] el1h_64_error_handler+0x30/0x50
[ 1569.710659] el1h_64_error+0x64/0x68
[ 1569.710662] _regmap_bus_reg_write+0x20/0x30
[ 1569.710667] regmap_write+0x4c/0x80
[ 1569.710671] rockchip_pd_power+0x220/0x2d0
[ 1569.710677] rockchip_pd_power_on+0x14/0x20
[ 1569.710681] _genpd_power_on+0xc0/0x140
[ 1569.710685] genpd_power_on.part.0+0xa4/0x1f0
[ 1569.710689] genpd_runtime_resume+0xe4/0x280
[ 1569.710693] __rpm_callback+0x48/0x170
[ 1569.710698] rpm_callback+0x6c/0x80
[ 1569.710702] rpm_resume+0x364/0x5e0
[ 1569.710706] __pm_runtime_resume+0x4c/0x80
[ 1569.710710] panfrost_perfcnt_close+0x34/0xa0 [panfrost]
[ 1569.710730] panfrost_postclose+0x1c/0x50 [panfrost]
[ 1569.710739] drm_file_free.part.0+0x1a4/0x290 [drm]
[ 1569.710853] drm_close_helper.isra.0+0x5c/0x70 [drm]
[ 1569.710949] drm_release+0x68/0x110 [drm]
[ 1569.711044] __fput+0x70/0x230
[ 1569.711050] ____fput+0x10/0x20
[ 1569.711053] task_work_run+0x80/0x180
[ 1569.711059] do_notify_resume+0x1ec/0x1120
[ 1569.711066] el0_svc+0x9c/0xb0
[ 1569.711073] el0t_64_sync_handler+0xa4/0x130
[ 1569.711077] el0t_64_sync+0x18c/0x190
[ 1569.711084] SMP: stopping secondary CPUs
[ 1569.711097] Kernel Offset: disabled
[ 1569.711099] CPU features: 0x100,0000100d,19801c86
[ 1569.711103] Memory Limit: 4096 MB
[ 1569.735186] ---[ end Kernel panic - not syncing: Asynchronous SError Interrupt ]---
Figured this might be worth reporting.
Linux m1 5.18.0-rc7 #1 SMP PREEMPT Thu May 19 23:15:47 PDT 2022 aarch64 GNU/Linux
Kernel odroid-5.18.y commit 035eaa6
Hello. What I tried was native compile on the odroid n2+ I wish to install kernel 5.15 on:
git clone --depth 1 https://github.com/tobetter/linux -b odroid-5.15.y
cd linux
make defconfig
# I didn't edit config file or make menuconfig
make -j4
sudo make modules_install
sudo cp -f arch/arm64/boot/Image.gz arch/arm64/boot/dts/amlogic/meson64_odroidn2.dtb /media/boot/
sudo sync
sudo reboot
It was built without errors. After the reboot the screen was just black. The red LED and blue LED on the odroid were on solid color, no blinking blue heart beat. What did I miss? It's my first time doing this.
Thank you in advance.
The object file is referenced by the Makefile, but the C file was not added in the commit.
3a163dc#diff-3ecbae0b5d2a1c7684951cd0b643259df579598f3406d91c30110d0b3bfde6f0R50
make[3]: *** No rule to make target 'drivers/char/rk3568-gpiomem.o', needed by 'drivers/char/built-in.a'. Stop.
make[2]: *** [scripts/Makefile.build:500: drivers/char] Error 2
make[1]: *** [scripts/Makefile.build:500: drivers] Error 2
make: *** [Makefile:2012: .] Error 2
The following commit seems to be broken on 5.15.y.
drivers/pwm/pwm-gpio.c: In function ‘gpio_pwm_remove’:
drivers/pwm/pwm-gpio.c:232:9: error: void value not ignored as it ought to be
232 | return pwmchip_remove(&gpio_chip->chip);
| ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
drivers/pwm/pwm-gpio.c:233:1: error: control reaches end of non-void function [-Werror=return-type]
Unless its me? But it compiles fine on 5.14.15
Hello,
I am using your kernel in my Odroid XU4 in order to run Openstack on it. However, I am finding this error when I try to set up Openstack:
iptables v1.6.0: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
iptables v1.6.0: can't initialize iptables table `mangle': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.
modprobe: FATAL: Module ebtables not found in directory /lib/modules/4.2.0+
The kernel doesn't support the ebtables 'filter' table.
Is there a way for me to include the ebtables module?
There appears to be a fail in the following function concerning the ODROID-COMMON: power:reset: Add odroid support commit.
CC drivers/power/reset/odroid-reboot.o
drivers/power/reset/odroid-reboot.c: In function ‘odroid_restart_probe’:
drivers/power/reset/odroid-reboot.c:141:3: error: ‘arm_pm_restart’ undeclared (first use in this function); did you mean ‘alarm_restart’?
141 | arm_pm_restart = do_odroid_restart;
| ^~~~~~~~~~~~~~
| alarm_restart
drivers/power/reset/odroid-reboot.c:141:3: note: each undeclared identifier is reported only once for each function it appears in
make[6]: *** [scripts/Makefile.build:271: drivers/power/reset/odroid-reboot.o] Error 1
make[5]: *** [scripts/Makefile.build:514: drivers/power/reset] Error 2
make[4]: *** [scripts/Makefile.build:514: drivers/power] Error 2
make[4]: *** Waiting for unfinished jobs....
make[3]: *** [Makefile:1851: drivers] Error 2
make[3]: *** Waiting for unfinished jobs....
make[2]: *** [debian/rules:6: build] Error 2
dpkg-buildpackage: error: debian/rules build subprocess returned exit status 2
make[1]: *** [scripts/Makefile.package:83: bindeb-pkg] Error 2
make: *** [Makefile:1569: bindeb-pkg] Error 2
When deselected from the defconfig the build completes fine, of course the boards no longer have the ability to reboot correctly. Just thought you would like to know. Thank you!
Using the kernels from the 6.1 and 6.2 branches, it seems that on the Odroid HC1, SSDs are not powered off and then powered back on correctly after rebooting.
@tobetter any ideas why this is happening? Thanks!
Also posted on the forum: https://forum.odroid.com/viewtopic.php?f=93&t=46555
Perhaps this is a u-boot issue: https://forum.odroid.com/viewtopic.php?f=96&t=40978 ?
Im on an odroid n2+ (using you 6.6 kernel from master branch). on boot i get the following kernel message
[ 21.400692] meson8b-dwmac ff3f0000.ethernet eth0: Register MEM_TYPE_PAGE_POOL RxQ-0
[ 21.406658] meson8b-dwmac ff3f0000.ethernet eth0: __stmmac_open: Cannot attach to PHY (error: -19)
The only solution i found so far is to restart systemd-networkd
after boot every time, then everything works as expected.
Hi @tobetter
Thank you for your work on this as always,
I noticed that in odroid-5.15.y there is odroidxu4_defconfig, but not in odroid-5.16.y
Where did odroidxu4_defconfig go, and which defconfig should I use instead now?
Thanks :)
The ones on the hardkernel website for the hardkernel repo don't work on the 5.19.y branch
A declarative, efficient, and flexible JavaScript library for building user interfaces.
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google ❤️ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.