does not give rest))) [ 4.025054][ T1] kirkwood-pinctrl f1010000.pin-controller: unsupported function gpio on pin mpp7 [ 4.034257][ T1] pinctrl core: failed to register map default (1): invalid type given * Marvell Kirkwood 88f6282 name pins functions ================================================================================ mpp7 7 gpo,by MM - Debian
Quote bodhi Could you summarized what is lacking with stock u-boot that you guys want to have? and what is working, i.e SATA, USB, saving envs,... stock u-boot is quite functional, but for IP Plug netconsole would be very convenient (to get access to UART, i need to disassemble the entire case), it is also desirable to have u-boot envs in a script (uEnv.txt)by MM - Debian
bodhi, Quotebodhi Updated 25 Mar 2025: Kernel linux-6.13.8-kirkwood-tld-1 package has been uploaded. The following features were added/updated: ... - Updated PromWad Wtplug and Thin Client DTS ... Does DTS in the kernel topik have any differences from the latest version in this thread? Quotebodhi I think it is possible to have 2025.01 u-boot. But I'm out of time at the moment.by MM - Debian
bodhi, I worded the question incorrectly, the LED doesn't matter, I'm trying to find the reason of this message: [ 3.571022] kirkwood-pinctrl f1010000.pin-controller: unsupported function gpio on pin mpp7by MM - Debian
bodhi, please check the mpp7 function in DTS, is it definitely LED?by MM - Debian
cmp 18, I removed the link to avoid advertisingby MM - Rescue System
cmp 18, I removed the link to avoid advertising Some dude...by MM - Rescue System
cmp18, Some dude is selling thin clients with your openwrt build 23 for $15, you got famous)by MM - Rescue System
cmp18, _______ ________ __ | |.-----.-----.-----.| | | |.----.| |_ | - || _ | -__| || | | || _|| _| |_______|| __|_____|__|__||________||__| |____| |__| W I R E L E S S F R E E D O M ----------------------------------------------------- OpenWrt 24.10.0, r28427-6df0e3d02a a big thanks!by MM - Rescue System
bodhi, there is some tryings: - modules se and cu of rtl8192xx - usb wifi dongle via external powered usb hub (without drivers, only detction test) root@debian:~# modprobe rtl8192se root@debian:~# lsmod Module Size Used by rtl8192se 73728 0 rtl_pci 28672 1 rtl8192se rtlwifi 114688 2 rtl8192se,rtl_pci mt76x0uby MM - Debian
8191su works via USB signalling :)by MM - Debian
bodhi, >>Is this a plain 8191, or is there any s/u/c/e suffix in the model name? it's 8191su root@debian:~# dmesg | grep rtl root@debian:~# modprobe rtl8192ce root@debian:~# lsmod Module Size Used by rtl8192ce 61440 0 rtl_pci 28672 1 rtl8192ce rtl8192c_common 61440 1 rtl8192ce rtlwifi 114688 3 rtl_by MM - Debian
bodhi, 6.13.0 kernel pci probe with realtek 8191 wifi card root@debian:~# dmesg | grep -iE 'pci|xhci' [ 2.500094] PCI: CLS 0 bytes, default 32 [ 4.024622] mvebu-pcie mbus@f1000000:pcie@82000000: host bridge /mbus@f1000000/pcie@82000000 ranges: [ 4.034550] mvebu-pcie mbus@f1000000:pcie@82000000: Parsing ranges property... [ 4.034592] mvebu-pcie mbus@f1000000:pcby MM - Debian
bodhi > Yes, my bad! Sorry, it's mine) I used wrong DTB (thin client for ip-plug) and got red blinking LED:) > They are both 38 and 39 in both cases already. I didn’t pay attention that this is the second bankby MM - Debian
bodhi, >I could look into rolling new u-boot in a couple of months... Will 1M partition be enough for the new u-boot 2025?by MM - Debian
bodhi, LED's GPIO different in two sections of kirkwood-promwad-wtplug.dts: pmx_leds: pmx-leds { marvell,pins = "mpp38", "mpp39"; marvell,function = "gpio"; }; and gpio-leds { compatible = "gpio-leds"; pinctrl-0 = <&pmx_leds>; pinctrl-names = "default"; led-red { label = "wtplug:reby MM - Debian
cmp18, NAND params of IP-PLUG: NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit) Scanning device for bad blocks Bad eraseblock 2960 at 0x000017200000 Bad eraseblock 3222 at 0x0000192c0000 Bad eraseblock 3977 at 0x00001f120000 Bad eraseblock 4088 at 0x00001ff00000 Using static partition definition Creating 4 MTD partitions on "nand_mtd": 0x0by MM - Rescue System
bodhi, >I could look into rolling new u-boot in a couple of months... Wow! Good news, thanks!by MM - Debian
bodhi, Is it possible to make u-boot 2017 for promwad boxes? netconsole is very good on my goflexnet, on wtplug access to UART also requires disassembling the entire boxby MM - Debian
Mikele25, The implementation of Intel AC 7260 support is in the kmod-iwlwifi module, let's try itby MM - Debian
cmp18, ak-systems ip-plug (cost about $5) Something tells me we'll be getting ip-plug openwrt build in a few weeks)by MM - Debian
Michele25, has kmod-i2c-core been added to the kernel?by MM - Debian
bodhi, thanks for new dtb, could you share the dts? I bought wtplug (version without usb/pcie) someday I'll get around to it for OpenWrt and then thin client will return for Debian there can't be too many ARM devices ;)by MM - Debian
bodhi, u-boot i2c probe: Marvell>> i2c probe Valid chip addresses: 1A 64 Marvell>> i2c probe 0 Valid chip addresses: 1A 64 Marvell>> i2c probe 1 Valid chip addresses: 1A 64 Marvell>>by MM - Debian
the new box seems to have problems( log from the old oneby MM - Debian
bodhi, log with new DTBby MM - Debian
bodhi, cool, pin8 and pin9 (twsi0) was busy by uart1 Thanks! ==== edit: i reread pin functions and dts)by MM - Debian
... from kirkwood-6282.dtsi: /* * Default I2C1 pinctrl setting on mpp36/mpp37, * overwrite marvell,pins on board level if required. */ pmx_twsi1: pmx-twsi1 { marvell,pins = "mpp36", "mpp37"; marvell,function = "twsi1"; }; in the 6282 dtsi i2c1 is defined, not i2c0by MM - Debian
bodhi, cmp18 6282 has two i2c buses, may be 64 is valid addres for second? http://lists.infradead.org/pipermail/linux-arm-kernel/2013-January/145043.htmlby MM - Debian