Strange problems with Marvell 8686 sdio on AT91SAM9263

Hans J. Koch hjk at
Mon Jun 2 18:43:20 EDT 2008

On Mon, Jun 02, 2008 at 04:26:47PM -0400, Dan Williams wrote:
> On Fri, 2008-05-30 at 20:13 +0200, Hans J. Koch wrote:
> > Hi,
> > I got a strange error report from a customer using libertas-sdio with a
> > 8686 on an AT91SAM9263 platform. He tests with pings with different
> > blocksizes. It works fine, but only up to a certain blocksize. With
> > larger sizes, there's a TX timeout. After that timeout, it works again
> > for smaller sizes.
> FWIW, pings up to 5000 bytes (ping -s 5000 x.x.x.x) work for me from the
> sd8686 reference board using 8.73.7p3 firmware and the libertas bits
> from 2.6.25 in both the following configurations:
> 1) sd8686 -> MacBook Air (bcm4324 I think) with WEP-encrypted
> infrastructure connection
> 2) sd8686 -> Dell Latitude C610 (Cisco Airo 350) with unencrypted Ad-Hoc
> connection
> I guess the first thing I'd suspect is the SDIO controller on the
> embedded board?  That's usually the ultimate source of problems with the
> SDIO 8686 stuff, that the SDIO controller acts in ways the SDIO stack
> does not necessarily expect.
> ef367e08dddf0fd35f825ea68f1ee104971938f0  sd8686_helper.bin
> 190a58ad1577658944784c024af60fa41e3acbec  sd8686.bin

Hi Dan (and Holger),
thanks for your reports. Ok, I'll try to find out what's behind this.

Thanks for your help,

More information about the libertas-dev mailing list