From: Ian Molton <ian@mnementh.co.uk>
To: "Charles D. Krebs" <ckrebs@therealtimegroup.com>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>,
linux-sh@vger.kernel.org, sailaja.sdn@redpinesignals.com,
Magnus Damm <magnus.damm@gmail.com>,
linux-mmc@vger.kernel.org
Subject: Re: Status of tmio_mmc DMA support for SDIO
Date: Sat, 15 May 2010 10:26:41 +0000 [thread overview]
Message-ID: <AANLkTiky1H2rJLoJVa_iDVKyGKLsVKGS7_bb4NctJ1nL@mail.gmail.com> (raw)
In-Reply-To: <1B215080664E44FE81F6BA1DCFA65A38@RSI45>
Could someone send me a copy of the patch to tmio ?
--
Ian Molton
Linux, Automotive, and other hacking:
http://www.mnementh.co.uk/
On 14 May 2010 20:43, Charles D. Krebs <ckrebs@therealtimegroup.com> wrote:
>>> Just saw this - am I right in thinking someone has written SDIO
>>> support for TMIO ? Im afraid I dont appear to have the preceeding
>>> emails.
>>
>> This is the first email regarding TMIO SDIO that I'm aware of - from
>> Charles, he's sent it tothe sh ML and to me and I've added you and the mmc
>> list to CC.
>
> To clarify - I didn't write that code. It was developed by some of the
> Kernel guys over at Renesas Japan specifically for my request to support
> SDIO under their BSP for 2.6.33. The code in tmio and sh_mobile_sdhi
> replaces a previously closed source module for SD support on the hardware
> due to licensing restrictions of the SD consortium. Apparently those issues
> were resolved and now the complete SD stack is integrated into the Kernel
> directly. However, the transition didn't include support for SDIO, so the
> patch to tmio was provided in the interim.
>
> Magnus - Do you know the author for the SDIO patch?
>
> Charles Krebs, Embedded Solutions Developer
> The Realtime Group
>
> --------------------------------------------------
> From: "Guennadi Liakhovetski" <g.liakhovetski@gmx.de>
> Sent: Friday, May 14, 2010 12:54 PM
> To: "Ian Molton" <ian@mnementh.co.uk>
> Cc: "Charles D. Krebs" <ckrebs@therealtimegroup.com>;
> <linux-sh@vger.kernel.org>; <sailaja.sdn@redpinesignals.com>; "Magnus Damm"
> <magnus.damm@gmail.com>; <linux-mmc@vger.kernel.org>
> Subject: Re: Status of tmio_mmc DMA support for SDIO
>
>> On Fri, 14 May 2010, Ian Molton wrote:
>>
>>> Just saw this - am I right in thinking someone has written SDIO
>>> support for TMIO ? Im afraid I dont appear to have the preceeding
>>> emails.
>>
>> This is the first email regarding TMIO SDIO that I'm aware of - from
>> Charles, he's sent it tothe sh ML and to me and I've added you and the mmc
>> list to CC.
>>
>> Thanks
>> Guennadi
>> ---
>> Guennadi Liakhovetski, Ph.D.
>> Freelance Open-Source Software Developer
>> http://www.open-technology.de/
>>
>
>
next prev parent reply other threads:[~2010-05-15 10:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <A0C4AD4CC48F4CAAA4C9CB027472149D@RSI45>
2010-05-14 8:35 ` Status of tmio_mmc DMA support for SDIO Guennadi Liakhovetski
2010-05-14 17:19 ` Ian Molton
2010-05-14 17:54 ` Guennadi Liakhovetski
2010-05-14 19:43 ` Charles D. Krebs
2010-05-15 10:26 ` Ian Molton [this message]
2010-05-17 3:35 ` Magnus Damm
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=AANLkTiky1H2rJLoJVa_iDVKyGKLsVKGS7_bb4NctJ1nL@mail.gmail.com \
--to=ian@mnementh.co.uk \
--cc=ckrebs@therealtimegroup.com \
--cc=g.liakhovetski@gmx.de \
--cc=linux-mmc@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sailaja.sdn@redpinesignals.com \
/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).