From: "Luis R. Rodriguez" <mcgrof@gmail.com>
To: Chase Douglas <chase.douglas@canonical.com>
Cc: Ubuntu Kernel Team <kernel-team@lists.ubuntu.com>,
Christian Lamparter <chunkeey@web.de>,
"John W. Linville" <linville@tuxdriver.com>,
debian-kernel@lists.debian.org, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>
Subject: Re: linux-firmware-nonfree: Add prism54 softmac firmware
Date: Tue, 23 Feb 2010 16:46:26 -0800 [thread overview]
Message-ID: <43e72e891002231646w269a1132i505ca5c21ab22bc@mail.gmail.com> (raw)
In-Reply-To: <1266956239.26106.11.camel@cndougla-ubuntu>
On Tue, Feb 23, 2010 at 12:17 PM, Chase Douglas
<chase.douglas@canonical.com> wrote:
> On Tue, 2010-02-23 at 12:02 -0800, Luis R. Rodriguez wrote:
>> On Tue, Feb 23, 2010 at 7:47 AM, Chase Douglas
>> <chase.douglas@canonical.com> wrote:
>> > I have uploaded a new version of the linux-firmware-nonfree package to:
>> >
>> > http://kernel.ubuntu.com/~cndougla/linux-firmware-nonfree/
>> >
>> > The new package includes the firmware for prism54 softmac cards. The firmware
>> > was removed from linux-firmware due to it missing a proper license statement. I
>> > did not copy over the old prism54 (non-softmac) firmware because it has been
>> > superseded by the softmac firmware and is no longer useful in the Lucid kernel
>> > version.
>>
>> Hey is PRISM54 no longer compiled in a module any more? I had set it
>> for removal on the feature removal schedule but I wanted to give you
>> the heads up we've received a few reports of users unable to use
>> prism54 over p54pci. It was theorized this would happen but we didn't
>> have any confirmation, which is why we just didn't remove it.
>>
>> How would you guys deal with having both enabled.
>
> Thanks for looking into this. I was going off of [1], which stated that
> the debian kernel does not include the prism54 module anymore.
Fun, passing this as a memo to lkml/Debian -- p54pci doesn't seem to
work well for *all* Prism54 FullMAC cards. They technically are the
same and the SoftMAC functionality was possible through a smaller
firmware. But it seems some cards have issues still with p54pci so I
would still enable prism54 as a module but not sure what to recommend
about dealing with two modules on the system for the same device.
> I checked
> the lucid kernel and we do have prism54 built as a module still. So, are
> we going to leave the prism54 module in, in which case we need to
> restore the prism54 firmware?
Yes I'd restore the prism54 firmware until the coast is clear with
p54pci for all. Its not the case so far as per reports.
> Or are we going to remove it, in which
> case the firmware package I uploaded was fine? I'm assuming at this
> point we'll be leaving it in though.
I'd say keep it for now.
> Andy, do you have any thoughts here?
>
> [1] http://wiki.debian.org/prism54
Luis
next parent reply other threads:[~2010-02-24 0:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4B83F8A1.8050503@canonical.com>
[not found] ` <43e72e891002231202t166ff48ewb67c45863682732f@mail.gmail.com>
[not found] ` <1266956239.26106.11.camel@cndougla-ubuntu>
2010-02-24 0:46 ` Luis R. Rodriguez [this message]
2010-02-24 14:54 ` Chase Douglas
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=43e72e891002231646w269a1132i505ca5c21ab22bc@mail.gmail.com \
--to=mcgrof@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=chase.douglas@canonical.com \
--cc=chunkeey@web.de \
--cc=debian-kernel@lists.debian.org \
--cc=kernel-team@lists.ubuntu.com \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®