public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Ian Molton <spyro@f2s.com>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Russell King <rmk+lkml@arm.linux.org.uk>,
	Richard Purdie <rpurdie@rpsys.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: MMC Driver RFC
Date: Sun, 16 Jan 2005 13:19:44 +0000	[thread overview]
Message-ID: <41EA69F0.5060500@f2s.com> (raw)
In-Reply-To: <41EA5C8D.8070407@drzeus.cx>

Pierre Ossman wrote:
> Ian Molton wrote:

> Afraid everything gets routed to the same account in the end anyway. I 
> checked the logs and the problem is that your mail server has a HELO 
> that differs from its IP

I've sent mail to my ISP re that. cheers.

> I've had the same idea. But I think it will be difficult since we need 
> som funky logic during init. Perhaps a model where each mode 
> (MMC/SD/SDIO) each gets their turn trying to find something on the bus.

Might be worth the effort. I'll need to think on it.

> But this would require a rather large rewrite of the MMC layer.

Im not sure it'd be so catastrophic.

>> Mind you, I have plans to look at SDIO, so that may alter things...
>>
> I need it to determine if the code should send an RCA or ask for one, 
> and to determine if it should try and read the SCR. Your solution used 
> an extra parameter but I thought a mode flag would be better since we 
> might need to know mode later on (after init.).

Fair enough.

>> The toshiba controller appears to want to be told when an ACMD is 
>> issued, compared to a normal CMD.
> 
> No hints in the spec about why?

What spec? ;-)

 > Seems very strange since there's no change in what goes over the wire.

I think the controller (for some odd reason) keeps some extra internal 
state.

  reply	other threads:[~2005-01-16 13:20 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-01-12 21:10 MMC Driver RFC Richard Purdie
2005-01-12 21:43 ` Russell King
2005-01-12 22:07   ` Richard Purdie
2005-01-12 22:17     ` Russell King
2005-01-12 23:23       ` Ian Molton
2005-01-12 23:58         ` Richard Purdie
2005-01-14 11:37         ` Pierre Ossman
2005-01-14 14:55           ` Ian Molton
2005-01-16 12:22             ` Pierre Ossman
2005-01-16 13:19               ` Ian Molton [this message]
2005-01-16 19:43                 ` Pierre Ossman
2005-01-16 23:17                   ` Richard Purdie
2005-01-16 22:33                     ` Alan Cox
2005-01-17  6:07                     ` Pierre Ossman
2005-01-17  9:53                       ` Richard Purdie
2005-01-17 11:59                         ` Pierre Ossman

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=41EA69F0.5060500@f2s.com \
    --to=spyro@f2s.com \
    --cc=drzeus-list@drzeus.cx \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rmk+lkml@arm.linux.org.uk \
    --cc=rpurdie@rpsys.net \
    /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