[gentoo-mips] IP30 hang on warm boot

[gentoo-mips] IP30 hang on warm boot

[Aaron Walker]

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

Gentoo has been running flawlessly on this IP30 for the last month I've had it,
except for one thing.  I've noticed that when I reboot, it hangs at the below
denoted spot:

<dmesg>
Serial: 8250/16550 driver $Revision: 1.90 $ 4 ports, IRQ sharing enabled
io scheduler noop registered
io scheduler anticipatory registered
io scheduler deadline registered
io scheduler cfq registered
loop: loaded (max 8 devices)

>>> HANGS HERE

IOC3 SuperIO: registered IOC3 at 900000001f600000, IRQ 12 (chip 0).
ttyS0 at IOC3 0x1f620178 (irq = 64) is a 16550A
ttyS1 at IOC3 0x1f620170 (irq = 65) is a 16550A
Found DS2502 NIC registration number 21:e5:b0:02:00:00, CRC 9b.
Ethernet address is 08:00:69:13:6f:e1.
eth0: link up, 100Mbps, full-duplex, lpa 0x01E1
eth0: Using PHY 1, vendor 0x15f42, model 2, rev 3.
eth0: IOC3 SSRAM has 128 kbyte.
qla1280: QLA1040 found on PCI bus 0, dev 0
PCI: Enabling device 0000:00:00.0 (0006 -> 0007)
</dmesg>

This happens every single warm boot, and never on a cold boot.  This box is
running mips-sources-2.6.12 with a slimmed-down version of the latest netboot
image's (20050724) kernel config.  I've posted the actual config[1] if it helps.

This is probably material for the linux-mips@ list but figured I'd ask here
first just in case.

[1] http://dev.gentoo.org/~ka0ttic/mips/ip30/ip30-config

Thanks
- --
Nonsense.  Space is blue and birds fly through it.
		-- Heisenberg

Aaron Walker <ka0ttic@gentoo.org>
[ BSD | commonbox | cron | cvs-utils | mips | netmon | shell-tools | vim ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD4DBQFC90krC3poscuANHARAvlGAKDi+eyF5fkypLAAY7zOEmG/68HjvACXX8nM
5x1LeMNDXjxZyMzo/EbkjA==
=12Pe
-----END PGP SIGNATURE-----
-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] IP30 hang on warm boot

[Olivier Bornet]

[-- Attachment #1: Type: text/plain, Size: 894 bytes --]

Hello,

> Gentoo has been running flawlessly on this IP30 for the last month I've had it,

Cool. Could you resume the installation process ? I also have a IP30
(Octane 2), but I was unable to install Linux on it. Note that I don't
have any cross-compiler for it, it has IRIX installed but I have no
experience with IRIX, and I have no experience with gentoo. (I'm an
experienced GNU/Debian user, and I will be more than happy to learn
gentoo).

What I'm interested is to have one working netboot image for the IP30.

Thanks in advance.

        Olivier
-- 
Olivier Bornet                |    français : http://puck.ch/f
Swiss Ice Hockey Results      |    english  : http://puck.ch/e
http://puck.ch/               |    deutsch  : http://puck.ch/g
Olivier.Bornet@puck.ch        |    italiano : http://puck.ch/i
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-mips] IP30 hang on warm boot

[Aaron Walker]

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

Olivier Bornet wrote:

> 
> Cool. Could you resume the installation process ? 

Except for maybe a few minor things (like using arcload over arcboot), just
follow the steps in the handbook.

I also have a IP30
> (Octane 2), but I was unable to install Linux on it. Note that I don't
> have any cross-compiler for it, it has IRIX installed but I have no
> experience with IRIX, and I have no experience with gentoo. (I'm an
> experienced GNU/Debian user, and I will be more than happy to learn
> gentoo).
> 
> What I'm interested is to have one working netboot image for the IP30.

I used http://dev.gentoo.org/~kumba/mips/netboot/new/ip30r10k+-20050724.img.bz2

- --
QOTD:
	"You want me to put *holes* in my ears and hang things from them?
	How...  tribal."

