From: Sascha Hauer <s.hauer@pengutronix.de>
To: barebox@tylerlabs.com
Cc: barebox@lists.infradead.org
Subject: Re: barebox for leopardboard
Date: Fri, 5 Feb 2010 19:20:45 +0100 [thread overview]
Message-ID: <20100205182045.GB18291@pengutronix.de> (raw)
In-Reply-To: <4B6C5C5E.2020208@tylerlabs.com>
On Fri, Feb 05, 2010 at 01:58:54PM -0400, Tyler W. Wilson wrote:
> On 2/5/2010 1:49 PM, Sascha Hauer wrote:
>> Hi Tyler,
>>
>> On Fri, Feb 05, 2010 at 12:25:28PM -0400, Tyler W. Wilson wrote:
>>
>>> I am curious if anybody has done any work on getting barebox running on
>>> the leopardboard, so I do not reproduce effort.
>>>
>>> I am especially interested in setting up a bootloader that directly
>>> supports USB and DFU, so that I do not need to use the UART/serial port.
>>>
>> I know nothing about the leopardboard, from googling I found out that
>> this is a beagleboard with a camera connected to it, right? Barebox runs
>> on the beagleboard, but unfortunately we do not have USB support for it.
>> You would have to port the usb driver for it, then DFU should work.
>> As a first shot you can compile the beagleboard defconfig and see how
>> far you get.
>>
>> Sascha
>>
>>
> Unfortunately, it is a little different - it uses a DaVinci DM355
> processor, which is an ARM9 + custom DSP. The beagleboard uses an OMAP3x
> of course. Unfortunately, even I am confused on the TI naming scheme as
> to what is an OMAP versus what is a DaVinci.
Then I'm afraid you have to start porting from scratch. If you're lucky
they share some peripherals.
>
> I will probably do as you suggest - start with the beagleboard configs
> and also look at the leopardboard code in the ti u-boot repo. Hopefully
> that will give me enough data to get the basic barebox running.
Experience showed that it's a good way to start barebox from U-Boot as a
second stage loader and add the low level init stuff later.This way you
should be running up quite fast. Feel free to ask further questions
about it.
>
> The USB worries me, since I am just familiar enough with it to know how
> complex it can be. Time will tell
What kind of controller does this SoC have, EHCI, OHCI?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next prev parent reply other threads:[~2010-02-05 18:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 16:25 barebox for leopardboard Tyler W. Wilson
2010-02-05 17:49 ` Sascha Hauer
2010-02-05 17:58 ` Tyler W. Wilson
2010-02-05 18:20 ` Sascha Hauer [this message]
2010-02-05 20:16 ` Anand Gadiyar
2010-02-08 10:41 ` Premi, Sanjeev
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=20100205182045.GB18291@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=barebox@tylerlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.