linux-mmc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andreas Feuersinger <andreas.feuersinger@spintower.eu>
To: "linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>
Cc: libertas-dev@lists.infradead.org
Subject: Re: MXC MMC and Libertas_sdio
Date: Mon, 26 Jul 2010 16:48:10 +0200	[thread overview]
Message-ID: <20100726164810.6265bd75@speedy> (raw)
In-Reply-To: <876305ubqq.fsf@linux-g6p1.site>


Hi,

I just managed to get the libertas card to work. Unfortunately the
data-rate is not too good (30 - 50K/s)

To get it work I changed block sizes to be multiples of 4.

Could somebody please point out a good place to increase buffer sizes
to multiples of 4 without influencing the performance/error rate of the
driver?
Are there other possibilities to increase data-rate for my
configuration?

thank you!

Andreas



On Fri, 23 Jul 2010 22:30:53 +0100
Matt Fleming <matt@console-pimps.org> wrote:

> On Fri, 23 Jul 2010 13:59:38 +0200, Andreas Feuersinger
> <andreas.feuersinger@spintower.eu> wrote:
> 
> Cc'ing libertas-dev@lists.infradead.org
> > 
> > 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: 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
> > 


      reply	other threads:[~2010-07-26 14:48 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
2010-07-26 14:48   ` Andreas Feuersinger [this message]

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=20100726164810.6265bd75@speedy \
    --to=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).