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] Q? So why does big-endian MIPS (mips) default to 64bit cores?
Date: Fri, 4 Dec 2009 15:13:02 -0600	[thread overview]
Message-ID: <200912041513.05959.minimod@morethan.org> (raw)
In-Reply-To: <200912041250.49202.minimod@morethan.org>


Right! There is probably decades of history behind the answer.

Judging by the overwhelming number of comments on this project, it
seems the active users of Buildroot for MIPS is down to just "self".

Where did I put my delete key?

Mike

On Fri December 4 2009, Michael S. Zick wrote:
> On Thu December 3 2009, Michael S. Zick wrote:
> > 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;
> >
> 
> Now at revision 0.3, document at above link updated.
> 
> Having had my lessons in en_MIPS and en_GCC will now
> tackle the en_Kconfig language.  ;)
> 
> Mike
> 

  reply	other threads:[~2009-12-04 21:13 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
2009-12-04 18:50   ` Michael S. Zick
2009-12-04 21:13     ` Michael S. Zick [this message]
2009-12-05 13:05     ` 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=200912041513.05959.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