gc-linux-devel — Development-related discussion.

[Gc-linux-devel] FASD project: Online survey launched

[<ben...@id...>]

Dear Open Source developer

I am doing a research project on "Fun and Software Development" in which I kindly invite you to participate.
You will find the online survey under http://fasd.ethz.ch/qsf/. The questionnaire consists of 53 questions and you will need about 15 minutes to complete it.

With the FASD project (Fun and Software Development) we want to define the motivational significance of fun when software developers decide to engage in Open Source projects. What is special about our research project is that a similar survey is planned with software developers in commercial firms. This procedure allows the immediate comparison between the involved individuals and the conditions of production of these two development models. Thus we hope to obtain substantial new insights to the phenomenon of Open Source Development.


With many thanks for your participation,
Benno Luthiger


PS:
The results of the survey will be published under http://www.isu.unizh.ch/fuehrung/blprojects/FASD/.
We have set up the mailing list fa...@we... for this study. Please see http://fasd.ethz.ch/qsf/mailinglist_en.html for registration to this mailing list.

_______________________________________________________________________

Benno Luthiger
Swiss Federal Institute of Technology Zurich
8092 Zurich

Mail: benno.luthiger(at)id.ethz.ch
_______________________________________________________________________

[Gc-linux-devel] framebuffer driver - help needed

[Groepaz <gr...@gm...>]

i'm playing with gamecubefb.c for a couple of days now and am
kindof stuck :/ maybe someone here has an idea, or can point
me to some information (although i've searched the net extensivly
with no success :/). if someone has implemented a framebuffer
driver for any device that doesnt have a straight rgb-framebuffer
to hardware-framebuffer mapping (like the gc) before, or knows a
person why did so, please speak up :=P

the problem is related to the fact that the framebuffer of the
gamecube is in a different format than rgb and thus can not be
directly mmap'ped and used by an application. (and the framebuffer
console). the interface in the driver used to handle this kind
of thing is located in fb_info->pixmap->outbuf and 
fb_info->pixmap->inbuf (note: the current driver incorrectly uses
a different function, it patches the interface that writes _into_
the linear rgb frame buffer, not the one that reads from it and
moves the data to the hardware buffer). whatever, changing this
is no problem, and works great with the framebuffer console (and
also magically removes the kludges from fb.h) - but the problem
with applications that mmap the framebuffer remains. (but unlike
with the current driver you wont get a picture with messed up
colors, but no picture at all since the data wont get moved
to the hardware buffer)

so, from my understanding there must be some mechanism that
addresses this problem (some function that gets called whenever a
portion of the rgb framebuffer needs to be moved to the hardware
framebuffer for example). the closest to that i could find was
the "sync" interface, but this doesnt cut it either (and well,
yes, its probably wrong for that kind of thing :)). mmmh and
there is some flag to distinguish between "memory mapped" and
"io mapped" graphics memory that look suspicous aswell, but
i couldnt really figure out what difference they make either,
nor what kind of interface is related to that :(

oh well...any hints are highly appriciated :)

gpz

[Gc-linux-devel] Re: [Fastboot] GameCube/PPC32 kexec port sources

[Adam L. <ag...@us...>]

On Tue, 2004-05-18 at 14:14, Albert Herranz wrote:
> Hi,
> 
> Here you can find my kexec port for the
> GameCube/PPC32.
> See README_PLEASE for additional information.
> 
> http://www.gc-linux.org/down/isobel/kexec-2.6.6-isobel/
> 
> Any comments are welcome!

This seems like a very straightforward port.  The GameCube does not have
an OpenFirmware interface, right?  Factoring OF out of the picture sure
makes life easier :)

-- 
Adam Litke - (agl at us.ibm.com)
IBM Linux Technology Center

[Gc-linux-devel] GameCube/PPC32 kexec port sources

[<alb...@ya...>]

Hi,

Here you can find my kexec port for the
GameCube/PPC32.
See README_PLEASE for additional information.

http://www.gc-linux.org/down/isobel/kexec-2.6.6-isobel/

Any comments are welcome!

Cheers,
Albert



		
______________________________________________________________________
Correo Yahoo! - 6MB, más protección contra el spam ¡Gratis!
http://correo.yahoo.es

[Gc-linux-devel] [RFT] Gekko (750CXe) processor revisions

[<a.o...@bl...>]

Hi,

Gekko is currently being enumerated as 745/755 when it is actually
a 750CXe; PVR reads 0x00083214. This has been corrected, but before
I may commit anything, it'd be interesting to know if there is in fact
more than one revision of the processor out there.

