From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pavel Machek <pavel@suse.cz>
Cc: Linux Kernel List <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] 1/4 MMC layer
Date: Mon, 3 May 2004 23:47:10 +0100 [thread overview]
Message-ID: <20040503234710.B25413@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20040503134744.GD1188@openzaurus.ucw.cz>; from pavel@suse.cz on Mon, May 03, 2004 at 03:47:45PM +0200
On Mon, May 03, 2004 at 03:47:45PM +0200, Pavel Machek wrote:
> > As there haven't been any comments, can I assume that either people
> > don't care, or people are happy for this to appear in Linus' tree?
>
> Happy. i386 nx5k notebook contains mmc slot, and I assume
> this will help me with a driver.
That depends on the kind of hardware interface you have - whether it
gives you low level access to the MMC command/data streams, or whether
it looks like a USB device / CF disk / whatever else. (I've heard
rumours that such games are played on laptops, but I've no idea how
true this is.)
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 PCMCIA - http://pcmcia.arm.linux.org.uk/
2.6 Serial core
next prev parent reply other threads:[~2004-05-03 22:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-29 12:48 [RFC] 1/4 MMC layer Russell King
2004-04-29 12:49 ` [RFC] 2/4 MMC layer: configuration + makefiles Russell King
2004-04-29 12:50 ` [RFC] 3/4 MMC layer: ARM MMCI driver Russell King
2004-04-29 12:51 ` [RFC] 4/4 MMC layer: PXA MCI driver Russell King
2004-05-02 14:52 ` [RFC] 1/4 MMC layer Russell King
2004-05-03 13:47 ` Pavel Machek
2004-05-03 22:47 ` Russell King [this message]
2004-05-03 23:00 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2004-05-10 12:53 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=20040503234710.B25413@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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