From: Lennert Buytenhek <buytenh@wantstofly.org>
To: Sedat Dilek <sedat.dilek@googlemail.com>
Cc: "John W. Linville" <linville@tuxdriver.com>,
linux-wireless@vger.kernel.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org, Sedat Dilek <sedat.dilek@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] mwl8k: Add 0x2a02 PCI device-id (Marvell 88W8361)
Date: Fri, 27 Apr 2012 11:14:05 +0200 [thread overview]
Message-ID: <20120427091405.GS3157@wantstofly.org> (raw)
In-Reply-To: <1335517711-6522-1-git-send-email-sedat.dilek@gmail.com>
On Fri, Apr 27, 2012 at 11:08:31AM +0200, Sedat Dilek wrote:
> User lautriv asked for belkin N-1 WLAN device support on IRC.
>
> Further informations from lautriv:
> * marvell 80W8031, card-id 11ab:2a02
> * Debian/sid 3.2.x
>
> On [1] I found a report by Jim Cromie concerning same PCI device-id:
>
> 00:0e.0 Ethernet controller [0200]: Marvell Technology Group Ltd.
> 88W8361 [TopDog] 802.11n Wireless [11ab:2a02] (rev 03)
> Subsystem: Marvell Technology Group Ltd. 88W8361 [TopDog] 802.11n Wireless [11ab:2a02]
>
> So, let's add 0x2a02 to PCI device table.
Let's not. There's no firmware for the 8361 that implements the
firmware interface currently implemented by the mwl8k driver, so
this is pretty useless.
> [1] http://www.spinics.net/lists/newbies/msg46601.html
>From that link:
| I have a card which modprobes, despite a PCI-ID mismatch
|
| [...]
|
| Given the pci-id mismatch shouldnt this just fail to modprobe ?
No. That's not a bug -- you are free to load drivers for hardware
not currently in your system.
> static DEFINE_PCI_DEVICE_TABLE(mwl8k_pci_id_table) = {
> + { PCI_VDEVICE(MARVELL, 0x2a02), .driver_data = MWL8363, },
> { PCI_VDEVICE(MARVELL, 0x2a0a), .driver_data = MWL8363, },
A 8361 is certainly not a 8363.
next prev parent reply other threads:[~2012-04-27 9:14 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 9:08 Sedat Dilek
2012-04-27 9:14 ` Lennert Buytenhek [this message]
2012-04-27 9:22 ` Sedat Dilek
2012-04-27 9:40 ` Lennert Buytenhek
2012-04-27 9:42 ` Sedat Dilek
2012-04-27 9:46 ` Lennert Buytenhek
2012-04-27 9:56 ` Sedat Dilek
2012-04-27 9:58 ` Lennert Buytenhek
2012-04-27 10:12 ` Sedat Dilek
2012-04-27 10:17 ` Lennert Buytenhek
2012-04-27 10:57 ` Sedat Dilek
2012-04-27 13:29 ` Sedat Dilek
2012-04-27 18:58 ` Lennert Buytenhek
2012-04-27 21:53 ` Sedat Dilek
2012-04-28 22:25 ` Sedat Dilek
2012-05-01 12:51 ` Lennert Buytenhek
2012-05-01 13:54 ` Sedat Dilek
2012-05-01 15:49 ` Lennert Buytenhek
2012-05-02 1:12 ` Pat Erley
2012-05-02 2:38 ` Lennert Buytenhek
2012-05-02 8:58 ` Sedat Dilek
2012-05-02 7:59 ` Arend van Spriel
2012-05-02 13:53 ` Ben Hutchings
2012-05-07 16:09 ` Dan Williams
2012-05-07 16:42 ` Dan Williams
2012-05-07 18:26 ` Adrian Chadd
2012-05-11 8:01 ` Helmut Stengele
2012-05-01 12:47 ` Lennert Buytenhek
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=20120427091405.GS3157@wantstofly.org \
--to=buytenh@wantstofly.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.com \
--cc=netdev@vger.kernel.org \
--cc=sedat.dilek@gmail.com \
--cc=sedat.dilek@googlemail.com \
--cc=stable@vger.kernel.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
Powered by JetHome