From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] ARM cores
Date: Mon, 24 Jan 2011 17:03:00 +0100 [thread overview]
Message-ID: <87y66athl7.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20110124165711.381989cf@surf> (Thomas Petazzoni's message of "Mon, 24 Jan 2011 16:57:11 +0100")
>>>>> "Thomas" == Thomas Petazzoni <thomas.petazzoni@free-electrons.com> writes:
Hi,
>> Thinking a bit more about it - For the omap3 stuff, they are all with
>> A8 cores, so we could even do 'depends on BR2_cortex_a8', right?
Thomas> Besides those OMAP-specific packages, there are also other packages
Thomas> that could depend on CPU-specific features.
Thomas> For example, some video decoders have specific code to use NEON
Thomas> instructions, but those instructions are not available on Cortex-A8
Thomas> cores for example.
Not available? Doesn't almost all A8 implementations have NEON? Do we
have any packages that cannot work on !NEON arms? (E.G. where it isn't
just an optimization)
Thomas> Should we go all the way down to specifying the particular CPU
Thomas> the user is going to use (OMAP3, OMAP4, etc.) and then select
Thomas> the appropriate mtune/march according to this, show/hide
Thomas> packages according to this, and tune specifically some packages
Thomas> according to this ?
That would imho be a lot of work to keep uptodate with the maze of ARM
SoCs available.
I think a few defconfigs for commonly used boards would be good enough.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-01-24 16:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-23 22:41 [Buildroot] [PATCH 3rd RESEND 0/6] GStreamer patches, and TI OMAP3 DSP stuff Felipe Contreras
2011-01-23 22:41 ` [Buildroot] [PATCH 3rd RESEND 1/6] gstreamer: remove unnecessary feature Felipe Contreras
2011-01-24 8:42 ` Peter Korsgaard
2011-01-23 22:41 ` [Buildroot] [PATCH 3rd RESEND 2/6] Fix gstreamer packages for make 3.82 Felipe Contreras
2011-01-24 8:39 ` Peter Korsgaard
2011-01-25 2:51 ` Felipe Contreras
2011-01-25 9:01 ` Peter Korsgaard
2011-01-23 22:41 ` [Buildroot] [PATCH 3rd RESEND 3/6] Add tidsp-binaries package Felipe Contreras
2011-01-24 8:53 ` Peter Korsgaard
2011-01-23 22:41 ` [Buildroot] [PATCH 3rd RESEND 4/6] Add gst-dsp package Felipe Contreras
2011-01-24 8:54 ` Peter Korsgaard
2011-01-23 22:41 ` [Buildroot] [PATCH 3rd RESEND 5/6] Add dsp-tools package Felipe Contreras
2011-01-24 8:54 ` Peter Korsgaard
2011-01-23 22:41 ` [Buildroot] [PATCH 3rd RESEND 6/6] Add gst-omapfb package Felipe Contreras
2011-01-24 8:58 ` Peter Korsgaard
2011-01-24 15:57 ` [Buildroot] ARM cores Thomas Petazzoni
2011-01-24 16:03 ` Peter Korsgaard [this message]
2011-01-24 17:04 ` Thomas Petazzoni
2011-01-24 20:06 ` Peter Korsgaard
2011-01-24 16:08 ` Eric BENARD
2011-01-24 17:08 ` Thomas Petazzoni
2011-01-25 2:55 ` [Buildroot] [PATCH 3rd RESEND 6/6] Add gst-omapfb package Felipe Contreras
2011-01-25 9:02 ` Peter Korsgaard
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=87y66athl7.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.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