Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] Clarify MIPS ABIs support
Date: Wed, 25 Jul 2012 20:31:09 +0200	[thread overview]
Message-ID: <20120725203109.5d295941@skate> (raw)
In-Reply-To: <20120725202503.7ecae923@skate>

Le Wed, 25 Jul 2012 20:25:03 +0200,
Thomas Petazzoni <thomas.petazzoni@free-electrons.com> a ?crit :

> Le Wed, 25 Jul 2012 19:32:26 +0200,
> Arnout Vandecappelle <arnout@mind.be> a ?crit :
> 
> >   As far as I understand, the situation is a bit similar to PCs, where
> > i386 and x86_64 are in fact quite different even at instruction set
> > level.  So wouldn't it make more sense to distinguish mips and mips64
> > at the 'Target Architecture' level?  Then mips would always select
> > o32, and the ABI choice would only exist for mips64.  And there
> > would be a 1-to-1 mapping between BR2_ARCH and the user choice,
> > which makes more sense to me.
> 
> Makes sense. Gustavo, what do you think?
> 
> >   It would require a bit of research to find out which sub-architectures
> > are 64-bit, of course.
> 
> Right, but it should be doable. The linux-mips.org Wiki has some info,
> and I know someone who has quite a bit of experience with MIPS stuff,
> so I could ask.

Thinking more about this, the way we do things for i386 vs. x86_64 is
not optimal: there are two complete distinct sets of entries for the
processor types. One for i386, one for x86_64. However, there should
normally be a big overlap between the two, since all x86_64 processors
support the i386 architecture. So maybe we should have a single list,
with certain processor not being visible in the i386. This would ensure
consistency between the list of processors available on i386 and x86_64.

Thoughts?

Thomas
-- 
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com

  reply	other threads:[~2012-07-25 18:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-24 20:47 [Buildroot] [PATCH] Clarify MIPS ABIs support Thomas Petazzoni
2012-07-25 16:29 ` Thomas Petazzoni
2012-07-25 17:32 ` Arnout Vandecappelle
2012-07-25 18:25   ` Thomas Petazzoni
2012-07-25 18:31     ` Thomas Petazzoni [this message]
2012-07-25 19:15       ` Thomas Petazzoni
2012-07-26 16:38         ` Arnout Vandecappelle
2012-07-27  6:31           ` Thomas Petazzoni
2012-07-26 19:01         ` Thomas Petazzoni
2012-07-26 19:38           ` Gustavo Zacarias
2012-07-27  6:56             ` Thomas Petazzoni
2012-07-27 10:17               ` Gustavo Zacarias
2012-07-25 20:25     ` Gustavo Zacarias
2012-07-25 20:38       ` Thomas Petazzoni

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=20120725203109.5d295941@skate \
    --to=thomas.petazzoni@free-electrons.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