From: "Premi, Sanjeev" <premi@ti.com>
To: "barebox@tylerlabs.com" <barebox@tylerlabs.com>,
"barebox@lists.infradead.org" <barebox@lists.infradead.org>
Subject: RE: barebox for leopardboard
Date: Mon, 8 Feb 2010 16:11:52 +0530 [thread overview]
Message-ID: <B85A65D85D7EB246BE421B3FB0FBB59301E2639AF2@dbde02.ent.ti.com> (raw)
In-Reply-To: <4B6C5C5E.2020208@tylerlabs.com>
> -----Original Message-----
> From: barebox-bounces@lists.infradead.org
> [mailto:barebox-bounces@lists.infradead.org] On Behalf Of
> Tyler W. Wilson
> Sent: Friday, February 05, 2010 11:29 PM
> To: barebox@lists.infradead.org
> Subject: Re: barebox for leopardboard
>
> 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.
>
> 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.
Tyler,
You may want to post specific queries to davinci-linux-open-source@linux.davincidsp.com
Best regards,
Sanjeev
>
> The USB worries me, since I am just familiar enough with it
> to know how
> complex it can be. Time will tell.
>
> Thank you for your input.
>
> Tyler
>
> _______________________________________________
> barebox mailing list
> barebox@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/barebox
>
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2010-02-08 10:42 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-05 16:25 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
2010-02-05 20:16 ` Anand Gadiyar
2010-02-08 10:41 ` Premi, Sanjeev [this message]
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=B85A65D85D7EB246BE421B3FB0FBB59301E2639AF2@dbde02.ent.ti.com \
--to=premi@ti.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox