| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA1 |
| 3 |
|
| 4 |
Greetings All, |
| 5 |
|
| 6 |
I'm seeking some direction / advise with regards to ppc64 bringup. |
| 7 |
Specifically as brad and I are bringing up ppc64, it would be nice to |
| 8 |
document bugs / changes inside of the current bug infrastruture on |
| 9 |
bugs.gentoo.org. |
| 10 |
Looking at the bugzilla query page, it would appear at first blush that |
| 11 |
perhaps there are two things that might need to be added. |
| 12 |
|
| 13 |
1) add ppc64 to the Hardware field. This seems obvious. :-) |
| 14 |
|
| 15 |
2) add Gentoo Linux/PPC64 under the Product field. Tho perhaps I'm |
| 16 |
reading into what the meaning of "product" is here. I would have |
| 17 |
expected to see AMD64 / x64_64 here as certainly that's a supported |
| 18 |
architecture on gentoo so maybe product refers more to some cd sold off |
| 19 |
of the gentoo.org page. |
| 20 |
|
| 21 |
Anyway, does this seem reasonable to support this new architecture(*)? |
| 22 |
|
| 23 |
* Yes PPC64 is a "new" architecture. Think of it as ppc64 is to ppc as |
| 24 |
amd64 is to ia32. |
| 25 |
|
| 26 |
If it's not reasonable, what is the *right* way to track issues? |
| 27 |
Should I flood the ppc family with ppc64 bugs that don't apply to them? |
| 28 |
That seems stupid! |
| 29 |
|
| 30 |
Thanks! |
| 31 |
|
| 32 |
Tom Gall |
| 33 |
gentoo-ppc64 -- God started with stage 1, shouldn't you? |
| 34 |
tgall@g.o |
| 35 |
tgall aatt uberh4x0r.org |
| 36 |
tom_gall aatt mac.com |
| 37 |
-----BEGIN PGP SIGNATURE----- |
| 38 |
Version: GnuPG v1.2.3 (Darwin) |
| 39 |
|
| 40 |
iD8DBQFALPzaNM6ZoaBWhQkRAnyCAJ0aFSUk8SGuFrLb8xqdyF25bgihKACgjh58 |
| 41 |
LmPGgeCba+0dtuWaLGhURRY= |
| 42 |
=HOHQ |
| 43 |
-----END PGP SIGNATURE----- |
| 44 |
|
| 45 |
|
| 46 |
-- |
| 47 |
gentoo-dev@g.o mailing list |
Archives