Re: ep0 etherlink III breakage

1999-09-29 Thread Russell Cattelan
Mark Hittinger wrote: Hey per request I'm reporting some ep0 breakage in today's -current. I have an etherlink III 3c509B and the probing appears correct. Sequence of events boot -s # ifconfig ep0 inet 192.168.18.200 (PC hangs) More later...

Re: ep0 etherlink III breakage

1999-09-22 Thread Timo Geusch
On Wed, Sep 22, 1999 at 10:40:22AM +0800, Peter Wemm wrote: No, it's better to remove "device ep0 at isa ? port foo irq blah ..." etc and just have "device ep0" *only*. If the pnp code finds it, let it use pnp to configure it. Does it do that by now? About two or three months ago it didn't

Re: ep0 etherlink III breakage

1999-09-22 Thread David O'Brien
I think David was joking with you, hence the \begin{wpaul} statement. Bill Paul is of course our resident Ethernet driver guy, and he is not known for his patience with people who do not supply enough information. :) Only 1/2 joking. This seems to be my month for content free bug reports. I

Re: ep0 etherlink III breakage

1999-09-22 Thread David O'Brien
Actually I don't really care what you do with this. I did say "more later" but you chopped that part out. I was only trying to give a heads up. Then way waste people's time with content-free messages? Just to lower the signal-to-noise ratio? We all could have waited for this email.

Re: ep0 etherlink III breakage

1999-09-20 Thread David O'Brien
On Mon, Sep 20, 1999 at 12:28:27PM -0500, Mark Hittinger wrote: Hey per request I'm reporting some ep0 breakage in today's -current. I have an etherlink III 3c509B and the probing appears correct. Sequence of events boot -s # ifconfig ep0 inet 192.168.18.200

Re: ep0 etherlink III breakage

1999-09-20 Thread Matthew Hunt
On Mon, Sep 20, 1999 at 11:58:28AM -0700, David O'Brien wrote: Sequence of events boot -s # ifconfig ep0 inet 192.168.18.200 (PC hangs) \begin{wpaul} Dunno, you seem too mellow. WHAT am I supose to do with this? I don't even understand what

Re: ep0 etherlink III breakage

1999-09-20 Thread Jason Young
I'm not certain what the problem is, but the ep0 changes that generated the HEADS UP messages affect _only_ PC Cards. The other sections of code are untouched. Further, I'm 99% sure the only card that could possibly have been broken by the probe change is the 3C574 PC Card (not 3C574B). Jason

Re: ep0 etherlink III breakage

1999-09-20 Thread Mark Hittinger
WHAT am I supose to do with this? I don't even understand what you are trying to tell me. You booted single user and got a hang. What is the #'ed line supose to be? Last time *_I_* booted single user I didn't see such output. Actually I don't really care what you do with