From: Tony Lindgren <tony@atomide.com>
To: Rick Foos <rick@synchromeshcomputing.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: omap mmc build errors
Date: Wed, 3 May 2006 02:53:09 -0700 [thread overview]
Message-ID: <20060503095308.GA30376@atomide.com> (raw)
In-Reply-To: <00ae01c66e33$bf52cd20$7701a8c0@AthlonX2>
* Rick Foos <rick@synchromeshcomputing.com> [060502 15:00]:
> CONFIG_MMC_OMAP also allowed the git kernel to boot on OMAP 2420 H4, Thanks.
> ----- Original Message -----
> From: Kevin Hilman
>
> Haven't had time to dig, but this builds but doesn't boot on 1710/H3. Simply
> disabling CONFIG_MMC_OMAP makes it boot.
Hmmm, seems like only 15xx works now. The driver hangs for 16xx in
the while loop in mmc_omap_set_ios(). Also I noticed that all the
menelaus code is missing so it won't work on 24xx.
Tony
next prev parent reply other threads:[~2006-05-03 9:53 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-10 21:26 omap mmc build errors Komal Shah
2006-04-11 13:22 ` Carlos Aguiar
2006-04-13 15:17 ` Komal Shah
2006-05-02 9:20 ` Tony Lindgren
2006-05-02 18:50 ` lamikr
2006-05-02 21:24 ` Kevin Hilman
2006-05-02 21:59 ` Rick Foos
2006-05-03 9:53 ` Tony Lindgren [this message]
2006-05-03 11:01 ` Tony Lindgren
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=20060503095308.GA30376@atomide.com \
--to=tony@atomide.com \
--cc=linux-omap-open-source@linux.omap.com \
--cc=rick@synchromeshcomputing.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