From: Matt Fleming <matt@console-pimps.org>
To: Andreas Feuersinger <andreas.feuersinger@spintower.eu>
Cc: libertas-dev@lists.infradead.org,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Subject: Re: MXC MMC and Libertas_sdio
Date: Fri, 23 Jul 2010 22:30:53 +0100 [thread overview]
Message-ID: <876305ubqq.fsf@linux-g6p1.site> (raw)
In-Reply-To: <20100723135938.619c6cb7@speedy>
On Fri, 23 Jul 2010 13:59:38 +0200, Andreas Feuersinger <andreas.feuersinger@spintower.eu> wrote:
Cc'ing libertas-dev@lists.infradead.org
>
> Hi,
>
> I'm trying to use the libertas driver on MX27 based hardware. I'm using
> kernel v2.6.22 with libertas and sdio driver ported (mainly 2.6.34).
> The Wlan device is Marvel SD8686 connected via sdio.
>
> Loading of firmware seems to work using a block size of 512
> sdio_set_block_size(card->func, 512);
>
> after loading the firmware I get the following output:
>
> libertas: waiting for firmware to boot
> libertas: sdio read scratch
> libertas: sdio scratch 0 ; ret: 0
> libertas: sdio read scratch
> libertas: sdio scratch 0 ; ret: 0
> libertas: sdio read scratch
> libertas: sdio scratch 0 ; ret: 0
> libertas: sdio read scratch
> libertas: sdio scratch 220 ; ret: 0
> libertas: sdio host to card type 1, bytes 46
> libertas: sdio host to card worker
> libertas: sdio read scratch
> libertas: sdio scratch 50 ; ret: 0
> libertas: sdio card to host size 50
> libertas: sdio card to host status: 10
> libertas: card->buffer[0] 0 card->buffer[1] 0
> packet of type 1 and size 0 bytes
> libertas: sdio handle cmd
> libertas: response packet too large (4294967292 bytes)
> libertas: problem fetching packet from firmware
>
> The latest output goes on forever. Canceling the modprobe command
> results in a Network Interface:
>
> Strg+C
> libertas: eth1: Marvell WLAN 802.11 adapter
>
> However the problem fetching packet from firmware remains and the
> device does not work.
> I tried several Firmware Versions all resulting as described above.
>
> If I use 32 instead of 512 for the block size the kernel hangs after
> loading helper firmware during the loading process of the "real"
> firmware.
>
> I read about Daniel Mack doing similar stuff for mx31 based systems.
> Did he/you has/have success in that and what were your problems?
>
> I appreciate any help/hints where to dig for the error.
>
> Thanks,
> Andreas
>
>
>
>
>
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-mmc" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2010-07-23 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-23 11:59 MXC MMC and Libertas_sdio Andreas Feuersinger
2010-07-23 21:30 ` Matt Fleming [this message]
2010-07-26 14:48 ` Andreas Feuersinger
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=876305ubqq.fsf@linux-g6p1.site \
--to=matt@console-pimps.org \
--cc=andreas.feuersinger@spintower.eu \
--cc=libertas-dev@lists.infradead.org \
--cc=linux-mmc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.