From: green <greenfreedom10@gmail.com>
To: Linux-OMAP List <linux-omap@vger.kernel.org>
Subject: Re: n810 internal mmc boot
Date: Sat, 21 Mar 2009 13:33:55 -0600 [thread overview]
Message-ID: <20090321193355.GG20072@swansys> (raw)
In-Reply-To: <20090228012717.GB4366@swansys>
[-- Attachment #1: Type: text/plain, Size: 575 bytes --]
green wrote at 2009-02-27 18:27 -0700:
> Any news on booting n810 from internal mmc? It hasn't worked for a while.
The kernel detects the external mmc fine (for root=), but not the internal...
I'm just wondering whether any progress is being made or expected. Sorry if
I'm being a nuisance.
> I've been trying to figure out which commit to blame between
> v2.6.28-omap1..cb4befa9201 but no luck: git is still rather new to me.
>
> Any tips how to successfully perform a bisect with these crazy-big merges?
> Commits in the linux merge won't build/work.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2009-03-21 19:34 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-28 1:27 n810 internal mmc boot green
2009-03-21 19:33 ` green [this message]
2009-03-25 11:26 ` Jarkko Nikula
2009-03-25 21:26 ` green
2009-03-26 4:35 ` green
2009-05-23 3:44 ` green
2009-05-24 9:43 ` Jarkko Nikula
2009-05-18 23:34 ` green
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=20090321193355.GG20072@swansys \
--to=greenfreedom10@gmail.com \
--cc=linux-omap@vger.kernel.org \
/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).