So, if your /proc/cpuinfo does not look anything like the one below
(emphasis on PVR), don't hesitate to speak up:

  # cat /proc/cpuinfo
  processor       : 0
  cpu             : 745/755
  revision        : 50.20 (pvr 0008 3214)
  bogomips        : 968.70
  vendor          : IBM
  machine         : Nintendo GameCube

Re: [Gc-linux-devel] cvs broken?

[<a.o...@bl...>]

On Saturday 15 May 2004 05:08, Groepaz wrote:
> after some time i tried to compile a recent version of gclinux tonight
> and run into some odd trouble.... i grabbed the 2.6.6 kernel, copied
> the cvs stuff over it as usual, copied the gamecube_default config
> to .config etc... then when i make vmlinux i get
>
> drivers/built-in.o(.text+0x39d84): In function `gamecubefb_writel':
> : undefined reference to `fb_writel_real'
>
> putting a #define __powerpc__ on top of gamecubefb.c "fixes" it (as
> in, makes it compile atleast) but then i get a console with messed
> up colors :/ also the network stuff doesnt seem to work, although
> the stuff it prints out looks all perfectly ok. :/
>
> i'm really wondering what i am doing wrong....or is the source
> really broken at this point? :)

On Sat, May 15, 2004 at 05:56:36AM +0200, Groepaz wrote:
> mmmh must be.... even after a complete clean recompile...same
> problem :/ looks like __powerpc__ isnt defined at all (but it
> should be i suppose)... i'd guess that this causes all sorta
> funny problems so uhm....how to fix? :)
 
Your compiler is broken. I won't even pretend to know where the exact
breakage is; you'll have to resolve that one with the maintainer.

That said, the recommended compiler, for both kernel and userspace,
is the uClibc one: http://uclibc.org/toolchains.html

Although building from source is recommended, a pre-built one is also
available: http://gc-linux.org/down/ppc-linux-uclibc-toolchain.tar.bz2
with the only bonus being it comes with a cross-debugger for those who
might find it of use. (hint: buildroot)

Consequently, the top-level Makefile in CVS is now gone as it's
clearly toolchain biased. You'll now have to do something like:

  $ export ARCH=ppc CROSS_COMPILE=$my-powerpc-toolchain-
  $ make

or:

  $ make ARCH=ppc CROSS_COMPILE=$my-powerpc-toolchain-

or just edit the Makefile to match your setup.

	Arthur

[Gc-linux-devel] Fixed/update sound driver

[Steven L. <st...@kr...>]

Hi,

Groupaz has fixed/updated the sounddriver.

Please test it, it can be found here: http://www.gc-linux.org/down/gamecube_audio.c

Steven

PS.
I'm mailing since groupaz is not able to. His mailprovider seems to be having some problems.

Re: [Gc-linux-devel] cvs broken?

[Groepaz <gr...@gm...>]

On Saturday 15 May 2004 17:18, Torben Nielsen wrote:
> I got the same problem. It seems to have happened after the upgrade to
> 2.6.5... At the moment I'm running the kernel with framebuffer support
> disabled.

yay...the problem seems to be the toolchain, which doesnt define __powerpc__.

i fixed it now by changing

CC		= $(CROSS_COMPILE)gcc -D__powerpc__

to

Re: [Gc-linux-devel] cvs broken?

[Torben N. <tr...@bi...>]

I got the same problem. It seems to have happened after the upgrade to
2.6.5... At the moment I'm running the kernel with framebuffer support
disabled.

For the NFS root stuff I use

CONFIG_CMDLINE="root=/dev/nfs nfsroot=192.168.001.048:/nfsroot/cube
video=gamecubefb ip=192.168.001.005:192.168.001.048"

where 192.168.001.048 is the nfs server, and 192.168.001.005 is the
cube.

On Sat, 2004-05-15 at 05:56, Groepaz wrote:
> On Saturday 15 May 2004 05:08, Groepaz wrote:
> > after some time i tried to compile a recent version of gclinux tonight
> > and run into some odd trouble.... i grabbed the 2.6.6 kernel, copied
> > the cvs stuff over it as usual, copied the gamecube_default config
> > to .config etc... then when i make vmlinux i get
> >
> > drivers/built-in.o(.text+0x39d84): In function `gamecubefb_writel':
> > : undefined reference to `fb_writel_real'
> >
> > putting a #define __powerpc__ on top of gamecubefb.c "fixes" it (as
> > in, makes it compile atleast) but then i get a console with messed
> > up colors :/ also the network stuff doesnt seem to work, although
> > the stuff it prints out looks all perfectly ok. :/
> >
> > i'm really wondering what i am doing wrong....or is the source
> > really broken at this point? :)
> 
> mmmh must be.... even after a complete clean recompile...same
> problem :/ looks like __powerpc__ isnt defined at all (but it
> should be i suppose)... i'd guess that this causes all sorta
> funny problems so uhm....how to fix? :)
> 
> gpz
> 
> ps: also... could someone please tell me the boot options for using
> a nfs-root (missing in stevens guide unfortunatly)... i really dont
> want to run a DHCP server either if possible...mmh :)

