From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: Simon Huggins <huggie@earth.li>
Cc: Linux Kernel mailing list <linux-kernel@vger.kernel.org>
Subject: Re: D-LINK DFE-530-TX
Date: Wed, 13 Dec 2000 13:10:07 -0500 [thread overview]
Message-ID: <3A37BB7F.7291DF8@mandrakesoft.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0012061942570.620-100000@asdf.capslock.lan> <20001208012321.A1732@colonel-panic.com> <3A30F68F.50076AA7@mandrakesoft.com> <20001213093247.A24856@paranoidfreak.freeserve.co.uk>
Simon Huggins wrote:
> On Fri, Dec 08, 2000 at 09:56:15AM -0500, Jeff Garzik wrote:
> > Peter Horton wrote:
> > > If the PCI device ID is 3065 then it's via-rhine, but not supported
> > > by the driver in the kernel. Get updated via-rhine from Donald
> > > Becker's site http://www.scyld.com/network.
> > 2.4.x-test has some fixes for via-rhine which don't appear to have made
> > it into the Becker driver yet...
>
> Is either of these likely to make it into the stock 2.2 via-rhine?
Becker never replies to patches and changes I send him, so who knows.
Ask Becker...
Jeff
--
Jeff Garzik |
Building 1024 | These are not the J's you're lookin' for.
MandrakeSoft | It's an old Jedi mind trick.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
prev parent reply other threads:[~2000-12-13 18:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-07 0:44 D-LINK DFE-530-TX Mike A. Harris
2000-12-07 14:06 ` James Bourne
2000-12-07 16:28 ` Marco Colombo
2000-12-07 16:39 ` Alan Cox
2000-12-07 16:47 ` James Bourne
2000-12-07 16:56 ` Marco Colombo
2000-12-07 17:02 ` James Bourne
2000-12-07 16:50 ` Marco Colombo
2000-12-07 22:56 ` Dr. Kelsey Hudson
2000-12-08 1:23 ` Peter Horton
2000-12-08 14:56 ` Jeff Garzik
2000-12-13 8:32 ` Simon Huggins
2000-12-13 14:47 ` Alan Cox
2000-12-15 0:23 ` D-LINK DFE-530-TX [patch] Urban Widmark
2000-12-13 18:10 ` Jeff Garzik [this message]
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=3A37BB7F.7291DF8@mandrakesoft.com \
--to=jgarzik@mandrakesoft.com \
--cc=huggie@earth.li \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox