From: Bob Bouterse <bob.bouterse@dm-holdings-na.com>
To: buildroot@busybox.net
Subject: [Buildroot] Help with configuring Buildroot for the Omap3530 EVM
Date: Mon, 24 May 2010 16:23:44 -0400 [thread overview]
Message-ID: <1274732624.9526.87.camel@bbouterse-debian.escient.local> (raw)
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 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".
next reply other threads:[~2010-05-24 20:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-24 20:23 Bob Bouterse [this message]
2010-05-24 22:51 ` [Buildroot] Help with configuring Buildroot for the Omap3530 EVM Paul Jones
2010-05-24 23:02 ` Michael S. Zick
2010-05-24 23:09 ` Michael S. Zick
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=1274732624.9526.87.camel@bbouterse-debian.escient.local \
--to=bob.bouterse@dm-holdings-na.com \
--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