Re: microSONIC using if_ssce.c
Eyal Lebedinsky <[email protected]> Tue, 02 Mar 2004 09:56:09 +1100
| Newsgroups | gmane.os.netbsd.ports.pc532 |
|---|---|
| Organization | Eyal at Home |
| Message-ID | <[email protected]> |
Sverre Froyen wrote: > I seem to remember a quirk that tells the SCSI driver not to look for > LUNS? Yes, I since found it. It did not compile as is but was not too hard to fix. The bootup now looks like ths: ssce0 at scsibus0 target 3 lun 0: <SonicSys, MicroSCSI, 2.00> processor fixed ssce0: ethernet address 00:40:10:07:a7:67 uk0 at scsibus0 target 3 lun 1: <SonicSys, MicroSCSI, 2.00> processor fixed uk1 at scsibus0 target 3 lun 2: <SonicSys, MicroSCSI, 2.00> processor fixed uk2 at scsibus0 target 3 lun 3: <SonicSys, MicroSCSI, 2.00> processor fixed uk3 at scsibus0 target 3 lun 4: <SonicSys, MicroSCSI, 2.00> processor fixed uk4 at scsibus0 target 3 lun 5: <SonicSys, MicroSCSI, 2.00> processor fixed uk5 at scsibus0 target 3 lun 6: <SonicSys, MicroSCSI, 2.00> processor fixed uk6 at scsibus0 target 3 lun 7: <SonicSys, MicroSCSI, 2.00> processor fixed ssce0: async, 8-bit transfers uk0: async, 8-bit transfers uk1: async, 8-bit transfers uk2: async, 8-bit transfers uk3: async, 8-bit transfers uk4: async, 8-bit transfers uk5: async, 8-bit transfers uk6: async, 8-bit transfers Better still, I managed to bring up the interface and do some pings. While it is all too easy to evoke SCSI errors, it seems that the driver works in general. Here is a sample ftp session fetching a file into the pc532: ftp> get kernel-source-2.4.20-30.9.i386.rpm local: kernel-source-2.4.20-30.9.i386.rpm remote: kernel-source-2.4.20-30.9.i386.rpm 227 Entering Passive Mode (192,168,2,4,102,162) 150 Opening BINARY mode data connection for kernel-source-2.4.20-30.9.i386.rpm (38926014 bytes). 100% |****************************************| 38013 KB 161.90 KB/s 00:00 ETA 226 Transfer complete. 38926014 bytes received in 03:54 (161.87 KB/s) Some flooding too seem to keep up: [root@e1]# ping -c 1000 -s 1500 -f 192.168.2.4 PING e4b2.eyal.emu.id.au (192.168.2.4): 1500 data bytes ................ ----e4b2.eyal.emu.id.au PING Statistics---- 1000 packets transmitted, 1000 packets received, 0.0% packet loss round-trip min/avg/max/stddev = 30.194/147.205/293.341/58.320 ms 71.0 packets/sec sent, 70.9 packets/sec received -- Eyal Lebedinsky ([email protected]) <http://samba.org/eyal/>