From: Wes <anomaly256@gmail.com>
To: gentoo-ppc-dev@lists.gentoo.org
Subject: [gentoo-ppc-dev] Playstation3 port status woes
Date: Tue, 25 Nov 2008 11:50:56 +1100 [thread overview]
Message-ID: <2899e2610811241650m58877e2dqb5548d884843981d@mail.gmail.com> (raw)
Hello,
I'm wondering, who is the maintainer of the PS3 port? I have a few
issues I'd like to raise. One being the fact that it's been built
targeting entirely the wrong ppc arch. Several sources I've come
across state that the pipelines are so different, that doing this
severely hurts performance, and you are in fact better off targeting
generic ppc than running 970-targeted binaries on CELL/BE. Also,
newer gcc's are available now which have an mcpu=cell target and it
would probably be best to make the playstation3 port..... a
playstation3 port! And not a ps3 / g5 port. These machines differ so
much it is incredibly detrimental to try to support both with the 1
port. Specially when there are better ports existing already for g5.
Also, the only available release is still a stage4, that hasn't been
updated in a whole year. While I commend the efforts of the
maintainer so far (apart from the 970 target mistake), it would be
nice if they actually maintained the port, or handed off to someone
more willing if they've grown bored with it.
It is my impression that this specific port currently does not follow
any Gentoo ideals or philosophy, and is desperately in need of change.
next reply other threads:[~2008-11-25 0:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-25 0:50 Wes [this message]
2008-11-25 1:04 ` [gentoo-ppc-dev] Playstation3 port status woes Joseph Jezak
2008-11-25 1:13 ` Wes
2008-11-25 1:25 ` Joseph Jezak
2008-11-25 1:33 ` Wes
2008-11-25 1:52 ` Nelson Batalha
2008-11-25 13:04 ` Joseph Jezak
2008-11-25 13:05 ` Luca Barbato
2008-11-25 13:56 ` Nelson Batalha
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=2899e2610811241650m58877e2dqb5548d884843981d@mail.gmail.com \
--to=anomaly256@gmail.com \
--cc=gentoo-ppc-dev@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