linux-wireless.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ivo van Doorn <ivdoorn@gmail.com>
To: users@rt2x00.serialmonkey.com
Cc: Simon Raffeiner <sturmflut@lieberbiber.de>,
	linux-wireless@vger.kernel.org,
	Xose Vazquez Perez <xose.vazquez@gmail.com>
Subject: Re: [rt2x00-users] [PATCH 2/2] rt2x00: Implement support for rt2800pci
Date: Fri, 16 Oct 2009 12:55:54 +0200	[thread overview]
Message-ID: <200910161255.54644.IvDoorn@gmail.com> (raw)
In-Reply-To: <200910161149.11661.sturmflut@lieberbiber.de>

Hi,

> I was comparing rt2800pci and the INF file of the original RT2860 windows 
> driver out curiosity. The original INF file contains 108 PCI id entries, 
> rt2800pci.c only 20. At first I thought that an entry like 
> 
> PCI\VEN_1814&DEV_0601&SUBSYS_77281432
> 
> (Edimax card) in the INF file will be automatically matched by rt2800pci for 
> the "1814:0601" vendor/device id, but then I found an additional entry for 
> "1432:7728" (the susbsystem id) in the rt2800pci pci_device_id table. 
> 
> I am a bit confused: Should every entry from the INF file have a PCI_DEVICE() 
> counterpart in our driver (resulting in 108 entries), or is this a special 
> case where the Manufacturer (Edimax) produces cards that actually have 
> "1432:7728" as vendor/device id.
> 
> You can probably tell that I don't have much experience developing kernel 
> drivers, but I am willing to get it right.

Well the main PCI and DEVICE id's should be listed in the PCI_DEVICE table,
the SUBSYS ID should only be added in case there can be different drivers
based on that ID.

As far as the ID 1432:7728, that one was send by Xose who got the ID from
the Windows driver, I don't know if he has mistakenly grabbed the subsystem ID or not...
Xose, could you give an update about this?

Ivo

  reply	other threads:[~2009-10-16 10:56 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <200910152137.58164.IvDoorn@gmail.com>
2009-10-15 20:04 ` [PATCH 2/2] rt2x00: Implement support for rt2800pci Ivo van Doorn
2009-10-16  9:49   ` Simon Raffeiner
2009-10-16 10:55     ` Ivo van Doorn [this message]
2009-10-16 11:12       ` [rt2x00-users] " Xose Vazquez Perez
2009-10-16 12:13         ` Simon Raffeiner
2009-10-17 14:54   ` Bartlomiej Zolnierkiewicz
2009-10-17 15:08     ` Johannes Berg
2009-10-17 15:19       ` Bartlomiej Zolnierkiewicz
2009-10-17 21:18     ` Bartlomiej Zolnierkiewicz
2009-10-18  9:40       ` Luis Correia
2009-10-18  3:08     ` Julian Calaby
2009-10-18 16:59     ` Ivo van Doorn
2009-10-19 15:56       ` Bartlomiej Zolnierkiewicz
2009-10-19 17:42         ` Ivo van Doorn
2009-10-20  6:58       ` Holger Schurig
2009-10-20 16:31         ` Ivo van Doorn

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=200910161255.54644.IvDoorn@gmail.com \
    --to=ivdoorn@gmail.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=sturmflut@lieberbiber.de \
    --cc=users@rt2x00.serialmonkey.com \
    --cc=xose.vazquez@gmail.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).