Re: [Gc-linux-devel] cvs broken?

[Florian Z. <Flo...@ep...>]

I had the same problem compiling, I went on the problem on another way. It 
seems the funktion fb_writel_real gets not defined in linux/fb.h so I 
manually defined it in gamecubefb.c. But I can't figure out why it doesn't 
get defined properly, perhaps a dev should tell you.

PS.: I don't know if this workaround fixes the messed up colors, because 
it uses another fb_writel funktion with this fix, but it could.

Am Sat, 15 May 2004 05:56:36 +0200 hat Groepaz <gr...@gm...> 
geschrieben:

> On Saturday 15 May 2004 05:08, Groepaz wrote:
>> after some time i tried to compile a recent version of gclinux tonight
>> and run into some odd trouble.... i grabbed the 2.6.6 kernel, copied
>> the cvs stuff over it as usual, copied the gamecube_default config
>> to .config etc... then when i make vmlinux i get
>>
>> drivers/built-in.o(.text+0x39d84): In function `gamecubefb_writel':
>> : undefined reference to `fb_writel_real'
>>
>> putting a #define __powerpc__ on top of gamecubefb.c "fixes" it (as
>> in, makes it compile atleast) but then i get a console with messed
>> up colors :/ also the network stuff doesnt seem to work, although
>> the stuff it prints out looks all perfectly ok. :/
>>
>> i'm really wondering what i am doing wrong....or is the source
>> really broken at this point? :)
>
> mmmh must be.... even after a complete clean recompile...same
> problem :/ looks like __powerpc__ isnt defined at all (but it
> should be i suppose)... i'd guess that this causes all sorta
> funny problems so uhm....how to fix? :)
>
> gpz
>
> ps: also... could someone please tell me the boot options for using
> a nfs-root (missing in stevens guide unfortunatly)... i really dont
> want to run a DHCP server either if possible...mmh :)
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by: SourceForge.net Broadband
> Sign-up now for SourceForge Broadband and get the fastest
> 6.0/768 connection for only $19.95/mo for the first 3 months!
> http://ads.osdn.com/?ad_id=2562&alloc_id=6184&op=click
> _______________________________________________
> Gc-linux-devel mailing list
> Gc-...@li...
> https://lists.sourceforge.net/lists/listinfo/gc-linux-devel



-- 
Florob

(o_
//\
V_/_

Re: [Gc-linux-devel] cvs broken?

[Groepaz <gr...@gm...>]

On Saturday 15 May 2004 05:08, Groepaz wrote:
> after some time i tried to compile a recent version of gclinux tonight
> and run into some odd trouble.... i grabbed the 2.6.6 kernel, copied
> the cvs stuff over it as usual, copied the gamecube_default config
> to .config etc... then when i make vmlinux i get
>
> drivers/built-in.o(.text+0x39d84): In function `gamecubefb_writel':
> : undefined reference to `fb_writel_real'
>
> putting a #define __powerpc__ on top of gamecubefb.c "fixes" it (as
> in, makes it compile atleast) but then i get a console with messed
> up colors :/ also the network stuff doesnt seem to work, although
> the stuff it prints out looks all perfectly ok. :/
>
> i'm really wondering what i am doing wrong....or is the source
> really broken at this point? :)

mmmh must be.... even after a complete clean recompile...same
problem :/ looks like __powerpc__ isnt defined at all (but it
should be i suppose)... i'd guess that this causes all sorta
funny problems so uhm....how to fix? :)

gpz

ps: also... could someone please tell me the boot options for using
a nfs-root (missing in stevens guide unfortunatly)... i really dont
want to run a DHCP server either if possible...mmh :)

[Gc-linux-devel] cvs broken?

[Groepaz <gr...@gm...>]

after some time i tried to compile a recent version of gclinux tonight
and run into some odd trouble.... i grabbed the 2.6.6 kernel, copied
the cvs stuff over it as usual, copied the gamecube_default config
to .config etc... then when i make vmlinux i get

drivers/built-in.o(.text+0x39d84): In function `gamecubefb_writel':
: undefined reference to `fb_writel_real'

putting a #define __powerpc__ on top of gamecubefb.c "fixes" it (as
in, makes it compile atleast) but then i get a console with messed
up colors :/ also the network stuff doesnt seem to work, although
the stuff it prints out looks all perfectly ok. :/

