From: Linus Walleij <linus.ml.walleij@gmail.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>,
Pierre Ossman <pierre@ossman.eu>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Sudeep K N <sudeepholla.maillist@gmail.com>,
linux-arm-kernel@lists.arm.linux.org.uk, drzeus-mmc@drzeus.cx,
linux-kernel@vger.kernel.org
Subject: Re: Rootfs in eMMC: Kernel panic ...Attempted to kill init!
Date: Tue, 23 Jun 2009 11:23:35 +0200 [thread overview]
Message-ID: <63386a3d0906230223v66564c5bh613d05a0defb8c35@mail.gmail.com> (raw)
In-Reply-To: <20090622164604.GG29188@n2100.arm.linux.org.uk>
2009/6/22 Russell King - ARM Linux <linux@arm.linux.org.uk>:
> If I knew what this "eMMC" was...
It's to be read out "embedded MultiMediaCard", comes
from JEDEC but is based on the standard from MMCA.
Just as it says, it's like an MMC card you embed.
It uses lower voltages than MMC and thus save some
power. It doesn't look like an MMC card either, it comes
in a standardized solder-on BGA package so it looks
like any chip, no expensive card holders. It uses 8bit wide
transfers giving a total of 10 pins for the bus.
(Plus voltage of course.)
But usually you reuse a standard MMC hardware IP
to talk to it.
Here is some whitepaper:
http://www.jedec.org/download/search/JESD84-C43.pdf
Linus Walleij
next prev parent reply other threads:[~2009-06-23 9:23 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-18 9:18 Sudeep K N
2009-06-19 13:44 ` Russell King - ARM Linux
2009-06-22 14:13 ` Sudeep K N
2009-06-22 14:26 ` Catalin Marinas
2009-06-22 14:32 ` Catalin Marinas
2009-06-22 15:43 ` Russell King - ARM Linux
2009-06-22 15:50 ` Catalin Marinas
2009-06-22 15:56 ` Russell King - ARM Linux
2009-06-22 16:13 ` Catalin Marinas
2009-06-22 16:46 ` Russell King - ARM Linux
2009-06-22 21:37 ` Catalin Marinas
2009-06-23 9:23 ` Linus Walleij [this message]
2009-06-23 14:34 ` Catalin Marinas
2009-07-13 15:44 ` Dirk Behme
2009-07-13 15:48 ` Russell King - ARM Linux
2009-07-16 10:39 ` Catalin Marinas
2009-06-23 5:58 ` Sudeep K N
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=63386a3d0906230223v66564c5bh613d05a0defb8c35@mail.gmail.com \
--to=linus.ml.walleij@gmail.com \
--cc=catalin.marinas@arm.com \
--cc=drzeus-mmc@drzeus.cx \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=pierre@ossman.eu \
--cc=sudeepholla.maillist@gmail.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
all inboxes | Powered by JetHome®