From: James Cameron <quozl@laptop.org>
To: Vasily Khoruzhick <anarsoul@gmail.com>
Cc: Dan Williams <dcbw@redhat.com>,
Andreas Kemnade <andreas@kemnade.info>,
linux-wireless@vger.kernel.org, libertas-dev@lists.infradead.org
Subject: Re: status of libertas_tf + sdio?
Date: Tue, 10 Dec 2013 13:27:46 +1100 [thread overview]
Message-ID: <20131210022746.GE28975@us.netrek.org> (raw)
In-Reply-To: <CA+E=qVd_F_=z5Vb2jan-nNVmizQznOiR=98CPHQevMxbnxGJiA@mail.gmail.com>
On Mon, Dec 09, 2013 at 12:38:28PM +0300, Vasily Khoruzhick wrote:
> On Mon, Dec 9, 2013 at 7:18 AM, James Cameron <quozl@laptop.org> wrote:
> > On Fri, Dec 06, 2013 at 01:40:00PM +0300, Vasily Khoruzhick wrote:
> >> Out of curiosity,
> >>
> >> Does anyone know if it's possible to get thin firmware for 8686 with
> >> SPI interface?
> >
> > What happens when you try?
>
> How? There's no tf available for 8686 with SPI interface.
How do you know that? Are you saying that SPI support was removed
from firmware during the conversion from fat to thin?
> > How are you downloading firmware over SPI?
>
> See drivers/net/wireless/libertas/if_spi.c, but it's for fat
> firmware
What happens if you send the thin firmware instead?
> > I'm not aware of a second stage firmware download helper specific to
> > the SPI mode.
>
> What's a second stage firmware download helper?
File sd8686_helper.bin, we use it in Open Firmware with SDIO 8686 on
OLPC XO.
For SPI, which we don't use, I see if_spi.c uses gspi8686_v9_helper.bin
I was wrong; I am now aware of a second stage firmware downloader
helper specific to the SPI mode. I hadn't looked before.
> > I think it is not possible without firmware engineering.
>
> Yeah, just hoped that Marvell already did it. It's a pity that
> firmware source code isn't available :(
Cozybit did the thin firmware, if I recall correctly.
--
James Cameron
http://quozl.linux.org.au/
next prev parent reply other threads:[~2013-12-10 2:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-03 19:26 status of libertas_tf + sdio? Andreas Kemnade
2013-12-04 14:36 ` Dan Williams
2013-12-06 10:40 ` Vasily Khoruzhick
2013-12-09 4:18 ` James Cameron
2013-12-09 9:38 ` Vasily Khoruzhick
2013-12-10 2:27 ` James Cameron [this message]
2013-12-11 8:10 ` Vasily Khoruzhick
2013-12-11 20:55 ` James Cameron
2013-12-11 21:21 ` Vasily Khoruzhick
2013-12-11 22:41 ` Dan Williams
2013-12-27 21:30 ` Steve deRosier
2013-12-28 7:40 ` Vasily Khoruzhick
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=20131210022746.GE28975@us.netrek.org \
--to=quozl@laptop.org \
--cc=anarsoul@gmail.com \
--cc=andreas@kemnade.info \
--cc=dcbw@redhat.com \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-wireless@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