From: John W. <lin...@ho...> - 2002-01-28 22:36:45
|
I take it that it would be too much trouble to look at the maple bus in the same light as one would for USB... >From: Ernie <st...@ma...> >To: lin...@li... >Subject: Re: [linuxdc-dev]Microphone for Dreamcast / Dreameye camera >Date: Mon, 28 Jan 2002 17:14:33 -0500 > >I don't know about everyone else, but I can't wait to check my email >from my DC with a fishing rod ... oh, and maybe we could use the >lightgun to delete emails? Man, that'd rock ... ;) > >-e > >On Monday, January 28, 2002, at 03:15 PM, M. R. Brown wrote: > >>* Paul Mundt <pm...@mv...> on Mon, Jan 28, 2002: >> >>>Doesn't belong in maple much at all.. This looks a lot like something >>>that's >>>begging to be implemented through v4l (Video4Linux). See >>>drivers/media/video.. >>> >> >>Ah yeah. >> >>>Too bad we can't automagically taint the kernel if a bastard maple >>>device is >>>plugged in.. would serve the user right for hooking one of those >>>abominations >>>up anyways.. >>> >> >>C'mon!! Don't you want to check your e-mail from your DC with a goddamn >>fishing rod?!? Don't you want to dance-dance your way through your >>list of >>running processes??? Shake, shake, shake, senora, your way across the >>Web? >> >>Let's use our ball^H^H^H^Hheads people! :P. >> >>M. R. >> > > >_______________________________________________ >Linuxdc-dev mailing list >Lin...@li... >https://lists.sourceforge.net/lists/listinfo/linuxdc-dev -- John Wiggins Loxly Norwych (DAoC) Xortan Brax (EQ) Gunther Dragon (UDIC) lin...@ho... jwi...@sp... wig...@ya... _________________________________________________________________ Send and receive Hotmail on your mobile device: http://mobile.msn.com |
From: M. R. B. <mr...@0x...> - 2002-01-28 22:52:16
|
* John Wiggins <lin...@ho...> on Mon, Jan 28, 2002: > I take it that it would be too much trouble to look at the maple bus in t= he=20 > same light as one would for USB... >=20 We do ... although you have to question the intelligence of adding all those Maple drivers in the kernel tree itself. True that USB does, but is that necessarily the right thing to do? USB does include mass storage, audio, networking, etc. but it's a heck of a lot more organized (and standardized) than Maple ever could be. Besides, those USB drivers hook into other Linux subsystems. I can't imagine what subsystem the maracas would hook into. But if "controller" type devices map out to controller buttons, then it's not that big of a deal. Does the fishing rod return analog input like the controller, or some weird protocol that only fishing rods know how to do? If it is a controller, then it can live with the rest of the Maple controller code and be treated as such - apps that use it wouldn't need to know the difference. Is there anyone on the list who has a bunch of 2nd class DC peripherals? I may want to send you a test program to grab useful info from them. 2nd class also includes 3rd-party controllers, and of course, the steering wheel :P. M. R. |
From: Adrian M. <ad...@mc...> - 2002-01-28 23:10:31
|
On Monday 28 Jan 2002 10:48 pm, M. R. Brown wrote: > * John Wiggins <lin...@ho...> on Mon, Jan 28, 2002: > > I take it that it would be too much trouble to look at the maple bus in > > the same light as one would for USB... > > We do ... although you have to question the intelligence of adding all > those Maple drivers in the kernel tree itself. True that USB does, but is > that necessarily the right thing to do? USB does include mass storage, > audio, networking, etc. but it's a heck of a lot more organized (and > standardized) than Maple ever could be. Besides, those USB drivers hook > into other Linux subsystems. I can't imagine what subsystem the maracas > would hook into. > Well, I doubt we'll ever really have maracas drivers, but why should these be treated any differently (in terms of running as kernel code) than, say, a mouse, which is an utterly useless article when it comes to a Dreamcast? > > M. R. |
From: M. R. B. <mr...@0x...> - 2002-01-28 23:34:45
|
* Adrian McMenamin <ad...@mc...> on Mon, Jan 28, 2002: > On Monday 28 Jan 2002 10:48 pm, M. R. Brown wrote: > > * John Wiggins <lin...@ho...> on Mon, Jan 28, 2002: > > > I take it that it would be too much trouble to look at the maple bus = in > > > the same light as one would for USB... > > > > We do ... although you have to question the intelligence of adding all > > those Maple drivers in the kernel tree itself. True that USB does, but= is > > that necessarily the right thing to do? USB does include mass storage, > > audio, networking, etc. but it's a heck of a lot more organized (and > > standardized) than Maple ever could be. Besides, those USB drivers hook > > into other Linux subsystems. I can't imagine what subsystem the maracas > > would hook into. > > >=20 > Well, I doubt we'll ever really have maracas drivers, but why should thes= e be=20 > treated any differently (in terms of running as kernel code) than, say, a= =20 > mouse, which is an utterly useless article when it comes to a Dreamcast? >=20 Because there is provision for mice in more than one spot in the kernel. The mouse hooks into the input subsystem via mousedev, so it's presence is more than justified in the kernel itself. There is no such maracasdev or any other input mechanism that one could subscribe to that would justify a hacked up kernel interface to the maracas. I wasn't saying that we don't include Maple device support because it is or isn't useful, but the argument is whether or not they are useful as kernel drivers or userspace drivers. IMO, if the device deviates from the standard Maple input list and introduces a proprietary protocol that can't be utilized sanely anywhere else in the kernel besides Maple, then support for it belongs in userspace. I don't know enough yet about the maracas, dance pad, fishing rod, etc. to make that determination, but my best guess is that they don't look like controllers to Maple. I think in those extreme cases that a more generic Maple driver and userspace access library would work, similar to how evdev works as a catch-all in the input subsystem. I do not think that we should spend time making those devices "emulate" real Maple input devices for the sake of coolness. The lightgun is as hacked as I am willing to go, only because it *must* be a hack, there is no other sane way to support it. We've already talked about borrowing from or integrating USB and Maple, and that is more than enough challenge by itself. M. R. |
From: Ernie <st...@ma...> - 2002-01-29 00:13:44
|
On Monday, January 28, 2002, at 05:48 PM, M. R. Brown wrote: > Is there anyone on the list who has a bunch of 2nd class DC > peripherals? I > may want to send you a test program to grab useful info from them. 2nd > class also includes 3rd-party controllers, and of course, the steering > wheel :P. Ah yes, the steering wheel. For moving through your emails ... Maybe if one has a gas pedal, we can hook it into kernel networking, and use it as a kind of bandwidth control ... Ok ok, i'll stop now, i promise :) -e |