Subject: Re: Problems installing i386 1.2.1 -- EHPL!!...uh, HELP!!
To: Jonathan Stone <jonathan@DSG.Stanford.EDU>
From: I can teach you how to fish... <greywolf@starwolf.starwolf.com>
List: port-i386
Date: 07/28/1997 23:28:10
[thanks to thorpej && jonathan for their replies. --*greywolf; ]

Jonathan Stone sez:
/*
 * 
 *  > > BUT:
 *  > > ep1: no connectors! address 00:c0:4f:bd:3b:0b        <?? What's this mean?
 *  > > ep1: interrupting at irq 11
 *  >
 *  >...means that the 905 probably didn't work properly in 1.2.1.  *shrug*
 *  >I'm told it works well in -current.
 * 
 * Yes, it works well in -current. 
 * 
 * The 3c595 worked fine in early 1.2 and in 1.2.1, too, so the 3c905
 * should work in 1.2.1.  The NetBSD driver treats the 3c905 and the
 * 3c595 identically, so it really should work in 1.2.1.
 * 
 * If the driver printed out the MAC address, then the driver really
 * should work.  You just have to configure the media speed via the 3Com
 * DOS utility: the link[012] switches don't work on the 3c59x/3c90x
 * generation, and 1.2.1 doesn't have the if_media extensions.

That's interesting; according to the release notes, the 3c905 is
supported with the link* switches.

 * 
 * It's attached as ep1, not ep0, because the GENERIC "ep0 at isa" line
 * ties down ep0, and causes "ep* at pci" and "ep* at eisa" start at ep1
 * and work upwards.
 */

Is this to imply that  "ep1 at isa0" is really an eisa attachment?
I don't get "ep1 at eisa0" or "ep1 at pci0".


				--*greywolf;
--
Assignment:  Think about and expound upon the possibilities of these two 
questions.  What would the world be like today if
    a)  the Roman Empire had been defeated early on? (religious implications)
    b)  the Stock Market had not crashed? (economical/political implications)