lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Fri, 23 Nov 2007 17:39:58 +0100
From:	Pierre Ossman <drzeus@...eus.cx>
To:	Nicolas Ferre <nicolas.ferre@...el.com>
Cc:	ARM Linux Mailing List <linux-arm-kernel@...ts.arm.linux.org.uk>,
	Linux Kernel list <linux-kernel@...r.kernel.org>
Subject: Re: Wifi chips on SDIO interface

I'll just readd my reply again. :)

On Fri, 23 Nov 2007 16:13:18 +0100
Nicolas Ferre <nicolas.ferre@...el.com> wrote:

> I take advantage of this thread to ask a question about the SDIO cards
> you are using to test the stack.
> 
> I look at the page on the MMC wiki :
> http://mmc.drzeus.cx/wiki/SDIO
> but cannot see a card using the Marvell 8xxx chipset : Can you give me
> advice on which SDIO cards you are using.  

That whole site is unfortunately completely unmaintained. I'll probably pull the plug on the entire thing in the near future.

I'm afraid the only card I'm using actively is the Marvell 8686. Of my collection, it's the only one working well enough to do anything useful.

> 
> Another point, do you know what the plans are for future SDIO wifi chips
> support ?
>   

Not much. Atheros 6001 support is on its way (OpenMoko has this chip, so they're looking at it). The chip unfortunately seems to be a bit misdesigned when it comes to timeouts so it has problems initializing. I have no idea what the current status is.

I also have a Socket wifi card, but they haven't shown any interest in providing specs, so it's just a paperweight right now.

> The Marvell chip seems a bit particular as a wifi chip (802.11 stack
> included in chip). Do you think that other chips are more or less
> difficult to interface through SDIO ?  

Well, full MAC is probably a must when it comes to SDIO. The bus is simply too slow and too high-latency to get any decent software MAC running.

Rgds
Pierre

Download attachment "signature.asc" of type "application/pgp-signature" (190 bytes)

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