i'm really wondering what i am doing wrong....or is the source
really broken at this point? :)

gpz

Re: [Gc-linux-devel] Availablity of PSO

[Jesse K. <j.k...@ti...>]

I ordered it at bol.com
First time I ordered it it took them three weeks to tell me that it
wasn't available anymore, but then I ordered it again and within a few
days I recieved it. Strange.... Well anyway, it's worth tryin.

Jesse

On Sun, 2004-05-09 at 15:25, Adrian McMenamin wrote:
> I am having some difficulty tracking this down in the UK. Gertting a BBA was 
> easy in comparison.
> 
> Anybody else in the UK got one and where did they source it from?
> 
> Adrian
> 
> 
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to deliver
> higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> Gc-linux-devel mailing list
> Gc-...@li...
> https://lists.sourceforge.net/lists/listinfo/gc-linux-devel

Re: [Gc-linux-devel] Availablity of PSO

[Sascha K. <ma...@sa...>]

Or get the PSO 1&2 Plus Version ( 
http://www.lik-sang.com/info.php?category=79&products_id=3780&lsaid=269103 
).
It is only available as JAP version, but can be switched to english (or 
even german, spanish or french!) easily.
All you need to start is the Freeloader or a modded (or japanese) Cube...

And if you need any help with the menus, don't hesitate to ask me...

Regards
Sascha


David Remahl wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> On 9 maj 2004, at 15.25, Adrian McMenamin wrote:
>
>> I am having some difficulty tracking this down in the UK. Gertting a  
>> BBA was
>> easy in comparison.
>>
>> Anybody else in the UK got one and where did they source it from?
>>
>> Adrian
>
>
> I got mine from <http://www.amazon.co.uk/>. However, now it seems 
> that  it is out of stock...
>
> <http://www.amazon.co.uk/exec/obidos/ASIN/B000086F7J/202-9957240 - 
> -7673404e>
>
> Perhaps you should check if there's anything on ebay.co.uk...
>
> / David
>
> - --- PGP key information---
> pub  1024D/ 87256085 2003/06/12 David Remahl <da...@re...>
> Web: http://ittpoi.com/david_remahl.asc
> Fingerprint: 0C38 293C 86A9 7756 9CEA  4ED6 1651 620E 8725 6085
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.2.3 (Darwin)
>
> iD8DBQFAnjT9FlFiDoclYIURApinAJ9bNwofxXjspne6diTx6Nt3CwJQhgCaA2O+
> 91/sxvKDe954qB5Q8r3YElY=
> =YSrr
> -----END PGP SIGNATURE-----
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
> deliver
> higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> Gc-linux-devel mailing list
> Gc-...@li...
> https://lists.sourceforge.net/lists/listinfo/gc-linux-devel
>
>

Re: [Gc-linux-devel] Availablity of PSO

[David R. <da...@it...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 9 maj 2004, at 15.25, Adrian McMenamin wrote:

> I am having some difficulty tracking this down in the UK. Gertting a  
> BBA was
> easy in comparison.
>
> Anybody else in the UK got one and where did they source it from?
>
> Adrian

I got mine from <http://www.amazon.co.uk/>. However, now it seems that  
it is out of stock...

<http://www.amazon.co.uk/exec/obidos/ASIN/B000086F7J/202-9957240 
- -7673404e>

Perhaps you should check if there's anything on ebay.co.uk...

/ David

- --- PGP key information---
pub  1024D/ 87256085 2003/06/12 David Remahl <da...@re...>
Web: http://ittpoi.com/david_remahl.asc
Fingerprint: 0C38 293C 86A9 7756 9CEA  4ED6 1651 620E 8725 6085
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (Darwin)

iD8DBQFAnjT9FlFiDoclYIURApinAJ9bNwofxXjspne6diTx6Nt3CwJQhgCaA2O+
91/sxvKDe954qB5Q8r3YElY=
=YSrr
-----END PGP SIGNATURE-----

[Gc-linux-devel] Availablity of PSO

[Adrian M. <ad...@mc...>]

I am having some difficulty tracking this down in the UK. Gertting a BBA =
was=20
easy in comparison.

Anybody else in the UK got one and where did they source it from?

Adrian

Re: [Gc-linux-devel] Memory card block device driver

[Groepaz <gr...@gm...>]

On Saturday 08 May 2004 17:04, Torben Nielsen wrote:

> Thanks for the tip. Now I wonder, is there any (easy) way to reformat
> the card, or should I just try to restore the backup I made of the card
> before I started writing to it?

if you dont mind loosing the data, just pop it in and go to the memorycard
manager in the bios...it will then report the card as corrupted and offer
to reformat it. (its unknown how to do that in your own software...feel
free to do some research on that topic :))

