From: Lauri Kasanen <cand@gmx.com>
To: libre-riscv-dev@lists.libre-riscv.org
Subject: Re: [libre-riscv-dev] PPC on Talos and Playstation 3
Date: Mon, 30 Mar 2020 10:32:26 +0300
Message-ID: <20200330103226.4cc14532f22a48719e25ea8f@gmx.com> (raw)
In-Reply-To: <CAC2bXD4DoabbWWc4vZCdrjEwOR7TG8DhrFMnU-0=uktSR23Q0A@mail.gmail.com>
On Mon, 30 Mar 2020 00:12:40 -0700
Jacob Lifshay <programmerjake@gmail.com> wrote:
> On Sun, Mar 29, 2020, 23:55 Lauri Kasanen <cand@gmx.com> wrote:
> > Remember that Sony blocked OtherOS in a specific firmware version, and
> > newer firmwares were required for running newer games. So finding a PS3
> > that can be used will be hard.
> >
> > However, WiiUs are a viable option for recent-ish power hw for cheap.
>
> The Wii U is a tri-core 32-bit PPC with 2GB of ddr3. Additionally, Nintendo
> is not likely to support installing custom software.
>
> I personally think Power Macs are probably the best option since they can
> use standard PC hardware (eg. ram, sata disk, pci cards (maybe pcie?),
> external display, usb, ethernet), they actually are designed to be able to
> install your own OS, they have 1, 2, or 4 core 64-bit Power processors, and
> they are relatively inexpensive -- I saw one for $100 last I checked.
The specs quote 64-bit FPU, so it's not entirely 32-bit. Nintendo
doesn't need to, they have abandoned the console, and in its last state
it was still hackable, unlike the PS3. Therefore it's safe to buy any
(NTSC, I haven't checked PAL) WiiU if you intend to hack it, vs very
careful checking to find that rare low-firmware PS3.
PowerMacs are fine, though old and power-hogging.
- Lauri
_______________________________________________
libre-riscv-dev mailing list
libre-riscv-dev@lists.libre-riscv.org
http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev
next prev parent reply index
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-29 20:17 Immanuel, Yehowshua U
2020-03-29 20:20 ` Immanuel, Yehowshua U
2020-03-29 20:35 ` Jacob Lifshay
2020-03-29 21:01 ` Luke Kenneth Casson Leighton
2020-03-30 6:56 ` Lauri Kasanen
2020-03-30 7:12 ` Jacob Lifshay
2020-03-30 7:32 ` Lauri Kasanen [this message]
2020-03-30 7:52 ` Jacob Lifshay
2020-03-30 8:05 ` Lauri Kasanen
2020-03-30 18:07 ` Jacob Lifshay
2020-03-30 18:12 ` Immanuel, Yehowshua U
2020-03-30 18:16 ` Jacob Lifshay
2020-03-30 18:35 ` Immanuel, Yehowshua U
2020-03-30 18:36 ` Immanuel, Yehowshua U
2020-03-30 18:46 ` Luke Kenneth Casson Leighton
2020-03-30 18:57 ` Immanuel, Yehowshua U
2020-03-30 19:09 ` Luke Kenneth Casson Leighton
2020-03-30 19:20 ` Immanuel, Yehowshua U
2020-03-30 19:25 ` Luke Kenneth Casson Leighton
2020-03-30 19:35 ` Immanuel, Yehowshua U
2020-03-30 19:45 ` Jacob Lifshay
2020-03-30 19:46 ` Immanuel, Yehowshua U
2020-03-30 22:02 ` Luke Kenneth Casson Leighton
2020-03-30 19:01 ` Jacob Lifshay
2020-03-30 19:20 ` Luke Kenneth Casson Leighton
2020-03-31 21:57 ` Michael Nolan
2020-03-31 23:01 ` Luke Kenneth Casson Leighton
2020-04-01 0:23 ` Immanuel, Yehowshua U
2020-04-01 0:44 ` [libre-riscv-dev] additional ddr3 interfaces Jacob Lifshay
2020-04-01 0:47 ` Immanuel, Yehowshua U
2020-04-01 1:01 ` Jacob Lifshay
2020-04-01 11:10 ` Luke Kenneth Casson Leighton
2020-04-01 15:19 ` Staf Verhaegen
2020-04-01 15:42 ` Luke Kenneth Casson Leighton
2020-04-01 11:00 ` [libre-riscv-dev] PPC on Talos and Playstation 3 Luke Kenneth Casson Leighton
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=20200330103226.4cc14532f22a48719e25ea8f@gmx.com \
--to=cand@gmx.com \
--cc=libre-riscv-dev@lists.libre-riscv.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
Libre RISC-V Mailing list Archives (accessible via public-inbox)
Archives are clonable: git clone --mirror https://inbox.libre-soc.org/libre-riscv-dev
Example config snippet for mirrors
AGPL code for this site: git clone https://public-inbox.org/public-inbox.git