From: Alessandro Suardi <alessandro.suardi@oracle.com>
To: Patrick Mochel <mochel@osdl.org>
Cc: Jeff Garzik <jgarzik@mandrakesoft.com>,
Mikael Pettersson <mikpe@csd.uu.se>,
linux-kernel@vger.kernel.org
Subject: Re: 2.5.20 tulip bogosities
Date: Fri, 07 Jun 2002 14:08:17 +0200 [thread overview]
Message-ID: <3D00A231.3020003@oracle.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0206061139111.654-100000@geena.pdx.osdl.net>
Patrick Mochel wrote:
> On Thu, 6 Jun 2002, Jeff Garzik wrote:
>
>
>>Mikael,
>>
>>Can you try an experiment for me?
>>
>>Run 2.5.19 with the 2.5.20 tulip. Just copy drivers/net/tulip/* from
>>2.5.20 into 2.5.19.
>>
>>Nothing changed in 2.5.20 tulip that should cause that, AFAICS. So I
>>want to narrow down the problem before looking further.
>
>
> There was a bug in the PCI code that only passed the first device ID the
> driver supported to the driver's probe callback. It caused a few other
> oddities. A patch was posted to the list:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=102316813812289&w=2
>
> and is now in Linus' tree. It should fix the problem, if you get a chance
> to test it...
Just wanted to restate that this patch is still not enough to
make my Xircom PCI CardBus card work properly (xircom_cb driver).
Jun 7 12:49:24 dolphin cardmgr[597]: get dev info on socket 0 failed: Resource temporarily unavailable
All LEDs on the card never light up at all.
--alessandro
"the hands that build / can also pull down
even the hands of love"
(U2, "Exit")
next prev parent reply other threads:[~2002-06-07 12:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-06 16:24 2.5.20 tulip bogosities Mikael Pettersson
2002-06-06 18:31 ` Jeff Garzik
2002-06-06 18:41 ` Patrick Mochel
2002-06-07 12:08 ` Alessandro Suardi [this message]
2002-06-07 17:04 ` Thunder from the hill
2002-06-07 17:17 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-06-06 20:26 Mikael Pettersson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3D00A231.3020003@oracle.com \
--to=alessandro.suardi@oracle.com \
--cc=jgarzik@mandrakesoft.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=mochel@osdl.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.