gpz

Re: [Gc-linux-devel] Memory card block device driver

[Torben N. <tr...@bi...>]

On Sat, 2004-05-08 at 17:04, Torben Nielsen wrote:
> On Sat, 2004-05-08 at 13:14, Groepaz wrote:
> > On Saturday 08 May 2004 12:20, Torben Nielsen wrote:
> > > I just checked a memory card block device driver into the CVS.
> > > It cannot unlock the cards, so these are threated like fixed disks
> > > (i.e. they must be present a boot so PSO unlocks them).
> > > I haven't done extensive testing, but I was actually able to copy a
> > > standard Nintendo 59 memory card to a blank card like this:
> > >
> > > 	mknod /tmp/card0 b 254 0
> > > 	mknod /tmp/card1 b 254 1
> > > 	dd if=/tmp/card0 of=/tmp/card1
> > >
> > > where 254 is the major device number assigned to the driver. Check
> > > /proc/devices, there should be a line like this:
> > >
> > > 254 memcard
> > >
> > > Feel free to test it, but please don't use a memory card with important
> > > data on it.
> > 
> > tip: dont copy the very first sector of the card to another card if
> > you plan using it outside linux (first sector contains the unique
> > card ID or decryption/unlock seed or whatever it is :))
> > 
> > gpz
> > 
> > 
> 
> Thanks for the tip. Now I wonder, is there any (easy) way to reformat
> the card, or should I just try to restore the backup I made of the card
> before I started writing to it?
> 
> 
OK, I was lucky... The cube just suggested that I formatted the card, so I did that.

Re: [Gc-linux-devel] Memory card block device driver

[Torben N. <tr...@bi...>]

On Sat, 2004-05-08 at 13:14, Groepaz wrote:
> On Saturday 08 May 2004 12:20, Torben Nielsen wrote:
> > I just checked a memory card block device driver into the CVS.
> > It cannot unlock the cards, so these are threated like fixed disks
> > (i.e. they must be present a boot so PSO unlocks them).
> > I haven't done extensive testing, but I was actually able to copy a
> > standard Nintendo 59 memory card to a blank card like this:
> >
> > 	mknod /tmp/card0 b 254 0
> > 	mknod /tmp/card1 b 254 1
> > 	dd if=/tmp/card0 of=/tmp/card1
> >
> > where 254 is the major device number assigned to the driver. Check
> > /proc/devices, there should be a line like this:
> >
> > 254 memcard
> >
> > Feel free to test it, but please don't use a memory card with important
> > data on it.
> 
> tip: dont copy the very first sector of the card to another card if
> you plan using it outside linux (first sector contains the unique
> card ID or decryption/unlock seed or whatever it is :))
> 
> gpz
> 
> 

Thanks for the tip. Now I wonder, is there any (easy) way to reformat
the card, or should I just try to restore the backup I made of the card
before I started writing to it?

Re: [Gc-linux-devel] Memory card block device driver

[Groepaz <gr...@gm...>]

On Saturday 08 May 2004 12:20, Torben Nielsen wrote:
> I just checked a memory card block device driver into the CVS.
> It cannot unlock the cards, so these are threated like fixed disks
> (i.e. they must be present a boot so PSO unlocks them).
> I haven't done extensive testing, but I was actually able to copy a
> standard Nintendo 59 memory card to a blank card like this:
>
> 	mknod /tmp/card0 b 254 0
> 	mknod /tmp/card1 b 254 1
> 	dd if=/tmp/card0 of=/tmp/card1
>
> where 254 is the major device number assigned to the driver. Check
> /proc/devices, there should be a line like this:
>
> 254 memcard
>
> Feel free to test it, but please don't use a memory card with important
> data on it.

tip: dont copy the very first sector of the card to another card if
you plan using it outside linux (first sector contains the unique
card ID or decryption/unlock seed or whatever it is :))

gpz

[Gc-linux-devel] Memory card block device driver

[Torben N. <tr...@bi...>]

I just checked a memory card block device driver into the CVS.
It cannot unlock the cards, so these are threated like fixed disks 
(i.e. they must be present a boot so PSO unlocks them).
I haven't done extensive testing, but I was actually able to copy a
standard Nintendo 59 memory card to a blank card like this:

	mknod /tmp/card0 b 254 0
	mknod /tmp/card1 b 254 1
	dd if=/tmp/card0 of=/tmp/card1

where 254 is the major device number assigned to the driver. Check
/proc/devices, there should be a line like this:

254 memcard

