From: Xose Vazquez Perez <xose.vazquez@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: linux-wireless <linux-wireless@vger.kernel.org>,
users@rt2x00.serialmonkey.com, IvDoorn@gmail.com
Subject: Re: [PATCH] rt2800pci.c : more ids
Date: Tue, 13 Oct 2009 14:12:09 +0200 [thread overview]
Message-ID: <4AD46E99.4040008@gmail.com> (raw)
In-Reply-To: <4AD434B6.3090903@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 498 bytes --]
On 10/13/2009 10:05 AM, Xose Vazquez Perez wrote:
> stolen from windows inf file(09/05/2009, 1.04.07.0000)
>
> 0x1814, 0x3060
apply this one instead,
got 0x1462,0x89a from linux driver(2009_0903_RT3090_Linux_STA_v2.2.0.1)
-thanks-
--
«Allá muevan feroz guerra, ciegos reyes por un palmo más de tierra;
que yo aquí tengo por mío cuanto abarca el mar bravío, a quien nadie
impuso leyes. Y no hay playa, sea cualquiera, ni bandera de esplendor,
que no sienta mi derecho y dé pecho a mi valor.»
[-- Attachment #2: new_id-2800pci-v2.diff --]
[-- Type: text/plain, Size: 1273 bytes --]
--- o/drivers/net/wireless/rt2800pci.c 2009-10-13 09:57:37.523379731 +0200
+++ n/drivers/net/wireless/rt2800pci.c 2009-10-13 14:10:12.785378782 +0200
@@ -3225,6 +3225,8 @@
* RT2800pci module information.
*/
static struct pci_device_id rt2800pci_device_table[] = {
+ /* ??? */
+ { PCI_DEVICE(0x1462, 0x891a), PCI_DEVICE_DATA(&rt2800pci_ops) },
/* Edimax */
{ PCI_DEVICE(0x1432, 0x7708), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1432, 0x7727), PCI_DEVICE_DATA(&rt2800pci_ops) },
@@ -3233,10 +3235,12 @@
{ PCI_DEVICE(0x1432, 0x7748), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1432, 0x7758), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1432, 0x7768), PCI_DEVICE_DATA(&rt2800pci_ops) },
+ /* Ralink */
{ PCI_DEVICE(0x1814, 0x0601), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1814, 0x0681), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1814, 0x0701), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1814, 0x0781), PCI_DEVICE_DATA(&rt2800pci_ops) },
+ { PCI_DEVICE(0x1814, 0x3060), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1814, 0x3062), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1814, 0x3090), PCI_DEVICE_DATA(&rt2800pci_ops) },
{ PCI_DEVICE(0x1814, 0x3091), PCI_DEVICE_DATA(&rt2800pci_ops) },
next prev parent reply other threads:[~2009-10-13 12:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-13 8:05 [PATCH] rt2800pci.c : more ids Xose Vazquez Perez
2009-10-13 12:12 ` Xose Vazquez Perez [this message]
2009-10-19 9:50 ` Xose Vazquez Perez
2009-10-19 17:31 ` Ivo van Doorn
2009-10-28 19:44 ` [rt2x00-users] " John W. Linville
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=4AD46E99.4040008@gmail.com \
--to=xose.vazquez@gmail.com \
--cc=IvDoorn@gmail.com \
--cc=linux-wireless@vger.kernel.org \
--cc=users@rt2x00.serialmonkey.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).