Menu
▾
▴
gc-linux-devel
|
From: Michael S. <st...@in...> - 2004-01-22 12:23:23
|
Hi! It is really amazing how many people are interested in contributing! ** SI/gamepad driver ** "Free the Cube" has announced yesterday that he was working on a SI/gamepad driver - great. Don't we need an independent driver for the SI bus first, that exports an API for the bus, and gamepad drivers later, that plug into the SI API? Anyway, the joystick->mouse converter sounds very interesting, but a kernel driver would be more useful, I think. Adding code for joystick->keyboard conversion should not be hard then. ** EXI driver ** Arthur Othieno (hubb) told me yesterday that he was working on a driver for the EXI bus. He already has an API design as well as a skeleton driver that builds and loads into a x86 kernel. ** writing drivers/docs ** You might ask whether it already makes sense to start writing drivers, if the kernel doesn't boot yet. Yes, it makes sense. You can't try it out yet, but if you're motivated, then write some code! In the Xbox Linux project, we had an almost-working bootloader as well as a simple filesystem drivers before we even had a modchip. So if you want to start working on some other driver (see http://gc-linux.org/docs/roadmap.html ), just announce it on the mailing list and go ahead. Yes, we have very little documentation on the website. If you have some documentation from elsewhere on the web, tell me, and we'll add it. Also tell me if you want to write documentation (<- this is _very_ useful!). ***** ->"Free the Cube": The EXI doc looks interesting, it doesn't seem to be the same as Costis' article on the website. Perhaps it makes sense to merge information contained in yours into Costis' article (in English)? Michael |
|
From: Free T. C. <Fre...@fr...> - 2004-01-22 12:44:28
|
Michael Steil wrote: > Hi! > > It is really amazing how many people are interested in contributing! > > ** SI/gamepad driver ** > > "Free the Cube" has announced yesterday that he was working on a > SI/gamepad driver - great. Don't we need an independent driver for the > SI bus first, that exports an API for the bus, and gamepad drivers > later, that plug into the SI API? The GCPAD driver from GCLIB uses direct memory access to the mapped area where are pad status, it should be possible to do like this (temporarily)... Then we can modify this first implementation to use the SI layer ! (i need confirmation) > Anyway, the joystick->mouse converter sounds very interesting, but a > kernel driver would be more useful, I think. Adding code for > joystick->keyboard conversion should not be hard then. OK, i will try to put the "joystick->mouse converter" into kernel-space :) ! For the joystick->keyboard conversion, i don't know how to make it possible, someone has got an idea ??? > > ** EXI driver ** > > Arthur Othieno (hubb) told me yesterday that he was working on a driver > for the EXI bus. He already has an API design as well as a skeleton > driver that builds and loads into a x86 kernel. > > ** writing drivers/docs ** > > You might ask whether it already makes sense to start writing drivers, > if the kernel doesn't boot yet. Yes, it makes sense. You can't try it > out yet, but if you're motivated, then write some code! In the Xbox > Linux project, we had an almost-working bootloader as well as a simple > filesystem drivers before we even had a modchip. > So if you want to start working on some other driver (see > http://gc-linux.org/docs/roadmap.html ), just announce it on the mailing > list and go ahead. Yes, we have very little documentation on the > website. If you have some documentation from elsewhere on the web, tell > me, and we'll add it. Also tell me if you want to write documentation > (<- this is _very_ useful!). > > ***** > > ->"Free the Cube": The EXI doc looks interesting, it doesn't seem to be > the same as Costis' article on the website. Perhaps it makes sense to > merge information contained in yours into Costis' article (in English)? This is not mine, this is a french translation :) from the article taken from GCDemos, I have to write the source on the headline, sorry. > > Michael > > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > Gc-linux-devel mailing list > Gc-...@li... > https://lists.sourceforge.net/lists/listinfo/gc-linux-devel > > |
|
From: Michael S. <st...@in...> - 2004-01-22 12:54:41
|
On 22.01.2004, at 13:44, Free The Cube wrote: > The GCPAD driver from GCLIB uses direct memory access to the mapped > area where are pad status, it should be possible to do like this > (temporarily)... Then we can modify this first implementation to use > the SI layer ! (i need confirmation) "temporarily"? :-) http://www.over-yonder.net/~fullermd/rants/bsd4linux/bsd4linux8.php says that it's typical of Linux hackers to do temporary solutions that will never be replaced by good solutions. :-) But in this case I tend to agree that a temporary, working solution is better, because we will certainly lack good debug methods in the first time. By the way, porting the ethernet adapter code of GCLIB to Linux would also be important. Any voluntaries? >> ->"Free the Cube": The EXI doc looks interesting, it doesn't seem to >> be the same as Costis' article on the website. Perhaps it makes sense >> to merge information contained in yours into Costis' article (in >> English)? > This is not mine, this is a french translation :) from the article > taken from GCDemos, I have to write the source on the headline, sorry. http://gcdemos.com/tuts.htm ? Hmmm, I can't click on anything. If anyone can provide me with documentation, pelase email me and I'll add it to the website. Michael |
|
From: Michael S. <st...@in...> - 2004-01-22 12:56:59
|
On 22.01.2004, at 13:54, Michael Steil wrote: > http://gcdemos.com/tuts.htm ? Hmmm, I can't click on anything. If > anyone can provide me with documentation, pelase email me and I'll add > it to the website. Oh, I just didn't understand the website. Bad web design. :-( http://gcdemos.com/lowlevel.htm - does anyone want to help HTMLizing this? I want to have all docs on gc-linux.org (including a link to the original source of course). Michael |
|
From: Alexandre B. <al...@bo...> - 2004-01-22 14:38:37
|
On Thu, 22 Jan 2004 13:56:48 +0100 Michael Steil <st...@in...> wrote: > On 22.01.2004, at 13:54, Michael Steil wrote: > Oh, I just didn't understand the website. Bad web design. :-( > http://gcdemos.com/lowlevel.htm - does anyone want to help HTMLizing > this? I want to have all docs on gc-linux.org (including a link to the > Hello, All the docs that are on gcdemos.com are also included in dolwin 0.08 source package, and the files present in this package seemed more acurate to me than those on gcdemos.com. -- Alexandre Boeglin e. mail : al...@bo... | Jabber : bo...@ja... ICQ UIN : 38852646 | Website : http://www.boeglin.org/ GPG Key fingerprint : 6B02 86CA A79E FA83 2FF0 3B83 14DE 4187 39C1 2786 |
|
From: Michael S. <st...@in...> - 2004-01-22 17:25:09
|
On 22.01.2004, at 15:42, Alexandre Boeglin wrote: > All the docs that are on gcdemos.com are also included in dolwin 0.08 > source package, and the files present in this package seemed more > acurate to me than those on gcdemos.com. Someone just sent me a beta version of self-written a 500 KB HTML document containing so much GameCube information that the dolwin docs are probably obsolete anyway. Michael |
|
From: <a.o...@bl...> - 2004-01-22 13:53:59
|
On Thu, Jan 22, 2004 at 01:54:29PM +0100, Michael Steil wrote: > > http://gcdemos.com/tuts.htm ? Hmmm, I can't click on anything. If > anyone can provide me with documentation, pelase email me and I'll add > it to the website. http://gcdemos.com/lowlevel.htm is probably what you want. Arthur -- Linux is a true multitasking system. Are you? |
|
From: <a.o...@bl...> - 2004-01-22 14:26:43
|
On Thu, Jan 22, 2004 at 01:44:20PM +0100, Free The Cube wrote: > Michael Steil wrote: > >** SI/gamepad driver > >"Free the Cube" has announced yesterday that he was working on a > >SI/gamepad driver - great. Don't we need an independent driver for the > >SI bus first, that exports an API for the bus, and gamepad drivers > >later, that plug into the SI API? > > The GCPAD driver from GCLIB uses direct memory access to the mapped area > where are pad status, it should be possible to do like this > (temporarily)... Then we can modify this first implementation to use the > SI layer ! (i need confirmation) > IMHO, you're better off going with the bus-layer -> device-driver architecture, initially. That way, the bus driver handles things like probing for and maintaining a list of existing devices, binding device drivers to devices, handling PM and hotplug events, etc, while device drivers handle stuff like enabling the device, accessing configuration space and communicating with the drive. Don't get me wrong here - if you feel more comfortable starting with your approach, feel free to do so. We can always move over later on :) Arthur -- Linux is a true multitasking system. Are you? |
|
From: Free T. C. <Fre...@fr...> - 2004-01-23 08:49:12
|
Arthur Othieno wrote: > IMHO, you're better off going with the bus-layer -> device-driver > architecture, initially. That way, the bus driver handles things like > probing for and maintaining a list of existing devices, binding device > drivers to devices, handling PM and hotplug events, etc, while device > drivers handle stuff like enabling the device, accessing configuration > space and communicating with the drive. > > Don't get me wrong here - if you feel more comfortable starting with your > approach, feel free to do so. We can always move over later on :) > > > Arthur You're right :) !!!! But the "temporary" driver is written :), it need more tests (it's a port of the GCLIB driver so it should work correclty (i hope) :) I will work on the SI driver... Regards, Free The Cube. |
|
From: Michael S. <st...@in...> - 2004-01-23 12:37:39
|
On 23.01.2004, at 09:49, Free The Cube wrote: > You're right :) !!!! But the "temporary" driver is written :), it need > more tests (it's a port of the GCLIB driver so it should work > correclty (i hope) :) > I will work on the SI driver... Great. Jut send a kernel patch (preferably 2.6.1) to the mailing list and we'll put it in the CVS for everyone to see it. ...and you need an SF CVS account yourself then. Michael |
|
From: Free T. C. <Fre...@fr...> - 2004-01-23 13:11:46
|
Michael Steil wrote: > On 23.01.2004, at 09:49, Free The Cube wrote: > >> You're right :) !!!! But the "temporary" driver is written :), it need >> more tests (it's a port of the GCLIB driver so it should work >> correclty (i hope) :) >> I will work on the SI driver... > > > Great. Jut send a kernel patch (preferably 2.6.1) to the mailing list > and we'll put it in the CVS for everyone to see it. > ...and you need an SF CVS account yourself then. > I can't send you a patch against 2.6.1, I'm at my work office ;) (no kernel sources, and can't spend time to download, test, ...) but I can send you the source file tested with linux 2.4.XX :) ! In my version, there are 2 parts : - the GCPAD driver - some functions (not finished) to test it with my 86 box... I removed the last one in the attached file. We still must adjust some values such as 'gcpad[i].dev.absmin' 'gcpad[i].dev.absmax' !!! If i remember correctly, the trigger values go from -32767 to 32768, it is not really what we want (0 to 32768). This driver (if it works :) ) is not really good : - the active loop wastes CPU time, even if i didn't feel this into my x86 box. - it doesn't use the SI layer - and the worst : it is not tested :) ! let us not be so pessimistic : it uses the standart input layer :D... Free The Cube. |
|
From: <xa...@da...> - 2004-01-22 17:03:55
|
.------[ Free The Cube wrote (Thu, Jan 22, 2004 at 01:44:20PM +0100) ]------ | | >Anyway, the joystick->mouse converter sounds very interesting, but a | >kernel driver would be more useful, I think. Adding code for | >joystick->keyboard conversion should not be hard then. | OK, i will try to put the "joystick->mouse converter" into kernel-space :) ! | For the joystick->keyboard conversion, i don't know how to make it | possible, someone has got an idea ??? This may be something no one wants to deal with, but the joystick has enough buttons to do a simple two-handed chording keyboard. You can press up to 5 buttons at a time so you'd get 36 characters.Or you could use the directions as a shift type thing and get 4x (or even 8x) 15. Anyway, it's just an idea and no one really likes learning how to type on those things anyway, but for lack of another input device it would work... -s |
|
From: Richard E. <ric...@br...> - 2004-01-22 17:11:14
|
I really think that the SI interface should be a general driver, and build the pads etc. on top of it. Not all of you know this, but there are a few keyboards for the gamecube currently available. I have one made by Datel, that was designed to be used with PSO. It's actually a normal PS/2 keyboard with a PS/2 to GC adapter. There's also an adapter on Lik-Sang. I would really like to get my keyboard working with GC-Linux.. Richard Eng > .------[ Free The Cube wrote (Thu, Jan 22, 2004 at 01:44:20PM +0100) ]------ > | > | >Anyway, the joystick->mouse converter sounds very interesting, but a > | >kernel driver would be more useful, I think. Adding code for > | >joystick->keyboard conversion should not be hard then. > | OK, i will try to put the "joystick->mouse converter" into kernel-space :) ! > | For the joystick->keyboard conversion, i don't know how to make it > | possible, someone has got an idea ??? > > This may be something no one wants to deal with, but the joystick has enough buttons to do a simple two-handed chording keyboard. You can press up to 5 buttons at a time so you'd get 36 characters.Or you could use the directions as a shift type thing and get 4x (or even 8x) 15. > > Anyway, it's just an idea and no one really likes learning how to type on those things anyway, but for lack of another input device it would work... |
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X