Feel free to test it, but please don't use a memory card with important
data on it.

[Gc-linux-devel] Gekko binutils patch

[Anders M M. <amm...@cc...>]

Hi, this is a in-progress patch for adding support for the Gekko
instructions to binutils (as and objdump). It's not well-tested at all,
and it's incomplete because the load and store instructions are still
missing because I don't really understand their encoding (eg. what do the
W and I fields represent?)
 The patch is against current CVS, and any help testing/fixing/whatever is
appreciated.

To assemble Gekko instructions, pass "-mgekko" to as, and to disassemble
them pass "-Mgekko" to objdump.

-Anders

Index: gas/config/tc-ppc.c
===================================================================
RCS file: /cvs/src/src/gas/config/tc-ppc.c,v
retrieving revision 1.87
diff -u -r1.87 tc-ppc.c
--- gas/config/tc-ppc.c	7 Apr 2004 04:50:15 -0000	1.87
+++ gas/config/tc-ppc.c	2 May 2004 15:06:17 -0000
@@ -914,6 +914,9 @@
   /* -many means to assemble for any architecture (PWR/PWRX/PPC).  */
   else if (strcmp (arg, "any") == 0)
     ppc_cpu |= PPC_OPCODE_ANY;
+  else if (strcmp (arg, "gekko") == 0)
+      ppc_cpu = (PPC_OPCODE_CLASSIC | PPC_OPCODE_PPC
+        | PPC_OPCODE_32 | PPC_OPCODE_GEKKO);
   else
     return 0;

@@ -1106,6 +1109,7 @@
 -maltivec		generate code for AltiVec\n\
 -me500, -me500x2	generate code for Motorola e500 core complex\n\
 -mspe			generate code for Motorola SPE instructions\n\
+-mgekko			generate code for Gamecube Gekko\n\
 -mregnames		Allow symbolic names for registers\n\
 -mno-regnames		Do not allow symbolic names for registers\n"));
 #ifdef OBJ_ELF
@@ -1150,6 +1154,9 @@
 	  else
 	    ppc_cpu |= PPC_OPCODE_PPC | PPC_OPCODE_CLASSIC | PPC_OPCODE_32;
 	}
+    else if (strcmp (default_cpu, "gekko") == 0)
+        ppc_cpu |= (PPC_OPCODE_PPC | PPC_OPCODE_CLASSIC | PPC_OPCODE_32
+                    | PPC_OPCODE_GEKKO);
       else
 	as_fatal (_("Unknown default cpu = %s, os = %s"),
 		  default_cpu, default_os);
Index: include/opcode/ppc.h
===================================================================
RCS file: /cvs/src/src/include/opcode/ppc.h,v
retrieving revision 1.17
diff -u -r1.17 ppc.h
--- include/opcode/ppc.h	16 Mar 2004 00:58:42 -0000	1.17
+++ include/opcode/ppc.h	25 Apr 2004 10:37:58 -0000
@@ -134,6 +134,9 @@
 /* Opcode is supported by machine check APU.  */
 #define PPC_OPCODE_RFMCI	  0x800000

+/* Opcode is only supported by PowerPC Gekko processor */
+#define PPC_OPCODE_GEKKO         0x1000000
+
 /* A macro to extract the major opcode from an instruction.  */
 #define PPC_OP(i) (((i) >> 26) & 0x3f)

Index: opcodes/ppc-dis.c
===================================================================
RCS file: /cvs/src/src/opcodes/ppc-dis.c,v
retrieving revision 1.16
diff -u -r1.16 ppc-dis.c
--- opcodes/ppc-dis.c	16 Mar 2004 00:58:41 -0000	1.16
+++ opcodes/ppc-dis.c	2 May 2004 10:59:25 -0000
@@ -91,6 +91,15 @@
 	dialect |= PPC_OPCODE_64;
     }

+  if (info->disassembler_options)
+  {
+      if (strstr (info->disassembler_options, "gekko") != NULL)
+      {
+          dialect &= ~(PPC_OPCODE_ALTIVEC | PPC_OPCODE_403);
+          dialect |= PPC_OPCODE_GEKKO;
+      }
+  }
+
   ((struct dis_private *) &info->private_data)->dialect = dialect;
   return dialect;
 }
@@ -312,4 +321,5 @@
   fprintf (stream, "  power4                   Disassemble the Power4 instructions\n");
   fprintf (stream, "  32                       Do not disassemble 64-bit instructions\n");
   fprintf (stream, "  64                       Allow disassembly of 64-bit instructions\n");
+  fprintf (stream, "  gekko                    Disassemble the Gamecube Gekko instructions\n");
 }
