From: Dan Williams <dcbw@redhat.com>
To: Daniel Drake <dsd@laptop.org>
Cc: Andres Salomon <dilinger@queued.net>,
David Woodhouse <dwmw2@infradead.org>,
cjb@laptop.org, linux-kernel@vger.kernel.org,
libertas-dev@lists.infradead.org
Subject: Re: [GIT PULL linux-firmware.git] OLPC libertas firmware blobs
Date: Mon, 20 Jun 2011 23:47:13 -0500 [thread overview]
Message-ID: <1308631634.31157.7.camel@dcbw.foobar.com> (raw)
In-Reply-To: <BANLkTimyFj+iTWAopPMEyohP2pop_=g=6g@mail.gmail.com>
On Sun, 2011-06-19 at 10:41 +0100, Daniel Drake wrote:
> On 19 June 2011 05:42, Andres Salomon <dilinger@queued.net> wrote:
> >> LICENCE.OLPC | 33 +++++++++++++++++++++++++++++++++
> >> WHENCE | 20 ++++++++++++++++++++
> >> libertas/lbtf_sdio.bin | Bin 0 -> 120924 bytes
> >> libertas/lbtf_usb.bin | Bin 0 -> 118888 bytes
> >> libertas/sd8686_v9_OLPC.bin | Bin 0 -> 124244 bytes
> >> libertas/usb8388_v5_OLPC.bin | Bin 0 -> 127824 bytes
> >
> > Of course, if people would prefer the OLPC version to supersede the
> > ones currently in the linux-firmware tree, I can do that instead. I
> > don't know what versions of sd8686.bin and usb8388.bin are actually in
> > the tree. I also don't know if the OLPC versions improve or make things
> > worse for people using those chips on non-OLPC systems.
>
> This overlaps with a submission I made the other day (of usb8388
> firmware), sorry for the lack of coordination there.
>
> I don't think the OLPC hardware has any quirks or special features
> that mean it requires special firmware.
>
> However, for the usb8388 we do use a special firmware developed by
> Cozybit (not Marvell), the one you submitted, which has its own
> versioning scheme. The main difference is that it includes mesh
> support. I am pretty sure it would run on any usb8388 but OLPC is the
> only user of the hardware anyway. See
> http://lists.infradead.org/pipermail/libertas-dev/2010-November/003330.html
> and the rest of the discussion.
>
> As for sd8686, I thought our firmware was standard, from Marvell, and
> simply a newer version of what is in linux-firmware. Do you have
> reason to believe otherwise?
For usb8388 I don't think we really care which firmware is default since
OLPC was about the only consumer of that chip that I've ever heard of.
For the other firmware I periodically trawled Marvell's Extranet and
grabbed latest firmware from there. If you guys have a newer micro
version of the firmware then great, push it. Latest I have access to
for 8686 is SD-8686-FEDORA26FC6-SYSKT-9.70.20.p0-26409.p64 so if you've
got something newer great.
Dan
next prev parent reply other threads:[~2011-06-21 4:44 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-19 4:38 [GIT PULL linux-firmware.git] OLPC libertas firmware blobs Andres Salomon
2011-06-19 4:42 ` Andres Salomon
2011-06-19 9:41 ` Daniel Drake
2011-06-19 18:11 ` Andres Salomon
2011-06-21 4:47 ` Dan Williams [this message]
2011-06-21 7:18 ` Andres Salomon
2011-06-21 8:05 ` Daniel Drake
2011-06-23 13:42 ` Daniel Drake
2011-07-09 23:48 ` Marek Vasut
2011-07-09 23:50 ` Marek Vasut
2011-07-11 23:37 ` Dan Williams
2011-07-11 23:59 ` Dan Williams
2011-07-12 0:04 ` Marek Vasut
2011-07-12 0:30 ` Dan Williams
2011-07-29 22:17 ` David Woodhouse
2011-07-30 17:13 ` Andres Salomon
2011-06-19 4:51 ` [PATCH linux-firmware] libertas: add OLPC libertas blobs Andres Salomon
-- strict thread matches above, loose matches on Subject: below --
2011-07-31 5:50 [GIT PULL linux-firmware.git] OLPC libertas firmware blobs Andres Salomon
2011-07-31 12:58 ` Daniel Drake
2011-07-31 17:00 ` Andres Salomon
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=1308631634.31157.7.camel@dcbw.foobar.com \
--to=dcbw@redhat.com \
--cc=cjb@laptop.org \
--cc=dilinger@queued.net \
--cc=dsd@laptop.org \
--cc=dwmw2@infradead.org \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-kernel@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