public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: Leno Hou <lenohou@gmail.com>
Cc: gentoo-dev@lists.gentoo.org, gentoo-powerpc@lists.gentoo.org,
	"Anthony G. Basile" <blueness@gentoo.org>
Subject: Re: [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments
Date: Thu, 24 Sep 2015 11:07:39 -0400	[thread overview]
Message-ID: <20150924150739.GB16646@vapier.lan> (raw)
In-Reply-To: <CAGQVrL8ei1py2LW2vNnwQbCa1r4gAeB4mfWg8iLatw9_a7c3Ww@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 662 bytes --]

On 14 Aug 2015 15:52, Leno Hou wrote:
> On Wed, Aug 12, 2015 at 3:47 PM, Mike Frysinger wrote:
> > On 12 Aug 2015 15:20, Leno Hou wrote:
> > > **Most importantly, Any Ideas/steps of how to  porting gentoo on  ppc64le
> > > architecture?**
> >
> > do you have hardware ?  then it's simply a matter of booting Gentoo in it
> > and
> > filing/fixing bugs :).
> >
> 
> YES. We have KVM virtual machine of ppc64le.  Can we booting/filing/fixing
> by KVM ?

KVM is fine.  i'm assuming you can't boot a ppc64le vm when the host is
ppc64be ?  i don't think any Gentoo dev has access to ppc64le hardware,
so we'd rely on ibm to fix bugs and such.
-mike

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2015-09-24 15:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-11  9:22 [gentoo-dev] Introduce ppc64le architecture into gentoo ! please share your comments Leno Hou
2015-08-11  9:49 ` James Le Cuirot
2015-08-11 10:11   ` Leno Hou
2015-08-11 14:33     ` Ian Stakenvicius
2015-08-11 14:44       ` James Le Cuirot
2015-08-11 14:45       ` Anthony G. Basile
2015-08-12  3:50         ` Mike Frysinger
2015-08-12  7:20           ` Leno Hou
2015-08-12  7:47             ` Mike Frysinger
2015-08-12  8:30               ` Anthony G. Basile
2015-09-11 12:01                 ` Leno Hou
2015-09-11 14:18                   ` Ian Stakenvicius
2015-09-13 18:36                   ` Mike Gilbert
2015-09-17  6:53                   ` Leno Hou
2015-09-24 12:23                   ` Leno Hou
2015-09-25 18:27                     ` [gentoo-powerpc] " Luca Barbato
2015-09-26 19:16                     ` Anthony G. Basile
2015-10-21  8:55                       ` Kevin Zhao
2015-11-23 19:54                         ` Richard Yao
2015-09-17  7:06                 ` Leno Hou
2015-08-12  9:46               ` Shuai Zhao
2015-08-12  9:50                 ` [gentoo-powerpc] " Luca Barbato
2015-08-12 23:58               ` 姜渠
2015-08-13  3:19                 ` Mike Frysinger
2015-08-14  7:52               ` Leno Hou
2015-09-24 15:07                 ` Mike Frysinger [this message]
2015-09-25  2:32                   ` Leno Hou
2015-09-25  5:05                     ` Mike Frysinger
2015-09-25  7:34                       ` Anthony G. Basile
2015-09-25  9:09                         ` Leno Hou
2015-09-25 10:59                           ` Anthony G. Basile
2015-09-25 17:21                             ` Anthony G. Basile
2015-08-12  3:50   ` Mike Frysinger

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=20150924150739.GB16646@vapier.lan \
    --to=vapier@gentoo.org \
    --cc=blueness@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=gentoo-powerpc@lists.gentoo.org \
    --cc=lenohou@gmail.com \
    /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