<div>Rob,</div>
<div> </div>
<div>I didn't release the code, as this is not really part of openmoko.</div>
<div>To make this driver, I used a part of Atheros's driver, merged with a part of openmoko's one, resulting in a "arch-independant" driver for 1.x versions of this card.</div>
<div> </div>
<div>This worked well, and was stable enough for applications like video streaming, so I stayed with this solution.</div>
<div> </div>
<div>I don't have access to the code yet ( I recently changed of company ) , I have to ask a person to send it back to me. AFAIK, he is on holiday actually, I'll be able to give it to you in about a week I think.</div>
<div> </div>
<div>Regards,</div>
<div>Vincent.</div>
<div><br> </div>
<div class="gmail_quote">2009/8/18 Robert Emanuele <span dir="ltr"><<a href="mailto:rob@emanuele.us">rob@emanuele.us</a>></span><br>
<blockquote style="BORDER-LEFT: #ccc 1px solid; MARGIN: 0px 0px 0px 0.8ex; PADDING-LEFT: 1ex" class="gmail_quote">Hi Vincent,<br><br>I would be happy to give your code a try. We are not using DMA with a<br>real MMC driver. I'd appreciate a look at it. Have you released this<br>
code back to the openmoko project? Is this the final solution you<br>went with or did you end up finding a card with the 2.0 firmware?<br><br>Thanks,<br><br>Rob<br>
<div>
<div></div>
<div class="h5"><br>On Mon, Aug 17, 2009 at 10:22 PM, Vincent Del<br>Medico<<a href="mailto:vincent.del.medico@gmail.com">vincent.del.medico@gmail.com</a>> wrote:<br>> Hi rob,<br>><br>> Openmoko's version of AR6k driver is for cards with 2.x firmware.<br>
> You seem to have a 1.x version ( BMI Get Target Info: Exit (ver: 0x1302270f<br>> type: 0x1) ), which is not compatible with 2.x.<br>><br>> I faced the same problem as you before, except I was playing with the OMAP<br>
> processor ( TI ).<br>><br>> I can give you the job I did, but it only works in some conditions :<br>> - your MMC/SD/SDIO driver must NOT use DMA transfers. The 32bit ARM core<br>> only supports transfers of data multiple of 4 bytes, but the AR6k driver<br>
> sometimes sends data of 1, 2 or 3 bytes, resulting in DMA misaligned errors.<br>> I've not been able to solve this problem, it could be nice to investigate.<br>> - the driver works with a real MMC/SD/SDIO driver ( not SPI )...<br>
> nevertheless, it maybe in SPI, but didn't tested.<br>><br>> Regards,<br>> Vincent.<br>> 2009/8/18 Robert Emanuele <<a href="mailto:rob@emanuele.us">rob@emanuele.us</a>><br>>><br>>> Greetings,<br>
>><br>>> I've been toying with your port of the ar6000 driver with my atmel<br>>> at91 processor.<br>>><br>>> It tries to initialize the card but fails....<br>>><br>>> ar6000_available<br>
>> BMI Get Target Info: Exit (ver: 0x1302270f type: 0x1)<br>>> Block Size Set: 128 (target address:0x8000066C)<br>>> ar6000_init() Got WMI @ 0xc3a37d60.<br>>> Timeout waiting for recv message<br>>> Target Not Available!!<br>
>> ar6000_avail: register_netdev failed<br>>> +ar6000_destroy<br>>> ar6000_cleanup(): WMI not ready 0xc3a322c0 0xc3a37d60<br>>> ar6000_cleanup(): Shut down WMI<br>>> eth0: link up (100/Full)<br>
>> Attempting to reset target on instance destroy....<br>>> -ar6000_destroy<br>>><br>>> In an earlier post I saw that this firmware version may be too old.<br>>> I've tried cards from 3 different vendors and the newest version I can<br>
>> come up with is 0x17 (which is on the way). Does anyone know the<br>>> differences between 1.3 and the version that works with this driver?<br>>> How do the CE guys get this to work? Or, does anyone know of a vendor<br>
>> that sells an ar6000 with the latest firmware in an SD Card package?<br>>><br>>> Thanks,<br>>><br>>> Rob<br>>><br>><br>><br></div></div></blockquote></div><br>