All of lore.kernel.org
 help / color / mirror / Atom feed
From: Luis Galdos <luis.galdos@digi.com>
To: Dan Williams <dcbw@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	Pierre Ossman <drzeus@drzeus.cx>
Subject: Re: [LIBERTAS-SDIO]  Support for single transfer blocks?
Date: Mon, 1 Jun 2009 11:53:32 +0200	[thread overview]
Message-ID: <4A23A51C.2000608@digi.com> (raw)
In-Reply-To: <1242223408.11182.34.camel@localhost.localdomain>

Dan Williams wrote:
> On Tue, 2009-05-12 at 23:11 -0700, Andrew Morton wrote:
>> Let's Cc the wireless development list.
> 
> And lets CC the MMC subsystem maintainer and original author of libertas_sdio too, so
> we can get an informed opinion :)
> 
> What firmware version are you using?
The installed firmware version is 9.70.3p24 (downloaded from the Marvell's website).

> What SDIO controller is this?  Has this controller been validated by Marvell for use
> with the 8686? (not that that is required or anything, just curious).
The uC is from Digi (NS9215) and its SDIO-port hasn't been validated by Marvell.

> All the information I have (up to firmware V10) references a block size of 32 bytes.
> The main firmware is transferred in 32-byte blocks using CMD 53, with a maximum number
> of 16 blocks transferred in a single CMD 53 write depending on how much data the helper
> firmware can accept in single write.  The available vendor drivers also use a 32-byte
> block size.
That's right. I only was surprised that the SD8686 accepts data blocks of 512 bytes in a 
single transfer too. This is just nice for SDIO-ports that only support single blocks :) 
(like the NS9215). Anyway, Pierre has informed me that the SD8686 has need of multiple 
blocks support, and the NS9215 doesn't. So, the problem is the controller.


> Dan

Thanks and sorry for the delayed answer (I was on vacations),


-- 
Luis Galdos


      parent reply	other threads:[~2009-06-01  9:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-11 14:41 [LIBERTAS-SDIO] Support for single transfer blocks? Luis Galdos
2009-05-13  6:11 ` Andrew Morton
2009-05-13 14:03   ` Dan Williams
2009-05-13 16:28     ` Pierre Ossman
2009-06-01  9:32       ` Luis Galdos
2009-06-01  9:53     ` Luis Galdos [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=4A23A51C.2000608@digi.com \
    --to=luis.galdos@digi.com \
    --cc=akpm@linux-foundation.org \
    --cc=dcbw@redhat.com \
    --cc=drzeus@drzeus.cx \
    --cc=linux-kernel@vger.kernel.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 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.