Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michael S. Zick <minimod@morethan.org>
To: buildroot@busybox.net
Subject: [Buildroot] [Bug 769] New: Update configuration menu for MIPS target
Date: Thu, 3 Dec 2009 19:06:36 -0600	[thread overview]
Message-ID: <200912031906.38721.minimod@morethan.org> (raw)
In-Reply-To: <bug-769-163@https.bugs.busybox.net/>

On Wed December 2 2009, bugzilla at busybox.net wrote:
> https://bugs.busybox.net/show_bug.cgi?id=769
> 
>               Host: Any
>             Target: MIPS/MIPSel
>            Summary: Update configuration menu for MIPS target
>            Product: buildroot
>            Version: 2009.11
>           Platform: Other
>                URL: http://morethan.org/bldrt/mips_arch.ods

Reviewed / Revised earlier version;
Added -march= options vs known cores table for gcc-2.95.3 through 4.5.dev.
File at above link updated.

Yuck.  I wonder why nobody tackled this mess before now? ;)

Not too surprising, not only are most of these machines being shipped with
an Aug. 2005 kernel, a compiler is being used that is too old to provide
code generation support specific to the core being used.  Double yuck.

Mike
>         OS/Version: Linux
>             Status: NEW
>           Severity: enhancement
>           Priority: P5
>          Component: Other
>         AssignedTo: minimod at morethan.org
>         ReportedBy: minimod at morethan.org
>                 CC: buildroot at uclibc.org
>    Estimated Hours: 0.0
> 
> 
> The MIPS portion of the configuration menu is outdated
> and does not define the complete set of toolchain options
> for current cores.
> 
> At the above link, the following link and as an attachment
> is the table of information from which the additional
> configuration menu entries will be defined.
> 
> Table 1 shows the relationship between feature names and
> the instruction set.
> 
> Table 2 shows the relationship between core code names
> and features.
> 
> The actual configuration menu patch will follow any day, RSN.
> 
> http://morethan.org/bldrt/mips_arch.ods
> 
> Mikez
> 
> 

  reply	other threads:[~2009-12-04  1:06 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-02 22:38 [Buildroot] [Bug 769] New: Update configuration menu for MIPS target bugzilla at busybox.net
2009-12-04  1:06 ` Michael S. Zick [this message]
2009-12-04 18:50   ` Michael S. Zick
2009-12-04 21:13     ` [Buildroot] [Bug 769] Q? So why does big-endian MIPS (mips) default to 64bit cores? Michael S. Zick
2009-12-05 13:05     ` [Buildroot] [Bug 769] New: Update configuration menu for MIPS target Michael S. Zick
2009-12-08 16:28       ` Michael S. Zick
2009-12-13 18:46 ` [Buildroot] [Bug 769] " bugzilla at busybox.net
2009-12-14 11:56   ` Michael S. Zick
2010-02-21 22:33 ` bugzilla at busybox.net
2013-12-26 21:41 ` bugzilla at busybox.net

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=200912031906.38721.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