Brent Baude - Latest comments

In response to: New 2.6.24 ps3-sources and ps3-kernel-bin in cell overlay

oxygen [Visitor] — Mon, 04 Feb 2008 17:08:33 +0000

For me, this (in relation to the prebuild toolchain) sounds like a good reason for a new livecd build.

In response to: PS3 GRP problems resolved

Brent BAUDE [Member] — Wed, 09 Jan 2008 14:54:40 +0000

Since you did not cite what stage you were working with, I cannot respond with complete confidence. I fixed the s/default/defaults thing a while back. Are you seeing this with a current stage, something with a Dec 2007 date? Many of the mirrors have stopped mirroring experimental release materials but have not taken the mirrored content off. So there is a fair amount of old media and stages floating around out there.

The auto/audo bit is something catalyst did/does. I'll look into it. Same with the -J suggestion, although I really thought catalyst did pass the -J.

In response to: PS3 GRP problems resolved

KenKen [Visitor] — Wed, 09 Jan 2008 09:54:39 +0000

On http://overlays.gentoo.org/proj/cell/wiki/InstallGentooOnPS3, there is a small typo in the fstab config.

the line:
none /spu spufs default 0 0
should be changed to:
none /spu spufs defaults 0 0

otherwise any program trying to load SPU code will give an error like:
spu_create() Invalid argument

In the stage4 tarball, the fstab has the correct spufs entry, but has a type in one of the "auto" columns where it says "audo".

Thirdly, the LiveCD should be created with the -J flag (Joliet) for mkisofs, as that will enable the PS3 to correctly read otheros.bld from the CD, if it is placed in PS3/otheros/otheros.bld.

I'm not sure who maintains these packages, but there is no feedback form in the wiki page.

In response to: My early Christmas present for PS3 users

Kyle [Visitor] — Wed, 19 Dec 2007 13:58:33 +0000

Hey Ranger,

I noticed that the mirrors currently contain no disk images and still contain the old stage 4 tarballs under experimental/ppc64. Any idea when those should be back up?

Thanks,
Kyle

In response to: My early Christmas present for PS3 users

Brent BAUDE [Member] — Sun, 16 Dec 2007 13:28:48 +0000

We're still a little ways from officially supporting PS3 as a ppc64 platform. I get this question a fair amount so it's worth responding to. The inhibiting factors right now are:

- PS3 required ebuilds were just moved from the cell over to portage and are still ~
- Mainline does not fully support everything we need/want for PS3. We're hoping for 2.6.25. For the record, we also hoped 2.6.23 and 2.6.24.
- Without Gcc-4.3, we lack the cell optimizations for mcpu and mtune. Right now we pass 970 and altivec. This goes in-line with the comment I made in my earlier post about inching towards a profile.

In response to: My early Christmas present for PS3 users

Josh Saddler [Member] — Sun, 16 Dec 2007 03:30:10 +0000

Cool!

Though as always, keep in touch with the docs team and let us know the moment it becomes an officially supported arch, whether on its own or wrapped into ppc/ppc64. That way we can get some stuff into the handbooks.

The more officially-supported Gentoo systems, the merrier! :)

In response to: Semi-optimized PS3 stages

Fallen- [Visitor] — Sat, 22 Sep 2007 15:26:21 +0000

Hello, I have my PS3 with Gentoo now :D and I want to optimize CFLAGS to install other things like Gnome.Should I replace mcpu=cell or do I leave mcpu=970? on:
http://gentoo-wiki.com/Safe_Cflags#Cell_Broadband_Engine_.28Playstation_3.29
the recommendation is cell.

Thank you for your help! Best regards.

In response to: POWER6 support

slouck [Visitor] — Thu, 30 Aug 2007 00:09:53 +0000

Hey Brent we just received our power6 boxes a couple weeks ago. Myself and one of our Unix admins are interested in installing a Linux LPAR for testing before these systems go into production. Id rather not use SUSE and am partial to gentoo anyways which is how I stumbled on this thread. I could offer some feedback on the 2007.0 profile and try and work out the build errors albeit with the limited knowledge that I possess when it comes to debugging code.