From: Chase Douglas <chase.douglas@canonical.com>
To: "Luis R. Rodriguez" <mcgrof@gmail.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: Wed, 24 Feb 2010 09:54:09 -0500 [thread overview]
Message-ID: <1267023249.32025.26.camel@cndougla-ubuntu> (raw)
In-Reply-To: <43e72e891002231646w269a1132i505ca5c21ab22bc@mail.gmail.com>
> > 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.
We've decided to keep things as is from Karmic to Lucid in an effort to
not screw things up for people who already have their wireless working.
This means we'll be shipping both prism54 and p54* drivers.
I have uploaded a new linux-firmware-nonfree package that contains all
the prism54 firmware for all the drivers:
http://kernel.ubuntu.com/~cndougla/linux-firmware-nonfree/
Thanks,
Chase
prev parent reply other threads:[~2010-02-24 14:54 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
2010-02-24 14:54 ` Chase Douglas [this message]
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=1267023249.32025.26.camel@cndougla-ubuntu \
--to=chase.douglas@canonical.com \
--cc=alan@lxorguk.ukuu.org.uk \
--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 \
--cc=mcgrof@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
all inboxes | Powered by JetHome®