public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andres Salomon <dilinger@queued.net>
To: Daniel Drake <dsd@laptop.org>
Cc: David Woodhouse <dwmw2@infradead.org>,
	cjb@laptop.org, linux-kernel@vger.kernel.org, dcbw@redhat.com,
	libertas-dev@lists.infradead.org
Subject: Re: [GIT PULL linux-firmware.git] OLPC libertas firmware blobs
Date: Sun, 19 Jun 2011 11:11:27 -0700	[thread overview]
Message-ID: <20110619111127.005064d0@debxo> (raw)
In-Reply-To: <BANLkTimyFj+iTWAopPMEyohP2pop_=g=6g@mail.gmail.com>

On Sun, 19 Jun 2011 10:41:22 +0100
Daniel Drake <dsd@laptop.org> 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.

Ah, sorry, I didn't know you were on top of this.  I'm wanting to
kill off the Debian OLPC-specific libertas package, and finally found
some time to put together a pull request.

> 
> 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?
> 

I was just playing it safe.  I have changelogs for the usb8388 firmware
releases, but not for sd8686.  I'll defer to you for XO-1.5 stuff.

I'm more interested in the lbtf stuff anyways, as I don't see much use
for the on-chip mesh.

  reply	other threads:[~2011-06-19 18:11 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 [this message]
2011-06-21  4:47     ` Dan Williams
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=20110619111127.005064d0@debxo \
    --to=dilinger@queued.net \
    --cc=cjb@laptop.org \
    --cc=dcbw@redhat.com \
    --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