Aaron Walker <ka0ttic@gentoo.org>
[ BSD | commonbox | cron | cvs-utils | mips | netmon | shell-tools | vim ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFC+8+LC3poscuANHARAn7lAJ94SwApChTItwRV25FM8xdru5aziQCdE3TP
jGL/Dq/g3/a1bzpz8VBJ3NY=
=S8o5
-----END PGP SIGNATURE-----
-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] IP30 hang on warm boot

[Olivier Bornet]

[-- Attachment #1: Type: text/plain, Size: 952 bytes --]

Hi,

On Thu, Aug 11, 2005 at 06:22:04PM -0400, Aaron Walker wrote:
> Olivier Bornet wrote:
> > What I'm interested is to have one working netboot image for the IP30.
> 
> I used http://dev.gentoo.org/~kumba/mips/netboot/new/ip30r10k+-20050724.img.bz2

When I try to get this file, I have:

    Forbidden
    You don't have permission to access ...

Browsing http://dev.gentoo.org/~kumba/mips/netboot/ don't show me the
new directory. But it seems to exist, as accessing other path says "Not
Found" and not "Forbidden".

Any other place to download the netboot image ?

Thanks in advance.

        Olivier
-- 
Olivier Bornet                |    français : http://puck.ch/f
Swiss Ice Hockey Results      |    english  : http://puck.ch/e
http://puck.ch/               |    deutsch  : http://puck.ch/g
Olivier.Bornet@puck.ch        |    italiano : http://puck.ch/i
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-mips] IP30 hang on warm boot

[Aaron Walker]

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

Olivier Bornet wrote:

> Any other place to download the netboot image ?

Guess he removed them.  Try
http://dev.gentoo.org/~ka0ttic/mips/ip30/ip30-r10k+-20050724.img.bz2
- --
QOTD:
	"You want me to put *holes* in my ears and hang things from them?
	How...  tribal."

Aaron Walker <ka0ttic@gentoo.org>
[ BSD | commonbox | cron | cvs-utils | mips | netmon | shell-tools | vim ]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFC/JarC3poscuANHARAjSOAKDIKQ/glpGLHZS65ws1/7EzZpnRmQCbB+LX
ntXQ84QOHLIQSke+Bz5g3A8=
=zDsI
-----END PGP SIGNATURE-----
-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] IP30 hang on warm boot

[Olivier Bornet]

[-- Attachment #1: Type: text/plain, Size: 540 bytes --]

Hi,

> Guess he removed them.  Try
> http://dev.gentoo.org/~ka0ttic/mips/ip30/ip30-r10k+-20050724.img.bz2

Perfect, thanks.
My first gentoo installation is on the way. :-D

Thanks a lot.

        Olivier
-- 
Olivier Bornet                |    français : http://puck.ch/f
Swiss Ice Hockey Results      |    english  : http://puck.ch/e
http://puck.ch/               |    deutsch  : http://puck.ch/g
Olivier.Bornet@puck.ch        |    italiano : http://puck.ch/i
Get my PGP-key at http://puck.ch/pgp or at http://pgp.mit.edu/

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

[gentoo-mips] profiles

[Stephen P. Becker]

Hi folks,

With the somewhat recent introduction of support for a wide variety of 
SGI machines under gentoo, expanding to include all of Indy/Indigo2, 
Origin, Octane, Indigo2 Impact (ip28), and O2, I've noticed more than 
just a handful of new users have had problems when getting to the kernel 
compile phase of the install.  The problem is that on systems that only 
run 64-bit kernels, you need a mips64-unknown-linux-gnu toolchain to 
build the kernel.  Since the userland is all 32-bit, the native 
toolchain isn't good enough to compile the kernel.  However, we do 
provide a proper toolchain via the gcc-mips64 ebuild.  Furthermore, 
binutils supports mips64 by default, but symlinks must exist such that 
we have mips64-unknown-linux-gnu-ld -> ld, etc.  Both of these are 
automatically provided during emerge system if you use the correct 
profile, which is default-linux/mips/mips64/2005.0 currently.

The problem is that all of our stages ship with 
default-linux/mips/2005.0 as the default profile, which does *not* 
provide gcc-mips64 and the binutils symlinks.  Therefore if a user 
didn't know any better and didn't change their profile appropriately, 
they would be stuck while trying to build their kernel because the 
native 32-bit toolchain in the userland will just spit out errors and 
die when compiling the kernel.  Of course, this is easily fixed by 
emerging gcc-mips64 and running "binutils-config --mips", which will set 
up a proper toolchain.  However, by that time, the user is discouraged a 
bit and inevitably finds our irc channel and whines that Gentoo is broken.

Now, I have a few ideas for getting around this.  Obviously whatever is 
decided should be added to the documentation, but here are some ideas:

A) Do nothing...document in the handbook that if your machine is 64-bit, 
you *must* select the mips64 sub-profile. (I don't like this because 
some folks may be confused as to why everything still works just fine 
with the mips profile, and/or they will just skim over that and keep going)

