From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] Help with configuring Buildroot for the Omap3530 EVM
Date: Mon, 24 May 2010 18:09:01 -0500 [thread overview]
Message-ID: <201005241809.04330.minimod@morethan.org> (raw)
In-Reply-To: <201005241802.54715.minimod@morethan.org>
On Mon May 24 2010, Michael S. Zick wrote:
> On Mon May 24 2010, Paul Jones wrote:
> >
> > > -----Original Message-----
> > > From: buildroot-bounces at busybox.net [mailto:buildroot-
> > > bounces at busybox.net] On Behalf Of Bob Bouterse
> > > Sent: Tuesday, 25 May 2010 6:24 AM
> > > To: buildroot at busybox.net
> > > Subject: [Buildroot] Help with configuring Buildroot for the Omap3530 EVM
> > >
> > > Sorry everone, this is a bit of complaining from me, with a hope that
> > there is
> > > someone that can give me either help to configure Buildroot for an
> > > Omap3530 EVM board, or hard measurements that I can use to show my
> > > Management (and TI) that OE is slow and will cost us development time.
> > >
> > > Here is my problem:
> > > We are beginning a new project, an have decided to use the Omap3530 EVM
> > > board to begin development on. We do not know if we will go to market with
> > > the OMAP or some other processor at this time.
> > > Seems like the entire Omap Open Source Community has jumped to using
> > > OpenEmbedded with no consideration for how well it works. I find several
> > > documents that give hearsay comments that it might be slow, but no metrics
> > > to show what they mean. I have seen that it seems to be around
> > > 2.5 to 4 times slower that buildroot, and even worse running on a VM, but
> > > due to my lack of experience with OE, it could be a configuration error on
> > my
> > > part. I am working with the Arago group on that.
> > >
> > > Does anyone have a board configuration for the Omap3503 EVM for
> > > buildroot? It would help a lot if I could show my management a working
> > build
>
> Check on the recently posted patch to add support for the Beagleboard
> to Buildroot. The Beagleboard uses an Omap3530.
>
> I admit that I didn't read the patch, but any new board should have
> a defconfig file as part of its addition to Buildroot.
>
Yup, there is a defconfig listed:
http://lists.busybox.net/pipermail/buildroot/2010-May/034598.html
Mike
> Mike
> > > really quickly. I need the target/device files and Omap patches in a
> > working
> > > build. I am not being given any time to work on this because Arago
> > "works".
> >
> > >From my experience with a mini2440 board it seems that the quickest route is
> > to get a kernel patch and get that building/running using buildroot, then
> > work on the root filesystem. All I had to do was select my architecture
> > (arm920) and choose some packages to build.
> >
> > Good Luck!
> >
> >
> > Paul.
> >
> > _______________________________________________
> > buildroot mailing list
> > buildroot at busybox.net
> > http://lists.busybox.net/mailman/listinfo/buildroot
> >
> >
>
>
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot
>
>
next prev parent reply other threads:[~2010-05-24 23:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 20:23 [Buildroot] Help with configuring Buildroot for the Omap3530 EVM Bob Bouterse
2010-05-24 22:51 ` Paul Jones
2010-05-24 23:02 ` Michael S. Zick
2010-05-24 23:09 ` Michael S. Zick [this message]
2010-05-25 13:13 ` Bob Bouterse
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=201005241809.04330.minimod@morethan.org \
--to=minimod@morethan.org \
--cc=buildroot@busybox.net \
/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