public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@pobox.com>
To: Mike Dresser <mdresser_l@windsormachine.com>
Cc: list linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: RTL8139D support for 2.4?
Date: Mon, 18 Nov 2002 17:41:28 -0500	[thread overview]
Message-ID: <3DD96C98.7020508@pobox.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0211181731040.1796-100000@router.windsormachine.com>

Mike Dresser wrote:

> On Mon, 18 Nov 2002, Jeff Garzik wrote:
>
>
> >this is a toughie...   basically that is an invalid PCI ID that should
> >not occur.  the "00ec" should really be "10ec", but it sounds like there
> >is a missing bit in the EEPROM where your card's PCI ID is stored.
>
>
> I'll try another card, and get back to you, just in case it's a
> partially fubar card.


FWIW I have seen tons of 8139s that work fine but have invalid PCI 
IDs... the price of being a US$0.50 chip I guess :)

So I doubt it's a fubar card...


> >A better patch would add
> >
> >	{ 0x00ec, 0x8139, 0xa0a0, 0x0027, ... }
>
>
> True true, until Aopen plays games with PCI ID's again :)


exactly... :/


> Never said i was a programmer :)  More of a hacker in the traditional
> sense.  Nano is my hammer, all .c code is nails.


hehe

>
>
> >>I left the D card in my workstation for now, I'll see how it handles the
> >>nightly backup tonight, and if you want me to test things for 8139cp
> >
> >cool.  no need to test 8139cp, it won't even load with your card, since
> >it is not an 8139C+ chip.
>
>
> Ok.  I take it the C+ has functions that weren't carried over to D?


8139C+ is, in CVS lingo, a branch.  8139D has -none- of the 8139C+ 
functions...

> >>What IS pci-skeleton then?
> >
> >Example driver that other developers may base drivers off of...
>
> Or feed to the Penguin.  Hey, you said red herring :D



hehe :)

	Jeff




  reply	other threads:[~2002-11-18 22:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-18  9:38 RTL8139D support for 2.4? Eyal Lebedinsky
2002-11-18 18:30 ` Jeff Garzik
2002-11-18 19:32   ` Ducrot Bruno
2002-11-18 19:48 ` Jeff Garzik
2002-11-18 21:13   ` Mike Dresser
2002-11-18 21:21     ` Jeff Garzik
2002-11-18 22:02       ` Mike Dresser
2002-11-18 22:13         ` Jeff Garzik
2002-11-18 22:16           ` Mike Dresser
2002-11-18 22:24             ` Jeff Garzik
2002-11-18 22:33               ` Mike Dresser
2002-11-18 22:41                 ` Jeff Garzik [this message]
2002-11-18 22:50                   ` Mike Dresser
2002-11-18 22:57               ` Mike Dresser
2002-11-19  0:34                 ` Val Henson
2002-11-19 12:15               ` Dave Jones

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=3DD96C98.7020508@pobox.com \
    --to=jgarzik@pobox.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mdresser_l@windsormachine.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