From: Efraim Flashner <efraim@flashner.co.il>
To: Matias Jose Seco Baccanelli <matias_jose_seco@autoproduzioni.net>
Cc: help-guix@gnu.org
Subject: Re: PowerPC e6500 and wip-ppc
Date: Wed, 28 Oct 2020 09:27:01 +0200 [thread overview]
Message-ID: <20201028072701.GY10124@E5400> (raw)
In-Reply-To: <10daf868-b873-7133-c05d-38f6a12c860e@autoproduzioni.net>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
On Wed, Oct 28, 2020 at 08:14:58AM +0100, Matias Jose Seco Baccanelli wrote:
>
> Good morning Guixers !
>
> I was curious to find out if the processor PowerPC e6500[1] is actually
> compatible with the integration of the PowerPC architecture in progress [2],
> is it actually suitable ?
>
> My interest was sparked by a project which is developing an Open Hardware
> PPC Notebook [3], which i'm planning to purchase.
>
> Have a nice Guix day!
>
> Matias
>
>
> [1] https://en.wikipedia.org/wiki/PowerPC_e6500
>
> [2] https://git.savannah.gnu.org/cgit/guix.git/log/?h=wip-ppc
>
> [3] https://www.powerpc-notebook.org/en/
>
The wip-ppc branch is currently targeting the ibook g4 on my desk. There
is ongoing work to target 64-bit PPC, both big and little endian. I
believe that one is closer to merging, there are just some last issues
about reproducibility of the bootstrap binaries. I'm pretty sure once
that is worked out it'll be ready to merge.
The bug report for the PPC64 issue is here: https://issues.guix.gnu.org/41669
--
Efraim Flashner <efraim@flashner.co.il> אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D 14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-10-28 7:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 7:14 PowerPC e6500 and wip-ppc Matias Jose Seco Baccanelli
2020-10-28 7:27 ` Efraim Flashner [this message]
2020-10-29 8:56 ` Matias Jose Seco Baccanelli
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20201028072701.GY10124@E5400 \
--to=efraim@flashner.co.il \
--cc=help-guix@gnu.org \
--cc=matias_jose_seco@autoproduzioni.net \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).