public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <shemminger@osdl.org>
To: "Thomas Bogendörfer" <tsbogend@alpha.franken.de>,
	"Jeff Garzik" <jgarzik@pobox.com>
Cc: netdev@vger.kernel.org, linux-pcmcia@lists.infradead.org
Subject: Dlink PCI/PCMCIA  id conflicts
Date: Wed, 30 Aug 2006 15:37:38 -0700	[thread overview]
Message-ID: <20060830153738.0bc23c98@localhost.localdomain> (raw)

It appears that the Dlink DGE-550SX card has this pci_id:
	vendor = 0x1186, device = 0x4001
(decoded from SysKonnect version of sk98lin driver).

According to a couple of places Dlink also uses the same id for the DFE-650TX
card.  Before I add this to the sky2 driver, I want to make sure not to break
existing users of the other card. 

Does the pcmcia code end up overlapping the pci on this?

Alternatively, we need to use the version id to disambiguate which was
done already for another Dlink card.  That would mean finding people with
all the versions of the cards to decode what to put in the table (yuck).


-- 
Stephen Hemminger <shemminger@osdl.org>

                 reply	other threads:[~2006-08-30 22:41 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=20060830153738.0bc23c98@localhost.localdomain \
    --to=shemminger@osdl.org \
    --cc=jgarzik@pobox.com \
    --cc=linux-pcmcia@lists.infradead.org \
    --cc=netdev@vger.kernel.org \
    --cc=tsbogend@alpha.franken.de \
    /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