Index: opcodes/ppc-opc.c
===================================================================
RCS file: /cvs/src/src/opcodes/ppc-opc.c,v
retrieving revision 1.69
diff -u -r1.69 ppc-opc.c
--- opcodes/ppc-opc.c	30 Apr 2004 07:14:40 -0000	1.69
+++ opcodes/ppc-opc.c	1 May 2004 17:40:37 -0000
@@ -1786,6 +1786,7 @@
 #define PPCCHLK	PPC_OPCODE_CACHELCK
 #define PPCCHLK64	PPC_OPCODE_CACHELCK | PPC_OPCODE_BOOKE64
 #define PPCRFMCI	PPC_OPCODE_RFMCI
+#define PPCGEKKO        PPC_OPCODE_GEKKO

 /* The opcode table.

@@ -2343,6 +2344,61 @@

 { "evdivws",  VX(4, 1222), VX_MASK,	PPCSPE,		{ RS, RA, RB } },
 { "evdivwu",  VX(4, 1223), VX_MASK,	PPCSPE,		{ RS, RA, RB } },
+
+{ "ps_abs",     XRC(4,264,0),XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_abs.",    XRC(4,264,1),XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_add",     A(4,21,0),   AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_add.",    A(4,21,1),   AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_cmpo0",   X(4,32),X_MASK|(3<<21), PPCGEKKO,       { BF, FRA, FRB } },
+{ "ps_cmpo1",   X(4,96),X_MASK|(3<<21), PPCGEKKO,       { BF, FRA, FRB } },
+{ "ps_cmpu0",   X(4,0), X_MASK|(3<<21), PPCGEKKO,       { BF, FRA, FRB } },
+{ "ps_cmpu1",   X(4,64),X_MASK|(3<<21), PPCGEKKO,       { BF, FRA, FRB } },
+{ "ps_div",     A(4,18,0),   AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_div.",    A(4,18,1),   AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge00", A(4,528,0),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge00.",A(4,528,1),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge01", A(4,560,0),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge01.",A(4,560,1),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge10", A(4,597,0),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge10.",A(4,597,1),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge11", A(4,624,0),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_merge11.",A(4,624,1),  AFRC_MASK, PPCGEKKO,       { FRT, FRA, FRB } },
+{ "ps_mr",      XRC(4,72,0), XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_mr.",     XRC(4,72,1), XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_nabs",    XRC(4,136,0),XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_nabs.",   XRC(4,136,1),XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_neg",     XRC(4,40,0), XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_neg.",    XRC(4,40,1), XRA_MASK,  PPCGEKKO,       { FRT, FRB } },
+{ "ps_res",     A(4,24,0), AFRAFRC_MASK,PPCGEKKO,       { FRT, FRB } },
+{ "ps_res.",    A(4,24,1), AFRAFRC_MASK,PPCGEKKO,       { FRT, FRB } },
+{ "ps_rsqrte",  A(4,26,0), AFRAFRC_MASK,PPCGEKKO,       { FRT, FRB } },
+{ "ps_rsqrte.", A(4,26,1), AFRAFRC_MASK,PPCGEKKO,       { FRT, FRB } },
+{ "ps_sub",     A(4,20,0),   AFRC_MASK, PPCGEKKO,       { FRT, FRB } },
+{ "ps_sub.",    A(4,20,1),   AFRC_MASK, PPCGEKKO,       { FRT, FRB } },
+{ "ps_madd",    A(4,29,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_madd.",   A(4,29,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_madds0",  A(4,14,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_madds0.", A(4,14,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_madds1",  A(4,15,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_madds1.", A(4,15,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_msub",    A(4,28,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_msub.",   A(4,28,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_mul",     A(4,25,0),   AFRB_MASK, PPCGEKKO,       { FRT, FRA, FRC } },
+{ "ps_mul.",    A(4,25,1),   AFRB_MASK, PPCGEKKO,       { FRT, FRA, FRC } },
+{ "ps_muls0",   A(4,12,0),   AFRB_MASK, PPCGEKKO,       { FRT, FRA, FRC } },
+{ "ps_muls0.",  A(4,12,1),   AFRB_MASK, PPCGEKKO,       { FRT, FRA, FRC } },
+{ "ps_muls1",   A(4,13,0),   AFRB_MASK, PPCGEKKO,       { FRT, FRA, FRC } },
+{ "ps_muls1.",  A(4,13,1),   AFRB_MASK, PPCGEKKO,       { FRT, FRA, FRC } },
+{ "ps_nmadd",   A(4,31,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_nmadd.",  A(4,31,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_nmsub",   A(4,30,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_nmsub.",  A(4,30,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_sel",     A(4,23,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_sel.",    A(4,23,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_sum0",    A(4,10,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_sum0.",   A(4,10,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_sum1",    A(4,11,0),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },
+{ "ps_sum1.",   A(4,11,1),   A_MASK,    PPCGEKKO,       { FRT,FRA,FRC,FRB } },

 { "mulli",   OP(7),	OP_MASK,	PPCCOM,		{ RT, RA, SI } },
 { "muli",    OP(7),	OP_MASK,	PWRCOM,		{ RT, RA, SI } },

Re: [Gc-linux-devel] Howto, please

[<a.o...@bl...>]

On Fri, Apr 30, 2004 at 09:03:29AM -0700, Bill wrote:
> Target:::GBA ;)
>
> ~Bill

I see. In which case you might want to coordinate any effort
in that regard with the guys over at:
http://wwwhsse.fh-hagenberg.at/Studierende/hse02006/uclgba/

	Arthur

Re: [Gc-linux-devel] Howto, please

[Bill <Bi...@ve...>]

Ok, I'll check all that stuff out, thanks.

Target:::GBA ;)

~Bill

Arthur Othieno wrote:

>On Thu, Apr 29, 2004 at 06:18:00PM -0700, Billybob wrote:
>  
>
>>This isn't related to the development of Linux for the GameCube, but it 
>>is related to the development of Linux for another Nintendo system ;)
>>    
>>
>
>Hmm, care to share the big secret? ;)
>
>  
>
>>To the point: I'm relatively new to doing any kind of kernel hacking, 
>>linux porting, etc... I know how to use Linux, and I can program most 
>>languages you can throw at me (i.e. C/C++), though.
>>So can anyone give me some hints or directions on how to begin porting 
>>Linux to an unsupported system? Since the target system is a nintendo 
>>system I figured asking for help here would be the best place.
>>
>>Any help is greatly appreciated.
>>
>>Thank you for your time.
>>    
>>
>
>Documentation for your platform helps, really. The more you have at your
>disposal, the better.
>
>The next most important step would be getting a working toolchain for your
>target platform. For this, I recommend just grabbing the uClibc toolchain
>builder from: http://uclibc.org/cgi-bin/cvsweb/toolchain/ and letting it
>do it's magic.
>
>Enough of the talk, more of the references:
>
>  http://www.tldp.org/LDP/cpg/html/index.html
>  http://www.realtimelogic.com/staff/leif/linux/linux_860_report.pdf.gz
>  http://penguinppc.org/embedded/howto/PowerPC-Embedded-HOWTO.html
>  http://www.denx.de/twiki/bin/view/DULG/Manual
>  http://www.opersys.com/dox/opersys-quickref-1.0.5.pdf
>
>	Arthur
>
>
>-------------------------------------------------------
>This SF.Net email is sponsored by: Oracle 10g
>Get certified on the hottest thing ever to hit the market... Oracle 10g. 
>Take an Oracle 10g class now, and we'll give you the exam FREE.
>http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
>_______________________________________________
>Gc-linux-devel mailing list
>Gc-...@li...
>https://lists.sourceforge.net/lists/listinfo/gc-linux-devel
>
>
>
>  
>

Re: [Gc-linux-devel] Howto, please

[<a.o...@bl...>]

On Thu, Apr 29, 2004 at 06:18:00PM -0700, Billybob wrote:
> This isn't related to the development of Linux for the GameCube, but it 
> is related to the development of Linux for another Nintendo system ;)

Hmm, care to share the big secret? ;)

> To the point: I'm relatively new to doing any kind of kernel hacking, 
> linux porting, etc... I know how to use Linux, and I can program most 
> languages you can throw at me (i.e. C/C++), though.
> So can anyone give me some hints or directions on how to begin porting 
> Linux to an unsupported system? Since the target system is a nintendo 
> system I figured asking for help here would be the best place.
> 
> Any help is greatly appreciated.
> 
> Thank you for your time.

Documentation for your platform helps, really. The more you have at your
disposal, the better.

The next most important step would be getting a working toolchain for your
target platform. For this, I recommend just grabbing the uClibc toolchain
builder from: http://uclibc.org/cgi-bin/cvsweb/toolchain/ and letting it
do it's magic.

Enough of the talk, more of the references:

  http://www.tldp.org/LDP/cpg/html/index.html
  http://www.realtimelogic.com/staff/leif/linux/linux_860_report.pdf.gz
  http://penguinppc.org/embedded/howto/PowerPC-Embedded-HOWTO.html
  http://www.denx.de/twiki/bin/view/DULG/Manual
  http://www.opersys.com/dox/opersys-quickref-1.0.5.pdf

	Arthur