>> 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)
>> Mor
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 lat
> 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.
> Gu
> 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.
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
Jason Young wrote:
>
> > ie0: unknown board_id: f000
> > 1 3C5x9 board(s) on ISA found at 0x300
> > ep0 at port 0x300-0x30f irq 10 on isa0
> > ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e
> > isa_compat: didn't get ports for le
> > isa_compat: didn't get ports for cs
> > unknown0: <3Com 3C509B Ether
> ie0: unknown board_id: f000
> 1 3C5x9 board(s) on ISA found at 0x300
> ep0 at port 0x300-0x30f irq 10 on isa0
> ep0: utp[*UTP*] address 00:a0:24:a1:9a:1e
> isa_compat: didn't get ports for le
> isa_compat: didn't get ports for cs
> unknown0: <3Com 3C509B EtherLink III> at port 0x210-0x21f irq 5
> 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 wi
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 Y
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 understa
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
>
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...
Mark Hittinger
Mindspring/Net
12 matches
Mail list logo
