From: "Gábor Stefanik" <netrolller.3d@gmail.com>
To: "John W. Linville" <linville@tuxdriver.com>
Cc: Cyrille <cyrille@cbiot.fr>,
b43-dev@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: problem with b43
Date: Fri, 24 Sep 2010 19:30:56 +0200 [thread overview]
Message-ID: <AANLkTinxr6avpgR9v3nBaNp8nSORFkStDcOsL2KW0-Ln@mail.gmail.com> (raw)
In-Reply-To: <20100924172132.GC8077@tuxdriver.com>
2010/9/24 John W. Linville <linville@tuxdriver.com>:
> On Fri, Sep 24, 2010 at 07:06:17PM +0200, G?bor Stefanik wrote:
>> On Fri, Sep 24, 2010 at 6:55 PM, Cyrille <cyrille@cbiot.fr> wrote:
>> > Hi
>> > I've got a problem with a broadcom 4312 [12e4:4315].
>> > The environment :
>> > ===========================
>> > uname -a
>> > 2.6.35.5-libre.29.fc14.x86_64
>
>> > Broadcom 43xx driver loaded [ Features: PMLS, Firmware-ID: FW13 ]
>> > ssb0:0: Missing Free firmware
>> > b43-phy4 ERROR: Rejected non-Free firmware
>> > ssb0:0: Missing Free firmware
>> > b43-phy4 ERROR: Rejected non-Free firmware
>>
>> Compile compat-wireless to bypass the "free-only" patch in Fedora.
>>
>> (John, are you still maintaining the Fedora kernel's wireless part? If
>> so, please kill this "freedom enforcement"!)
>
> This isn't a Fedora kernel. ?I'm guessing it is from "Free-dora"
> by way of BLAG, and I have no control over it -- sorry.
>
> Cyrille, did you try b43-openfwwf? ?If that doesn't work, then you
> will need to use extracted proprietary firmware with some other kernel
> (e.g. stock Fedora) or you will have to live without b43.
OpenFWWF definitely won't work with LP-PHYs. We don't even know enough
about LP-PHY to fix the DMA error, let alone to write our own
firmware...
>
> John
> --
> John W. Linville ? ? ? ? ? ? ? ?Someday the world will need a hero, and you
> linville at tuxdriver.com ? ? ? ? ? ? ? ? ?might be all we have. ?Be ready.
>
--
Vista: [V]iruses, [I]ntruders, [S]pyware, [T]rojans and [A]dware. :-)
next prev parent reply other threads:[~2010-09-24 17:30 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-24 16:55 problem with b43 Cyrille
2010-09-24 17:06 ` Gábor Stefanik
2010-09-24 17:21 ` John W. Linville
2010-09-24 17:30 ` Gábor Stefanik [this message]
2010-09-24 17:43 ` Michael Büsch
2010-09-24 17:39 ` Cyrille
2010-09-24 17:10 ` Rafał Miłecki
[not found] ` <20100924191547.59c58e7b.cyrille@cbiot.fr>
2010-09-24 17:28 ` Rafał Miłecki
2010-09-24 17:32 ` Cyrille
2010-09-24 17:46 ` Rafał Miłecki
2010-09-24 18:32 ` Cyrille
2010-09-24 18:39 ` Peter Stuge
2010-09-24 19:28 ` Nicolas de Pesloüan
-- strict thread matches above, loose matches on Subject: below --
2010-05-31 21:45 Problem " Fabrizio Regalli
2010-06-01 2:17 ` William Bourque
2010-06-01 8:39 ` Martino Salvetti
2010-06-20 12:04 ` Fabrizio Regalli
2010-06-20 18:12 ` Gábor Stefanik
[not found] ` <AANLkTimpDoxIjIBVOPug5uLADaV5oX6RX8se9VC1x6Pd@mail.gmail.com>
2010-06-21 23:22 ` Gábor Stefanik
2010-06-22 15:09 ` Larry Finger
2010-06-22 18:54 ` Fabrizio Regalli
2010-06-22 19:46 ` Larry Finger
2010-06-22 20:40 ` Fabrizio Regalli
2010-06-24 21:50 ` Fabrizio Regalli
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=AANLkTinxr6avpgR9v3nBaNp8nSORFkStDcOsL2KW0-Ln@mail.gmail.com \
--to=netrolller.3d@gmail.com \
--cc=b43-dev@lists.infradead.org \
--cc=cyrille@cbiot.fr \
--cc=linux-wireless@vger.kernel.org \
--cc=linville@tuxdriver.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).