From: Kevin Zhao <kevin.zhaoshuai@gmail.com>
To: gentoo-catalyst@lists.gentoo.org, basile@opensource.dyc.edu
Subject: Re: [gentoo-catalyst] ppc64el patches
Date: Tue, 5 Jan 2016 12:46:43 +0800 [thread overview]
Message-ID: <CAKe2hGCsK-Z2jTK8DxMYO3cpTB1LcJbt1eL0wdq5ZVwguO9RQg@mail.gmail.com> (raw)
In-Reply-To: <56878696.2030400@opensource.dyc.edu>
Hi Anthony,
Sorry I make a mistake of this. Power8 supports big-endian and
little-endian, also power7 supports both big-endian and little-endian
too.Maybe the power8 and power7 should inherit two arch: ppc64 and
ppc64le. Or maybe we can splite the power8 arch into two different
arch power8 and power8le, the same to power7.
2016-01-02 16:13 GMT+08:00 Anthony G. Basile <basile@opensource.dyc.edu>:
> Hi,
>
> I lost the original patches in my email, so I'll review from the arcvhive:
>
> 1. [gentoo-catalyst][PATCH v1 1/3] Add an subarch ppc64le,as the
> little-endian of ppc64.
> https://archives.gentoo.org/gentoo-catalyst/message/6ade3d1e9625a6e701f535ab80635dba
>
> CHOST looks fine. Are all power8's ppc64le??
>
> 2. [gentoo-catalyst][PATCH v1 2/3] Modify the create iso parameter of
> ppc64le and power8
> https://archives.gentoo.org/gentoo-catalyst/message/766798a56f6560176ce66db2e2243f93
>
> looks okay.
>
>
> 3. [gentoo-catalyst][PATCH v1 3/3] Add a new bootloader file grub 2.00
> and bootinfo.txt for ppc64le
> https://archives.gentoo.org/gentoo-catalyst/message/c481860df994aebcabb969de514b017c
>
> looks okay.
>
>
> --
> Anthony G. Basile, Ph. D.
> Chair of Information Technology
> D'Youville College
> Buffalo, NY 14201
> (716) 829-8197
>
next prev parent reply other threads:[~2016-01-05 4:46 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-02 8:13 [gentoo-catalyst] ppc64el patches Anthony G. Basile
2016-01-05 4:46 ` Kevin Zhao [this message]
2016-01-05 5:54 ` Anthony G. Basile
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=CAKe2hGCsK-Z2jTK8DxMYO3cpTB1LcJbt1eL0wdq5ZVwguO9RQg@mail.gmail.com \
--to=kevin.zhaoshuai@gmail.com \
--cc=basile@opensource.dyc.edu \
--cc=gentoo-catalyst@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