2012/5/18 Michael Schmitz <schmitzmic@xxxxxxxxxxxxxx>:
On 18/05/12 02:49, David Gálvez wrote:
What interrupt does it report it uses? Do you see the card interrupts
accumulate in /proc/interrupts?
smc91x: IOADDR 0902c000 doesn't match configuration (300).
smc91x.c: v1.1, sep 22 2004 by Nicolas Pitre<nico@xxxxxxxxxxx>
eth0: SMC91C11xFD (rev 2) at 0902c000 IRQ 140 [nowait]
/proc/interrupts has this entry:
140: 68 atari eth0
That's good - now what is the transmit/receive speed you get with this
driver on a large file transfer?
Transfer by ftp of a 230 MB file, CT060 Falcon is the server, and my
Ubuntu machine the client.
Receiving the file the speed stabilizes around 85 KB/s.
Transmitting the speed stabilizes around 105 KB/s
The addresses are these:
ISP116X_HCD_ADDR 0x80000016
ISP116X_HCD_DATA 0x80000012
I don't think I tried that combination - where did you find that?
Those addresses are used by the Ethernat USB driver for MiNT, which
it's working quite well.
Anyway, new test kernel on the way. Won't do anything useful with the USB
chipset other than hopefully probe it OK.
Below, you can find what I'm getting with this new kernel and module.
One important thing, ISP116x data bus has 16 bits, the EtherNat
hardware swaps both bytes before writing them to the bus or after
reading from it. I'm sure the driver doesn't consider this, so I think
this is the reason why an ivalid chip ID is gotten.
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: irq 139, io base 0x80000012
116x: Invalid chip ID 1000
isp116x-hcd isp116x-hcd: startup error -19
isp116x-hcd isp116x-hcd: USB bus 1 deregistered
116x: init error, -19
--
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