B) Similar to A, except ship stages without the profile set.  That way, 
folks really are stuck until they set the proper profile.  (I don't like 
this because they could still be confused and set the mips profile)

C) Make default-linux/mips/ provide all the 64-bit stuff and get rid of 
the mips64 sub-profile, since all of the SGI machines we support can run 
64-bit kernels if you so choose (ip22 is the only system that supports a 
32-bit kernel at this time).

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?

-Steve
-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] profiles

[Curtis Phillips]

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:

> Hi folks,
>
> With the somewhat recent introduction of support for a wide variety of 
> SGI machines under gentoo, expanding to include all of Indy/Indigo2, 
> Origin, Octane, Indigo2 Impact (ip28), and O2, I've noticed more than 
> just a handful of new users have had problems when getting to the 
> kernel compile phase of the install.  The problem is that on systems 
> that only run 64-bit kernels, you need a mips64-unknown-linux-gnu 
> toolchain to build the kernel.  Since the userland is all 32-bit, the 
> native toolchain isn't good enough to compile the kernel.  However, we 
> do provide a proper toolchain via the gcc-mips64 ebuild.  Furthermore, 
> binutils supports mips64 by default, but symlinks must exist such that 
> we have mips64-unknown-linux-gnu-ld -> ld, etc.  Both of these are 
> automatically provided during emerge system if you use the correct 
> profile, which is default-linux/mips/mips64/2005.0 currently.
>
> The problem is that all of our stages ship with 
> default-linux/mips/2005.0 as the default profile, which does *not* 
> provide gcc-mips64 and the binutils symlinks.  Therefore if a user 
> didn't know any better and didn't change their profile appropriately, 
> they would be stuck while trying to build their kernel because the 
> native 32-bit toolchain in the userland will just spit out errors and 
> die when compiling the kernel.  Of course, this is easily fixed by 
> emerging gcc-mips64 and running "binutils-config --mips", which will 
> set up a proper toolchain.  However, by that time, the user is 
> discouraged a bit and inevitably finds our irc channel and whines that 
> Gentoo is broken.
>
> Now, I have a few ideas for getting around this.  Obviously whatever 
> is decided should be added to the documentation, but here are some 
> ideas:
>
> A) Do nothing...document in the handbook that if your machine is 
> 64-bit, you *must* select the mips64 sub-profile. (I don't like this 
> because some folks may be confused as to why everything still works 
> just fine with the mips profile, and/or they will just skim over that 
> and keep going)
>
> B) Similar to A, except ship stages without the profile set.  That 
> way, folks really are stuck until they set the proper profile.  (I 
> don't like this because they could still be confused and set the mips 
> profile)
>
> C) Make default-linux/mips/ provide all the 64-bit stuff and get rid 
> of the mips64 sub-profile, since all of the SGI machines we support 
> can run 64-bit kernels if you so choose (ip22 is the only system that 
> supports a 32-bit kernel at this time).
>
> 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?
>
> -Steve
> -- 
> gentoo-mips@gentoo.org mailing list
>

-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] profiles

[Stuart Longland]

-----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

Re: [gentoo-mips] profiles

[Stephen Bennett]

Stuart Longland wrote:

>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)
>>|  |
>>
Profiles don't do multiple inheritance. You'll either end up duplicating 
n32/n64 in all the relevant subprofiles, in which case why bother with 
be/n32, or the ip22/n32 profile won't inherit from ip22/, which kinda 
defeats the point, no?
-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] profiles

[Stephen Bennett]

Stephen P. Becker wrote:

