From: "Vergoz Michael" <mvergoz@sysdoor.com>
To: "Jeff Garzik" <jgarzik@pobox.com>, "Ducrot Bruno" <poup@poupinou.org>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: 8139too.c patch for kernel 2.4.19
Date: Mon, 18 Nov 2002 18:51:55 +0100 [thread overview]
Message-ID: <001901c28f2b$2f3540a0$76405b51@romain> (raw)
In-Reply-To: 3DD9227E.5030204@pobox.com
Hi list,
The driver that i have post support realtek 8139A/B/C/D/C+ (already tested)
and another dlink card (realtek based).
On certain motherboard where the chip is integred you will perhaps have some
troubles.
The driver 8139cp.c can be removed to the source entry.
I think it's the better way to removed it, but i'm not a linux kernel
developer to take any type of decisions :P
PS : I'v don't really understand what is the problem with the APIC support
?!
Best regards,
Vergoz Michael
From: "Jeff Garzik" <jgarzik@pobox.com>
To: "Ducrot Bruno" <poup@poupinou.org>
Cc: "Vergoz Michael" <mvergoz@sysdoor.com>; "Linux Kernel Mailing List"
<linux-kernel@vger.kernel.org>
Sent: Monday, November 18, 2002 6:25 PM
Subject: Re: 8139too.c patch for kernel 2.4.19
> Ducrot Bruno wrote:
>
> > On Mon, Nov 18, 2002 at 09:50:50AM +0100, Vergoz Michael wrote:
> >
> > >Hi Jeff,
> > >
> > >What i see is the current driver _doesn't_ work on my realtek 8139C.
> > >With this one it work fine.
> >
> >
> > The question was (as I understand the changes you made and the
> > answer from Jeff) : did your card work with 8139cp or not?
> >
> > If not, you have to modify 8139cp, which is the right place for C+
> > support.
>
>
>
> Agreed. However from the above quoted, "8139C" chip would indicate that
> he needs to use 8139too not 8139cp.
>
> I am hoping (please!) that Michael will post some info that will help us
> debug his problem.
>
> Regards,
>
> Jeff
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2002-11-18 17:44 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-18 2:49 8139too.c patch for kernel 2.4.19 Vergoz Michael
2002-11-18 7:34 ` Jeff Garzik
2002-11-18 8:50 ` Vergoz Michael
2002-11-18 17:04 ` Ducrot Bruno
2002-11-18 9:05 ` Jeff Garzik
2002-11-18 11:17 ` Andreas Steinmetz
2002-11-18 15:55 ` Jeff Garzik
2002-11-18 16:12 ` Andreas Steinmetz
2002-11-18 16:47 ` Jeff Garzik
2002-11-18 17:25 ` Jeff Garzik
2002-11-18 17:51 ` Vergoz Michael [this message]
2002-11-18 18:14 ` Jeff Garzik
2002-11-18 20:04 ` Vergoz Michael
2002-11-18 21:15 ` Jeff Garzik
2002-11-18 21:34 ` Jeff Garzik
-- strict thread matches above, loose matches on Subject: below --
2002-11-18 17:15 Manfred Spraul
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='001901c28f2b$2f3540a0$76405b51@romain' \
--to=mvergoz@sysdoor.com \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.org \
--cc=poup@poupinou.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