On 17/05/12 18:10, David Gálvez wrote:
EtherNat's nertwork driver is working fine.
That's good to know. Well, not entirely - it does mean my EtherNAT is
dead ...
What interrupt does it report it uses? Do you see the card interrupts
accumulate in /proc/interrupts?
When loading the USB driver I'm getting this:
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
isp116x-hcd isp116x-hcd: ISP116x Host Controller
isp116x-hcd isp116x-hcd: new USB bus registered, assigned bus number 1
116x: Clock not ready after 15ms
116x: Please make sure that the H_WAKEUP pin is pulled low!
isp116x-hcd isp116x-hcd: can't setup
isp116x-hcd isp116x-hcd: USB bus 1 deregistered
116x: init error, -19
Just what I'm getting as well. Back to the drawing board. I'll have to
get confirmation on the exact addresses being used from the EtherNAT
designer.
Thanks a lot,
Michael
--
To unsubscribe from this list: send the line "unsubscribe linux-m68k" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