>  A) Do nothing...document in the handbook that if your machine is
>  64-bit, you *must* select the mips64 sub-profile. (I don't like this
>  because some folks may be confused as to why everything still works
>  just fine with the mips profile, and/or they will just skim over that
>  and keep going)
>
>  B) Similar to A, except ship stages without the profile set. That
>  way, folks really are stuck until they set the proper profile. (I
>  don't like this because they could still be confused and set the mips
>  profile)
>
>  C) Make default-linux/mips/ provide all the 64-bit stuff and get rid
>  of the mips64 sub-profile, since all of the SGI machines we support
>  can run 64-bit kernels if you so choose (ip22 is the only system that
>  supports a 32-bit kernel at this time).
>
>  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).


I quite like D here. Removes any confusion as to what profile you want,
and could then be combined with B so that people don't end up with the
wrong profile set anyway.
-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] profiles

[Stuart Longland]

[-- Attachment #1: Type: text/plain, Size: 1626 bytes --]

Stephen Bennett wrote:
> Stuart Longland wrote:
> 
>> 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)
>>> |  |
>>>
> Profiles don't do multiple inheritance. You'll either end up duplicating
> n32/n64 in all the relevant subprofiles, in which case why bother with
> be/n32, or the ip22/n32 profile won't inherit from ip22/, which kinda
> defeats the point, no?

That's a fly in the ointment, yes.  I spose that means removing the
toplevel n32 and n64 profiles.  This does mean duplication of files,
which is probably it's biggest downside -- but it gives us the greatest
flexibility IMHO.

In fact, there's an idea for profiles... why not have multiple
inheritance?  It'd be something to bring up with the portage devs I
think, but it may have some useful features.

Certainly though, at the very least, we should split according to
endianness and userland.  That way, CHOST and other vars can be set
correctly.
-- 
 ____                   _             Stuart Longland (a.k.a Redhatter)
/  _ \   ___    ___  __| |__  __   __ Gentoo Linux/MIPS Cobalt and Docs
- (_) \ /   \  ;   \(__   __)/  \ /  \                        Developer
 \    //  O _| / /\ \  | |  | /\ | /\ |
 /   / \   /__| /  \ \ | |  | \/ | \/ |
(___/   \____/|_;  |_| \_/   \__/ \__/ http://dev.gentoo.org/~redhatter

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]

Re: [gentoo-mips] profiles

[Stephen Bennett]

Stuart Longland wrote:

>  In fact, there's an idea for profiles... why not have multiple
>  inheritance? It'd be something to bring up with the portage devs I
>  think, but it may have some useful features.

Not going to happen in the current round of development. AIUI
though, profiles are being redone for the rewrite, and multiple
inheritance will very likely be in that.

-- 
gentoo-mips@gentoo.org mailing list

Re: [gentoo-mips] profiles

[Kumba]

[-- Attachment #1: Type: text/plain, Size: 3820 bytes --]

Stephen P. Becker wrote:
> Hi folks,
> 
> With the somewhat recent introduction of support for a wide variety of 
> SGI machines under gentoo, expanding to include all of Indy/Indigo2, 
> Origin, Octane, Indigo2 Impact (ip28), and O2, I've noticed more than 
> just a handful of new users have had problems when getting to the kernel 
> compile phase of the install.  The problem is that on systems that only 
> run 64-bit kernels, you need a mips64-unknown-linux-gnu toolchain to 
> build the kernel.  Since the userland is all 32-bit, the native 
> toolchain isn't good enough to compile the kernel.  However, we do 
> provide a proper toolchain via the gcc-mips64 ebuild.  Furthermore, 
> binutils supports mips64 by default, but symlinks must exist such that 
> we have mips64-unknown-linux-gnu-ld -> ld, etc.  Both of these are 
> automatically provided during emerge system if you use the correct 
> profile, which is default-linux/mips/mips64/2005.0 currently.
> 
> The problem is that all of our stages ship with 
> default-linux/mips/2005.0 as the default profile, which does *not* 
> provide gcc-mips64 and the binutils symlinks.  Therefore if a user 
> didn't know any better and didn't change their profile appropriately, 
> they would be stuck while trying to build their kernel because the 
> native 32-bit toolchain in the userland will just spit out errors and 
> die when compiling the kernel.  Of course, this is easily fixed by 
> emerging gcc-mips64 and running "binutils-config --mips", which will set 
> up a proper toolchain.  However, by that time, the user is discouraged a 
> bit and inevitably finds our irc channel and whines that Gentoo is broken.
> 
> Now, I have a few ideas for getting around this.  Obviously whatever is 
> decided should be added to the documentation, but here are some ideas:
> 
> A) Do nothing...document in the handbook that if your machine is 64-bit, 
> you *must* select the mips64 sub-profile. (I don't like this because 
> some folks may be confused as to why everything still works just fine 
> with the mips profile, and/or they will just skim over that and keep going)
> 
> B) Similar to A, except ship stages without the profile set.  That way, 
> folks really are stuck until they set the proper profile.  (I don't like 
> this because they could still be confused and set the mips profile)
> 
> C) Make default-linux/mips/ provide all the 64-bit stuff and get rid of 
> the mips64 sub-profile, since all of the SGI machines we support can run 
> 64-bit kernels if you so choose (ip22 is the only system that supports a 
> 32-bit kernel at this time).
> 
> 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?
> 
> -Steve


