From: "Rick Foos" <rick@synchromeshcomputing.com>
To: Kevin Hilman <khilman@mvista.com>
Cc: linux-omap-open-source@linux.omap.com
Subject: Re: omap mmc build errors
Date: Tue, 2 May 2006 16:59:54 -0500 [thread overview]
Message-ID: <00ae01c66e33$bf52cd20$7701a8c0@AthlonX2> (raw)
In-Reply-To: 4457CE22.8050702@mvista.com
CONFIG_MMC_OMAP also allowed the git kernel to boot on OMAP 2420 H4, Thanks.
----- Original Message -----
From: Kevin Hilman
To: Tony Lindgren
Cc: linux-omap-open-source@linux.omap.com
Sent: Tuesday, May 02, 2006 4:24 PM
Subject: Re: omap mmc build errors
Tony Lindgren wrote:
> * Komal Shah <komal_shah802003@yahoo.com> [060413 08:18]:
>> --- Carlos Aguiar <carlos.aguiar@indt.org.br> wrote:
>>
>>> Hi Komal and folks,
>>>
>>> You have to apply a patch that Tony sent to the list 7 days ago. This
>>>
>>> patch corrects the bugs mentioned above. Attached to this mail follow
>>>
>> You still need the attached patch on top of the Tony's patch to build
>> it successfully.
>
> I've just pushed that patch + fixed trying to ioremap a virtual address.
> Seems to work now, can you test?
Haven't had time to dig, but this builds but doesn't boot on 1710/H3. Simply
disabling CONFIG_MMC_OMAP makes it boot.
Kevin
_______________________________________________
Linux-omap-open-source mailing list
Linux-omap-open-source@linux.omap.com
http://linux.omap.com/mailman/listinfo/linux-omap-open-source
--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.385 / Virus Database: 268.5.1/328 - Release Date: 5/1/2006
next prev parent reply other threads:[~2006-05-02 21:59 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 [this message]
2006-05-03 9:53 ` Tony Lindgren
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='00ae01c66e33$bf52cd20$7701a8c0@AthlonX2' \
--to=rick@synchromeshcomputing.com \
--cc=khilman@mvista.com \
--cc=linux-omap-open-source@linux.omap.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