Date:	Mon, 8 Jan 2007 06:42:25 -0500
From:	"Dylan Taft" <d13f00l@...il.com>
To:	unlisted-recipients:; (no To-header on input)
Cc:	linux-kernel@...r.kernel.org
Subject: Re: Gaming Interface

I think this is a little bit overkill as well.  Gaming APIs can exist
outside the kernel, in fact, they should.  The problem here is not
that developers don't have access to gaming APIs available for linux,
it's that there's too many, but that's both the burden and blessing of
an open, "free" source environment.

There is one annoying thing though I recently came across.
Calibrating gamepads and joysticks in Linux, it seems there's no
universal way to do this.  There is libjsw, which some programs use,
and SDL, which I believe uses the /dev/* interfaces directly.  jscal
and jscalibrator both only apply to programs that use libjsw(I
believe)

In the end, joystick calibration code is often added directly to
applications that use joysticks, instead of being determined at a
lower level.  If anything, perhaps there should be a way to set null
zones, dead zones, and so on through the input interfaces?  I recently
had to edit gens' source code, for example.  My axis on my gamepad
outputs values from -32767 to +32767.  Values +-3000 are basically
garbage.  The controller is _WAY_ too sensitive.  Gens only throws out
values +-500, so there's a problem.  The gamepad was being so
sensitive that I could not properly define gamepad buttons for gens,
because every time I hit a button the analog sticks would vibrate and
fly to values +-3000 or so, and there is no universally way to
calibrate joysticks that I'm aware of.

Maybe something like _THIS_ should be added to the kernel?  Or is
there already, and I'm just being ignorant?

On 1/8/07, Jay Vaughan <jv@...ess-music.de> wrote:
> At 13:13 +0100 8/1/07, Dirk wrote:
> >Trent Waddington wrote:
> >  > Call me crazy, but game manufacturers want directx right?  You aint
> >  > running that in the kernel.
> >They want something like DirectX that changes it's API less frequent
> >than DirectX and that compiles as a module because you don't want to run
> >it in the kernel.
> >
>
> Whats wrong with just using SDL/OpenGL?  Thousands of games are made
> with SDL/OpenGL, and there are realms of Linux usage where this works
> just fine, especially for games (GP2X, etc).  In case you didn't
> notice, plenty of pro Game Developers use SDL/OpenGL just fine for
> their needs, and get the job done without grumbling and groaning
> about needing to have their hands held through the process.
>
> I fail to see the reason this requirement has to be a 'kernel'
> interface, other than pure sheer laziness and inability to grok on
> the part of the so-called professional Game Developers.  Gaming is
> only *one* kind of application for the Linux kernel - shall we burden
> the kernel with everything everyone wants just because people fail to
> understand the proper way to assemble a Linux-based kit for their
> specific application needs?  (Hint: work with the distro builders.)
>
> Just my .2c, but anyone suggesting that API's be crowbar'ed into the
> kernel "just to make it easier to get what you want from a single
> source" is probably not as familiar with the underlying technology,
> nor the reasons for its structured organization, as they ought to be
> before making such suggestions ..
>
> --
>
> ;
>
> Jay Vaughan
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@...r.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Powered by blists - more mailing lists