Re: smsc9514 - waiting for devices (Re: Pandaboard ES)
Rui-Xiang Guo <[email protected]> Thu, 9 Oct 2025 11:08:06 +0800
| Newsgroups | gmane.os.netbsd.ports.arm |
|---|---|
| Message-ID | <aOcnFhrrHVRcQuDn@picohive> |
On Fri, May 09, 2025 at 04:42:15PM +0800, Rui-Xiang Guo wrote: > On Wed, May 07, 2025 at 08:26:39PM -0400, Lwazi Dube wrote: > > On Sun, 4 May 2025 at 06:04, Rui-Xiang Guo <[email protected]> wrote: > > > > > Hi, > > > my test steps: > > > smsc9514 is activated in u-boot first > > > => usb info > > > 1: Hub, USB Revision 2.0 > > > - u-boot EHCI Host Controller > > > <snip> > > > > > > then booting kernel and I get such related debug messages: > > > [ 2.0001780] uhub0 at usb0: NetBSD (0x0000) EHCI root hub (0x0000), > > > class 9/0, rev 2.00/1.00, addr 1 > > > [ 2.0099135] uhub0: 3 ports with 3 removable, self powered > > > [ 2.0419450] uhub1 at usb1: NetBSD (0x0000) MOTG root hub (0x0000), > > > class 9/0, rev 2.00/1.00, addr 1 > > > [ 2.0579597] uhub1: 1 port with 1 removable, self powered > > > [ 2.0739677] WARNING: system needs entropy for security; see entropy(7) > > > [ 2.6273143] IPsec: Initialized Security Association Processing. > > > [ 2.6657300] sdmmc1: couldn't enable card: 60 > > > [ 2.6913199] aes: ARM NEON vpaes > > > [ 2.6977225] chacha: ARM NEON ChaCha > > > [ 2.7041246] adiantum: self-test passed > > > [ 2.7116708] aes_ccm: self-test passed > > > [ 2.7201230] blake2s: self-test passed > > > [ 2.7457158] sdmmc0: SD card status: 4-bit, C10 > > > [ 2.7521158] ld0 at sdmmc0: <0x03:0x5344:SU16G:0x80:0x1bec8779:0x0c8> > > > [ 2.7649147] ld0: 15193 MB, 7717 cyl, 64 head, 63 sec, 512 bytes/sect x > > > 31116288 sectors > > > [ 2.7841226] ld0: 4-bit width, High-Speed/SDR25, 50.000 MHz > > > [ 3.1105168] waiting for devices: usb0 uhub0 > > > [ 3.4369144] waiting for devices: usb0 uhub0 > > > [...] > > > [ 22.6945067] waiting for devices: usb0 uhub0 > > > [ 23.0209050] waiting for devices: usb0 uhub0 > > > [ 23.2257045] uhub0: device problem, disabling port 1 > > > [ 23.2333415] waiting for devices: usb0 > > > > > > Any ideas? > > > > > > -rxg > > > > > > > The kernel is overwriting your u-boot settings. Try commenting out > > ti_usb_init(sc). > > Helpful tip! > > [ 2.8356554] uhub2 at uhub0 port 1: vendor 0424 (0x0424) product 9514 (0x9514), class 9/0, rev 2.00/2.00, addr 2 > [ 2.8544543] uhub2: multiple transaction translators > [ 3.1716543] usmsc0 at uhub2 port 1 > [ 3.1780713] usmsc0: vendor 0424 (0x0424) product ec00 (0xec00), rev 2.00/2.00, addr 3 > [ 3.2036592] smscphy0 at usmsc0 phy 1: SMSC LAN8700 10/100 Ethernet Transceiver, rev. 3 > [ 3.2196595] smscphy0: 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto > [ 3.2331832] usmsc0: Ethernet address ff:ff:ff:ff:ff:ff > > I add wip/u-boot-omap4-panda for smsc9514 support in legacy mode because > the chip doesn't work in the modern u-boot of pandaboard. > But it is better to be activated in NetBSD without u-boot support. For activating smsc9514 on pandaboard, it requires the special procedure. I change my mind to let the switch remain in u-boot. Keep things simple. :) -rxg