From: Jeff Garzik <jgarzik@pobox.com>
To: Stephan von Krawczynski <skraw@ithnet.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: Realtek network card
Date: Wed, 13 Aug 2003 09:04:51 -0400 [thread overview]
Message-ID: <3F3A3773.5070108@pobox.com> (raw)
In-Reply-To: <20030813133059.616f0faa.skraw@ithnet.com>
Stephan von Krawczynski wrote:
> Hello all,
>
> does anybody know how to make the below work (neiter 2.2.25 nor 2.4.21 seem to recognise it):
>
> lspci --vv:
>
> 00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd.: Unknown device 8131 (rev 10)
> Subsystem: Realtek Semiconductor Co., Ltd.: Unknown device 8139
The subsystem device id seems to indicate 8139, so you probably just
need to add pci ids to 8139too.c.
Jeff
next prev parent reply other threads:[~2003-08-13 13:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 11:30 Realtek network card Stephan von Krawczynski
2003-08-13 12:37 ` Micha Feigin
2003-08-13 13:04 ` Jeff Garzik [this message]
2003-08-13 13:57 ` Mike Dresser
2003-08-13 15:52 ` Ian Hastie
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=3F3A3773.5070108@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=skraw@ithnet.com \
/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;
as well as URLs for NNTP newsgroup(s).