From owner-freebsd-hackers  Mon Aug  7 11:29:46 2000
Delivered-To: freebsd-hackers@freebsd.org
Received: by hub.freebsd.org (Postfix, from userid 618)
	id 04EFF37B859; Mon,  7 Aug 2000 11:29:43 -0700 (PDT)
Subject: Re: 3Com 10/100 Mini PCI Ethernet
In-Reply-To: <20000807113657.B38461F1C@bert.kts.org> from Hellmuth Michaelis at "Aug 7, 2000 01:36:57 pm"
To: hm@kts.org
Date: Mon, 7 Aug 2000 11:29:42 -0700 (PDT)
Cc: freebsd-hackers@freebsd.org, msmith@FreeBSD.ORG
X-Mailer: ELM [version 2.4ME+ PL54 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Message-Id: <20000807182943.04EFF37B859@hub.freebsd.org>
From: wpaul@FreeBSD.ORG (Bill Paul)
Sender: owner-freebsd-hackers@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.ORG

> Mike Smith wrote:
> 
> > > I think the ep driver (which does some funny things to the eeprom) managed
> > > to overwrite part of the eeprom so that the xl driver failed to recognize
> > > the card. I then tried to add it to the vx driver (at that point i think
> > > i started to know what i did) which failed too, so i wrote a subroutine
> > > to display the eeprom contents which (because i did not understood the
> > > the OP and SubOP command fields before running it) finally erased the
> > > eeprom contents to 0xffff in all locations (which now prevents the card
> > > from being initialized by the BIOS - has anybody an idea how to revive
> > > such a PCI card ????).
> > 
> > You would need to write the original EEPROM contents back into the 
> > EEPROM, after manually configuring it.  Very difficult.
> 
> Am i right assuming that pciconf is the right tool for this (manually 
> configuring) job ?

No, you are wrong. The only way to write to the EEPROM (that I know of
anyway) is via the usual EEPROM control registers in the card's I/O
space, which won't be mapped if the card is so fubared that the BIOS
won't initialize it. 
 
> > > Do i understand you right in that you would do a fresh start with this
> > > card using the xl driver ? I'm a bit concerned about again accidentially
> > > overwriting the eeprom, its an _expensive_ card ... ;-)

Then you should have been more careful with it.

> > That's correct.  The xl driver is not likely to trash the eeprom, 
> > although I'm quite surprised that the 'ep' driver did.
> > 
> > What possessed you to start with an ISA-only driver when the device is so 
> > clearly a PCI device?
> 
> It was the device ID 0x6055 in the ep driver which is identical to the
> device ID in the Mini PCI version.

I'm sorry, but after reading this thread, I'm having a hard time coming
up with an explanation for this nonsense which doesn't involve you being
a dumbass. The device ID in question is in if_ep_pccard.c which is for
PCMCIA devices only! Not PCI! There is no way that the ep driver will
probe a PCI device unless you go to some lengths to twist its arm! Why
you resorted to this arm-twisting instead of the blazingly obvious
action of trying an actual PCI driver is beyond me. (_How_ you even
managed to twist its arm is also beyond me. Obviously you decided not
to tell us exactly what you did for fear of being found out. Too late.)

This is not one of those "it's nobody's fault" situations. You did
not make an innocent mistake: you screwed up. In front of god and
everything. You ignored all of the signs, portents, and the dude with
the spooky black robe and scythe standing over your shoulder. And then
you tried to cover it up.

Now, get out a piece of paper, write "I damaged this card because
I'm a dumbass" on it, stick it to the card, then take it back to where
you got it and try to get it replaced. Alternatively, tell us where you
got it so I can order one and try to get it supported properly instead
of having my blood pressure driven off the scale by yet another tale
of foot-shooting idiocy.

-Bill


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-hackers" in the body of the message