|
From: Michael S. <ma...@uc...> - 2001-05-28 04:25:12
|
On Sun, May 27, 2001 at 12:54:56PM -0400, Marty Connor wrote: > Looking at the code again and comparing to the Linux driver, I have > another thought. Etherboot drivers don't use interrupts, and so where in > the kernel, you can do things like set "next_tick" and then run_at, we > have to do things other ways. > > What it looks like to me (and boy would it be nice if I had a Cisco > hub/switch to test this with) is that there is a time delay (and recheck) > needed after media selection. That makes sense -- the linux tulip driver messages at boot look like: May 25 17:47:17 d01 kernel: eth0: Lite-On 82c168 PNIC rev 32 at 0xe400, 00:A0:CC:56:99:E9, IRQ 11. May 25 17:47:17 d01 kernel: eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1. May 25 17:47:17 d01 network: Bringing up interface eth0: succeeded May 25 17:47:19 d01 kernel: eth0: Setting full-duplex based on MII#1 link partner capability of 41e1. Depending on how exactly the time stamps work possibly it's over a second to get to 100 Mbit/full-duplex with the linux driver and the Cisco-4000. > differently. The brute-force test for this is to insert a cheap 10 > BASE-T hub in between you and the Cisco, and see if it magically works. Etherboot does boot if the machine is connected to a cisco-1700 switch on the same subnet (10 Mbit). |