So people have an idea of what's being proposed in regards to Item #D, Attached 
to this message are two text files.  The first shows the current profile setup 
as of today.  The second file shows the proposed reorganization, starting with 
2005.1, of the profiles.

The upside to re-organizing under machine-specific categorization is better 
control for us developers, and easier to follow layout for the users.  Downside 
is, it requires more upkeep on our end (although that upkeep should be 
relatively trivial, and it's unoptimized; an optimized version will likely be 
simpler.).

And as a sidenote, the proposed variant lacks the multilib layout until we 
figure out where it goes.


--Kumba

-- 
Gentoo/MIPS Team Lead
Gentoo Foundation Board of Trustees

"Such is oft the course of deeds that move the wheels of the world: small hands 
do them because they must, while the eyes of the great are elsewhere."  --Elrond

[-- Attachment #2: gentoo-mips-profiles-current.txt --]
[-- Type: text/plain, Size: 1310 bytes --]

  mips/
    |
    |-2004.2/
    |   |-make.defaults
    |   |-parent
    |
    |-2005.0/
    |   |-make.defaults
    |   |-parent
    |
    |-cobalt/
    |   |-2004.2/
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-2005.0/
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-packages
    |   |-parent
    |   |-use.mask
    |   |-virtuals
    |
    |-mips64/
    |   |-2004.2/
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-2005.0/
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-ip28/
    |   |   |-2005.0/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-parent
    |   |
    |   |-multilib/
    |   |   |-2005.1/
    |   |   |   |-make.defaults
    |   |   |   |-parent
    |   |   |
    |   |   |-make.defaults
    |   |   |-parent
    |   |   |-profile.bashrc
    |   |   |-use.mask
    |   |
    |   |-n32/
    |   |   |-2004.2/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-2005.0/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-parent
    |   |
    |   |-parent
    |
    |-packages
    |-parent
    |-use.mask
    |-virtuals

[-- Attachment #3: gentoo-mips-profiles-proposed.txt --]
[-- Type: text/plain, Size: 1695 bytes --]

  mips/
    |
    |-cobalt
    |   |-2005.1
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-n32/
    |   |   |-2005.1/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-parent
    |   |
    |   |-packages
    |   |-parent
    |   |-use.mask
    |   |-virtuals
    |
    |-ip22
    |   |-2005.1
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-n32/
    |   |   |-2005.1/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-parent
    |   |
    |   |-packages
    |   |-parent
    |   |-use.mask
    |   |-virtuals
    |
    |-ip27
    |   |-2005.1
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-n32/
    |   |   |-2005.1/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-parent
    |   |
    |   |-packages
    |   |-parent
    |   |-use.mask
    |   |-virtuals
    |
    |-ip28
    |   |-2005.1
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-n32/
    |   |   |-2005.1/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-parent
    |   |
    |   |-packages
    |   |-parent
    |   |-use.mask
    |   |-virtuals
    |
    |-ip30
    |   |-2005.1
    |   |   |-make.defaults
    |   |   |-parent
    |   |
    |   |-n32/
    |   |   |-2005.1/
    |   |   |   |-make.defaults
    |   |   |   |-packages
    |   |   |   |-parent
    |   |   |
    |   |   |-parent
    |   |
    |   |-packages
    |   |-parent
    |   |-use.mask
    |   |-virtuals
    |
    |-ip32