From: Sricharan R <r.sricharan@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH RFC] OMAP5: uEVM: Enable USB EHCI functionality (preliminary, not tested)
Date: Fri, 17 May 2013 11:04:41 +0530 [thread overview]
Message-ID: <5195C171.8070900@ti.com> (raw)
In-Reply-To: <20130516152934.GJ32163@bill-the-cat>
Hi,
On Thursday 16 May 2013 08:59 PM, Tom Rini wrote:
> On Thu, May 16, 2013 at 05:56:57PM +0300, Lubomir Popov wrote:
> [snip]
>> The same U-Boot (yesterday's u-boot-ti/master), just configured for
>> my SOM5_EVB board:
>>
>> U-Boot SPL 2013.04-11569-ge3db066-dirty (May 16 2013 - 16:14:17)
>> OMAP5430 ES1.0
>>
>> U-Boot SPL 2013.04-11569-ge3db066-dirty (May 16 2013 - 16:14:17)
>> OMAP5430 ES1.0
>> OMAP SD/MMC: 0
>> reading u-boot.img
>> reading u-boot.img
>>
>>
>> U-Boot 2013.04-11569-ge3db066-dirty (May 16 2013 - 16:14:17)
> [snip]
>> Also please notice that the SPL now seems to be executed twice (on both
>> boards). This was not the case until recently, at least with the mainline.
>> Anything to do with all those relocation discussions/patches?
> Can you bisect and see when something changed? It looks like it's
> printing the same string twice, not loading SPL loading SPL loading
> U-Boot, but I could be wrong..
I tried SD and EMMC boot on the latest mainline on my 5432 ES2.0 and
did not see any issue. What boot are you trying ?
U-Boot SPL 2013.04-00237-g9d32686 (May 17 2013 - 10:54:15)
OMAP5432 ES2.0
OMAP SD/MMC: 0
reading u-boot.img
reading u-boot.img
U-Boot 2013.04-00237-g9d32686 (May 17 2013 - 10:54:15)
CPU : OMAP5432 ES2.0
Board: OMAP5430 EVM
I2C: ready
DRAM: 2 GiB
MMC: OMAP SD/MMC: 0, OMAP SD/MMC: 1
Using default environment
In: serial
Out: serial
Err: serial
Hit any key to stop autoboot: 0
OMAP5430 EVM #
Regards,
Sricharan
next prev parent reply other threads:[~2013-05-17 5:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-15 15:55 [U-Boot] [PATCH RFC] OMAP5: uEVM: Enable USB EHCI functionality (preliminary, not tested) Lubomir Popov
2013-05-15 16:09 ` Nishanth Menon
2013-05-15 22:06 ` Tom Rini
2013-05-15 22:33 ` Gilles Chanteperdrix
2013-05-16 8:23 ` Lubomir Popov
2013-05-16 12:28 ` Tom Rini
2013-05-16 14:56 ` Lubomir Popov
2013-05-16 15:29 ` Tom Rini
2013-05-16 18:43 ` Lubomir Popov
2013-05-17 13:52 ` Tom Rini
2013-05-17 5:34 ` Sricharan R [this message]
2013-05-17 9:35 ` Lubomir Popov
2013-05-15 22:31 ` Gilles Chanteperdrix
2013-05-16 8:39 ` Lubomir Popov
2013-05-18 15:25 ` Gilles Chanteperdrix
2013-05-18 17:07 ` Tom Rini
2013-05-18 17:12 ` Gilles Chanteperdrix
2013-05-18 19:13 ` Lubomir Popov
2013-05-18 19:16 ` Gilles Chanteperdrix
2013-05-18 19:24 ` Lubomir Popov
2013-05-18 20:46 ` Gilles Chanteperdrix
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=5195C171.8070900@ti.com \
--to=r.sricharan@ti.com \
--cc=u-boot@lists.denx.de \
/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