Re: [U-Boot] NEC OHCI chip bug

2010-12-20 Thread Macpaul Lin
Hi Martin, 2010/12/17 Martin Mueller : > Hi Gavin, > >> > detection might work without PCI slave-initiated transfer and the >> > root hub is OHCI internal. But - just guessing. If you have double >> > checked the window there are no more ideas from my side. >> >> Do you setup host bridge window ba

Re: [U-Boot] NEC OHCI chip bug

2010-12-17 Thread Martin Mueller
Hi Gavin, > > detection might work without PCI slave-initiated transfer and the > > root hub is OHCI internal. But - just guessing. If you have double > > checked the window there are no more ideas from my side. > > Do you setup host bridge window base & size? Exactly, I didn¡¦t set > it before.

Re: [U-Boot] NEC OHCI chip bug

2010-12-17 Thread gavinguo
> detection might work without PCI slave-initiated transfer and the > root hub is OHCI internal. But - just guessing. If you have double > checked the window there are no more ideas from my side. Do you setup host bridge window base & size? Exactly, I didn’t set it before. Suppose, PCI devices on

Re: [U-Boot] NEC OHCI chip bug

2010-12-16 Thread Martin Mueller
Hi Gavin, On 17.12.2010 04:49, gavin...@andestech.com wrote: >> not sure if the PCI bus number plays a role here. In our case the PCI >> window size was not set correctly so that the OHCI access to the PCI >> bus/RAM was refused. > > I found it strange that 2 devices are detected, and we can get

Re: [U-Boot] NEC OHCI chip bug

2010-12-16 Thread gavinguo
> not sure if the PCI bus number plays a role here. In our case the PCI > window size was not set correctly so that the OHCI access to the PCI > bus/RAM was refused. I found it strange that 2 devices are detected, and we can get descriptor from hub descriptor. And the "Unrecoverable Error" is occu

Re: [U-Boot] NEC OHCI chip bug

2010-12-16 Thread Martin Mueller
Hi Gavin, > > are you sure it is that NEC bug? We had a similar error message when the > > PCI bridge was not properly setup and the OHCI could not access RAM > > through PCI (DMA), hence the "unrecoverable error". > > The bus/dev/func/ number of OHCI host controller are 0/8/0 and 0/8/1, bus > num

Re: [U-Boot] NEC OHCI chip bug

2010-12-15 Thread gavinguo
Hi Martin, > are you sure it is that NEC bug? We had a similar error message when the > PCI bridge was not properly setup and the OHCI could not access RAM > through PCI (DMA), hence the "unrecoverable error". The bus/dev/func/ number of OHCI host controller are 0/8/0 and 0/8/1, bus number is

[U-Boot] NEC OHCI chip bug

2010-12-15 Thread Martin Mueller
Hi Gavin , > We need NEC pci-to-usb host controller work on U-boot. Because > using Faraday technology PCI controller, I need to complete the PCI > driver first. Now the PCI driver is completed. At this time, the > NEC host controller can work. When plugging a keyboard, 2 devices > can be found sh

Re: [U-Boot] NEC OHCI chip bug

2010-12-15 Thread gavinguo
> Seems you have to implement this workaround for U-Boot. Patches > welcome. Ok, I will try my best to figure out how to implement this one. > And *PLEASE* restrict your line length to some 70 or so characters. Thank you for the reminder. I have modified the setting to 70 characters a line. Re

Re: [U-Boot] NEC OHCI chip bug

2010-12-14 Thread Wolfgang Denk
Dear gavin...@andestech.com, In message <50fd90c65c53fb45badeebcd84ff07f20290e...@atcpcs06.andestech.com> you wrote: > Hi All, > Let's me explain the story first. > We need NEC pci-to-usb host controller work on U-boot. Because using Faraday > technology PCI controller, I need to complete the PC

[U-Boot] NEC OHCI chip bug

2010-12-14 Thread gavinguo
Hi All, Let's me explain the story first. We need NEC pci-to-usb host controller work on U-boot. Because using Faraday technology PCI controller, I need to complete the PCI driver first. Now the PCI driver is completed. At this time, the NEC host controller can work. When plugging a keyboard, 2