From: Tony Lindgren <tony@atomide.com>
To: Steve Sakoman <sakoman@gmail.com>
Cc: "linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>
Subject: Re: mmc broken?
Date: Fri, 5 Dec 2008 17:18:34 -0800 [thread overview]
Message-ID: <20081206011834.GV9714@atomide.com> (raw)
In-Reply-To: <5e088bd90812051701i633bf4f6h887d95ce12014444@mail.gmail.com>
* Steve Sakoman <sakoman@gmail.com> [081205 17:01]:
> On Fri, Dec 5, 2008 at 4:49 PM, Tony Lindgren <tony@atomide.com> wrote:
> > * Tony Lindgren <tony@atomide.com> [081205 16:34]:
> >> * Steve Sakoman <sakoman@gmail.com> [081205 16:31]:
> >> > I attempted an Overo build this afternoon with
> >> > fb3d15c023ff08c879155db630895f38526b95f6.
> >> >
> >> > I set bootargs for rootfs on mmc. The boot progresses normally and
> >> > then hangs waiting for the rootfs to mount.
> >> >
> >> > Where I previously got:
> >> >
> >> > Waiting for root device /dev/mmcblk0p2...
> >> > mmc0: host does not support reading read-only switch. assuming write-enable.
> >> > mmc0: new SD card at address ee21
> >> > mmcblk0: mmc0:ee21 SU02G 1.89 GiB
> >> > mmcblk0: p1 p2
> >> >
> >> > I now get:
> >> >
> >> > Waiting for root device /dev/mmcblk0p2...
> >> >
> >> > Has anyone else seen mmc issues with rc7?
> >>
> >> I think I did it again while cleaning up.. Can you try this patch?
> >> The name was conflicting with the other MMC omap driver.
> >
> > Actually now it breaks for earlier omaps, it needs to be like this
> > patch instead.
>
> Heh, isn't that how it always goes! Two steps forward, one step back :-)
:)
> I tested your first patch and it did indeed solve the issue. Looks
> like your second patch will also work. I'll verify this later this
> evening.
Pushed it already, seems to work.
Tony
prev parent reply other threads:[~2008-12-06 1:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 0:31 mmc broken? Steve Sakoman
2008-12-06 0:34 ` Tony Lindgren
2008-12-06 0:49 ` Tony Lindgren
2008-12-06 1:01 ` Steve Sakoman
2008-12-06 1:18 ` Tony Lindgren [this message]
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=20081206011834.GV9714@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap@vger.kernel.org \
--cc=sakoman@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