From: Michael Buesch <mb@bu3sch.de>
To: Xose Vazquez Perez <xose.vazquez@gmail.com>
Cc: Larry Finger <Larry.Finger@lwfinger.net>, linux-wireless@vger.kernel.org
Subject: Re: Fwd: b43* linux driver, more ids dev
Date: Fri, 27 Feb 2009 20:19:08 +0100 [thread overview]
Message-ID: <200902272019.08275.mb@bu3sch.de> (raw)
In-Reply-To: <49A83BC5.2020204@gmail.com>
On Friday 27 February 2009 20:15:17 Xose Vazquez Perez wrote:
> Larry Finger wrote:
>
> > Xose Vazquez Perez wrote:
> >
> >> are there any trouble with these devices ? why are they not inside
> >> b43* drivers ?
> >>
> >> PCI_VENDOR_ID_BROADCOM, 0x4313
> >> PCI_VENDOR_ID_BROADCOM, 0x4315
> >> PCI_VENDOR_ID_BROADCOM, 0x432a
> >> PCI_VENDOR_ID_BROADCOM, 0x432b
> >> PCI_VENDOR_ID_BROADCOM, 0x432c
> >> PCI_VENDOR_ID_BROADCOM, 0x432d
> >
> > Those devices are either LP PHY (4315 and probably 4313) or N PHY (432X)
> > devices. The reverse engineering for the LP PHY was just completed, but the code
> > is not yet written. The RE for the N PHY has barely begun.
> >
> > Once there is code to drive those devices, their ID's will be added.
>
> It smells like another crap_driver for staging tree.
>
No it doesn't. It is closed source.
Please read the documentation before posting the next mail. Thanks.
--
Greetings, Michael.
next prev parent reply other threads:[~2009-02-27 19:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ee588a540902270946h13e03b6el71de5237a458b7a3@mail.gmail.com>
2009-02-27 17:55 ` Fwd: b43* linux driver, more ids dev Xose Vazquez Perez
2009-02-27 18:41 ` John W. Linville
2009-02-27 18:56 ` Larry Finger
2009-02-27 19:15 ` Xose Vazquez Perez
2009-02-27 19:19 ` Michael Buesch [this message]
2009-02-27 19:31 ` Xose Vazquez Perez
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=200902272019.08275.mb@bu3sch.de \
--to=mb@bu3sch.de \
--cc=Larry.Finger@lwfinger.net \
--cc=linux-wireless@vger.kernel.org \
--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).