Joe Peterson wrote:
Dave Neuer wrote:
On 8/15/05, Joe Peterson <[EMAIL PROTECTED]> wrote:
So, overall, I agree that we should not invent hacks to make up for
another software package's problems...
but also wrote:
If the kernel could handle that aspect, it would make
Joe Peterson wrote:
Dave Neuer wrote:
On 8/15/05, Joe Peterson [EMAIL PROTECTED] wrote:
So, overall, I agree that we should not invent hacks to make up for
another software package's problems...
but also wrote:
If the kernel could handle that aspect, it would make all
On 8/15/05, Jon Smirl <[EMAIL PROTECTED]> wrote:
> The xorg evdev input driver is here:
> http://cvs.freedesktop.org/xorg/driver/xf86-input-evdev/
I see it is not there yet. Here is the old one:
http://cvs.freedesktop.org/xorg/xc/programs/Xserver/hw/xfree86/input/evdev/
>
> --
> Jon Smirl
>
On 8/15/05, Joe Peterson <[EMAIL PROTECTED]> wrote:
> So, overall, I agree that we should not invent hacks to make up for
> another software package's problems, but perhaps input devices,
> especially ones that sometimes are not there at boot or not there all
> the time, should be treated in a way
Dave Neuer wrote:
> On 8/15/05, Joe Peterson <[EMAIL PROTECTED]> wrote:
>
>>So, overall, I agree that we should not invent hacks to make up for
>>another software package's problems...
>
>
> but also wrote:
>
>
>>If the kernel could handle that aspect, it would make all programs more
On Mon, Aug 15, 2005 at 04:06:04PM -0400, Dave Neuer wrote:
> On 8/15/05, Joe Peterson <[EMAIL PROTECTED]> wrote:
> >
> > So, overall, I agree that we should not invent hacks to make up for
> > another software package's problems...
>
> but also wrote:
>
> > If the kernel could handle that
On 8/15/05, Joe Peterson <[EMAIL PROTECTED]> wrote:
>
> So, overall, I agree that we should not invent hacks to make up for
> another software package's problems...
but also wrote:
> If the kernel could handle that aspect, it would make all programs more
> stable.
which seems a little
Vojtech Pavlik wrote:
I am using evtouch, but I had read that X itself has an issue with
devices that are not "always there" and that X does not [yet] seem to be
designed to handle hotplugging well (for example, device names need to
be hard-coded in xorg.conf, so a changing device
On Mon, Aug 15, 2005 at 12:00:37PM -0600, Joe Peterson wrote:
> I am using evtouch, but I had read that X itself has an issue with
> devices that are not "always there" and that X does not [yet] seem to be
> designed to handle hotplugging well (for example, device names need to
> be hard-coded in
Vojtech Pavlik wrote:
> On Mon, Aug 15, 2005 at 11:27:56AM -0600, Joe Peterson wrote:
>
>
>>I, and a growing number of others, have been having trouble with using
>>touch screen devices in Linux, particularly the motorized ones that fit
>>into car dashboards. The problem is that these devices,
On Mon, Aug 15, 2005 at 11:27:56AM -0600, Joe Peterson wrote:
> I, and a growing number of others, have been having trouble with using
> touch screen devices in Linux, particularly the motorized ones that fit
> into car dashboards. The problem is that these devices, which have a
> USB
I, and a growing number of others, have been having trouble with using
touch screen devices in Linux, particularly the motorized ones that fit
into car dashboards. The problem is that these devices, which have a
USB touchscreen (often the eGalax brand), turn off when the screen is
retracted,
I, and a growing number of others, have been having trouble with using
touch screen devices in Linux, particularly the motorized ones that fit
into car dashboards. The problem is that these devices, which have a
USB touchscreen (often the eGalax brand), turn off when the screen is
retracted,
On Mon, Aug 15, 2005 at 11:27:56AM -0600, Joe Peterson wrote:
I, and a growing number of others, have been having trouble with using
touch screen devices in Linux, particularly the motorized ones that fit
into car dashboards. The problem is that these devices, which have a
USB touchscreen
Vojtech Pavlik wrote:
On Mon, Aug 15, 2005 at 11:27:56AM -0600, Joe Peterson wrote:
I, and a growing number of others, have been having trouble with using
touch screen devices in Linux, particularly the motorized ones that fit
into car dashboards. The problem is that these devices, which
On Mon, Aug 15, 2005 at 12:00:37PM -0600, Joe Peterson wrote:
I am using evtouch, but I had read that X itself has an issue with
devices that are not always there and that X does not [yet] seem to be
designed to handle hotplugging well (for example, device names need to
be hard-coded in
Vojtech Pavlik wrote:
I am using evtouch, but I had read that X itself has an issue with
devices that are not always there and that X does not [yet] seem to be
designed to handle hotplugging well (for example, device names need to
be hard-coded in xorg.conf, so a changing device name on plugging
On 8/15/05, Joe Peterson [EMAIL PROTECTED] wrote:
So, overall, I agree that we should not invent hacks to make up for
another software package's problems...
but also wrote:
If the kernel could handle that aspect, it would make all programs more
stable.
which seems a little contradictory.
On Mon, Aug 15, 2005 at 04:06:04PM -0400, Dave Neuer wrote:
On 8/15/05, Joe Peterson [EMAIL PROTECTED] wrote:
So, overall, I agree that we should not invent hacks to make up for
another software package's problems...
but also wrote:
If the kernel could handle that aspect, it would
Dave Neuer wrote:
On 8/15/05, Joe Peterson [EMAIL PROTECTED] wrote:
So, overall, I agree that we should not invent hacks to make up for
another software package's problems...
but also wrote:
If the kernel could handle that aspect, it would make all programs more
stable.
which
On 8/15/05, Joe Peterson [EMAIL PROTECTED] wrote:
So, overall, I agree that we should not invent hacks to make up for
another software package's problems, but perhaps input devices,
especially ones that sometimes are not there at boot or not there all
the time, should be treated in a way that
On 8/15/05, Jon Smirl [EMAIL PROTECTED] wrote:
The xorg evdev input driver is here:
http://cvs.freedesktop.org/xorg/driver/xf86-input-evdev/
I see it is not there yet. Here is the old one:
http://cvs.freedesktop.org/xorg/xc/programs/Xserver/hw/xfree86/input/evdev/
--
Jon Smirl
[EMAIL
22 matches
Mail list logo
