From: Andres Salomon <dilinger@queued.net>
To: Dan Williams <dcbw@redhat.com>
Cc: Daniel Drake <dsd@laptop.org>,
cjb@laptop.org, David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: [PATCH] libertas: prioritize usb8388_v5.bin firmware on OLPC machines
Date: Mon, 1 Aug 2011 11:25:22 -0700 [thread overview]
Message-ID: <20110801112522.1ba02f5e@debxo> (raw)
In-Reply-To: <1312219075.6121.20.camel@dcbw.foobar.com>
On Mon, 01 Aug 2011 12:17:23 -0500
Dan Williams <dcbw@redhat.com> wrote:
> On Sun, 2011-07-31 at 13:59 +0100, Daniel Drake wrote:
> > On 31 July 2011 08:05, Andres Salomon <dilinger@queued.net> wrote:
> > > Note: I've not tested this out yet on an XO-1. I'll do that
> > > after some feedback regarding the matching linux-firmware pull
> > > request. This should address dsd's concern about changing the
> > > loading order of the firmware.
> >
> > That indeed was a concern, but only until Dan Williams and Chris
> > pointed out that OLPC is the only usb8388 user. With that in mind, I
> > am in agreement with them that simply putting usb8388_olpc_v5.bin
> > (or whatever name is chosen) at the top of the firmware loading
> > list is the best option.
>
> Yeah, patches for that would be immediately acked.
>
What's your opinion on overwriting usb8388_v5.bin with OLPC's version,
versus having both a usb8388_v5.bin and a usb8388_olpc_v5.bin?
next prev parent reply other threads:[~2011-08-01 18:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-31 7:03 [PATCH] libertas: prioritize usb8388_v5.bin firmware on OLPC machines Andres Salomon
2011-07-31 7:05 ` Andres Salomon
2011-07-31 12:59 ` Daniel Drake
2011-08-01 17:17 ` Dan Williams
2011-08-01 18:25 ` Andres Salomon [this message]
2011-08-01 21:20 ` Dan Williams
2011-08-03 6:37 ` 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=20110801112522.1ba02f5e@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