public inbox for gentoo-mips@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Stuart Longland" <redhatter@gentoo.org>
To: gentoo-mips@lists.gentoo.org
Cc: gentoo-mips@lists.gentoo.org
Subject: Re: [gentoo-mips] profiles
Date: Thu, 1 Sep 2005 11:49:28 +1000 (EST)	[thread overview]
Message-ID: <51067.131.181.46.59.1125539368.squirrel@mail.longlandclan.hopto.org> (raw)
In-Reply-To: <decc722ea0bcae50f1fdecacf8405080@yahoo.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Curtis Phillips _top posted_:
> I'd prefer Kumba's machine specific profiles. Of course, that's the one
> that's the biggest PITA to implement/update.
>
> Curtis Phillips
> Winemaker
> Salmon Leap Consulting
>
> On Aug 30, 2005, at 8:18 AM, Stephen P. Becker wrote:
>
>> D) (Kumba's idea here...) Have machine specific profiles, e.g.
>> default-linux/mips/ip22, default-linux/mips/ip32, etc.  (This could be
>> really useful because it would allow us to do some other machine
>> specific voodoo in the profile).
>>
>> Any thoughts?

I was thinking that perhaps we could also split it into Endianness, for CHOST
voodoo, and anything else that's endianness-sensitive.

So the profiles would become;
> /usr/profiles/default-linux/mips:
> |- be -- Big Endian Systems
> |  |- n32 \__ Profile for any 64-bit voodoo
> |  |- n64 /
> |  |- ip22 -- SGI Indy, Indigo2 (R4k), Challenge S w/ o32
> |  |  |= n32 -- importing the ../n32 voodoo
> |  |  |- n64 -- importing the ../n64 voodoo
> |  |  '- 2.4 -- with kernel 2.6 stuff masked (for R4600)
> |  |
> |  |- ip27 -- SGI Origin 200/2000 w/ o32
> |  |  |- n32 -- importing the ../n32 voodoo
> |  |  '- n64 -- importing the ../n64 voodoo
> |  |
> |  |- ip28 -- SGI Indigo2 Impact (R10000)
> |  |  |- n32 -- as above
> |  |  '- n64
> |  |
> |  |- ip30 -- SGI Octane/Octane 2
> |  |  |- n32
> |  |  '- n64
> |  |
> |  '- ip32 -- SGI O2
> |     |- r10k -- For R10k-based O2s, if support existed.
> |     |  |- n32
> |     |  '- n64
> |     |- n32
> |     '- n64
> '- le -- Little Endian
>    |- n32
>    |- n64
>    |- cobalt
>    |  |- n32
>    |  '- n64
>    '- amdalchemy

The above is just an idea.  The main reason for splitting 'le' and 'be' is so
that the CHOST can be set correctly (mips{,64}-unknown-linux-gnu on be,
mips{,64}el-unknown-linux-gnu on le).  As for how to handle µClibc, not sure
there.  I'm guessing it'd be another profile like n32, just to s/gnu/uclibc/
in the CHOST -- certainly it will be that way whilst it's o32 only.

Anyways, those are my thoughts. :-)
- --
: ____                   _             Stuart Longland (a.k.a Redhatter)
:/    \   ___    ___  __| |__  __   __ Gentoo Linux/MIPS Cobalt and Docs
:- ( ) \ /   \  ;   \(__   __)/  \ /  \                        Developer
: \    //  O _| / /\ \  | |  | /\ | /\ |
: /   / \   /__| /  \ \ | |  | \/ | \/ |
:(___/   \____/|_;  |_| \_/   \__/ \__/ http://dev.gentoo.org/~redhatter

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.6 (GNU/Linux)

iD8DBQFDFl4ouarJ1mMmSrkRAiDCAJ42KOIXnKwRBvvojDdexE07NF9BIACePZVz
bwMsxOxp1aIv5jPfWyAsnV8=
=3zEt
-----END PGP SIGNATURE-----
-- 
gentoo-mips@gentoo.org mailing list



  reply	other threads:[~2005-09-01  1:49 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-08 11:59 [gentoo-mips] IP30 hang on warm boot Aaron Walker
2005-08-11 20:05 ` Olivier Bornet
2005-08-11 22:22   ` Aaron Walker
2005-08-12  6:47     ` Olivier Bornet
2005-08-12 12:31       ` Aaron Walker
2005-08-13 10:14         ` Olivier Bornet
2005-08-30 15:18           ` [gentoo-mips] profiles Stephen P. Becker
2005-08-30 16:47             ` Curtis Phillips
2005-09-01  1:49               ` Stuart Longland [this message]
2005-09-01 11:00                 ` Stephen Bennett
2005-09-01 14:22                   ` Stuart Longland
2005-09-01 14:30                     ` Stephen Bennett
2005-09-01 12:12             ` Stephen Bennett
2005-09-03  2:05             ` Kumba

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=51067.131.181.46.59.1125539368.squirrel@mail.longlandclan.hopto.org \
    --to=redhatter@gentoo.org \
    --cc=gentoo-mips@lists.gentoo.org \
    /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