Hi!
> > > Can't it make mouse jump forward and back when user suddenly stops?
> >
> > In theory - yes. It doesn't seem to be a problem in practice, though.
> > It'll happen when a user slows down the mouse pointer motion faster than
> > exponentially (base 2). I haven't been able to stop that
Hi!
Can't it make mouse jump forward and back when user suddenly stops?
In theory - yes. It doesn't seem to be a problem in practice, though.
It'll happen when a user slows down the mouse pointer motion faster than
exponentially (base 2). I haven't been able to stop that fast.
Put
On Fri, Jun 08, 2001 at 03:19:46PM -0500, Mike Coleman wrote:
> Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> > > Can't it make mouse jump forward and back when user suddenly stops?
> >
> > In theory - yes. It doesn't seem to be a problem in practice, though.
> > It'll happen when a user slows
On Fri, Jun 08, 2001 at 03:19:46PM -0500, Mike Coleman wrote:
Vojtech Pavlik [EMAIL PROTECTED] writes:
Can't it make mouse jump forward and back when user suddenly stops?
In theory - yes. It doesn't seem to be a problem in practice, though.
It'll happen when a user slows down the
Vojtech Pavlik <[EMAIL PROTECTED]> writes:
> > Can't it make mouse jump forward and back when user suddenly stops?
>
> In theory - yes. It doesn't seem to be a problem in practice, though.
> It'll happen when a user slows down the mouse pointer motion faster than
> exponentially (base 2). I
sorry I'm late, could you tell me where this driver/patch is?
also, my problem with USB mice on slow machines is that it takes
up too much CPU, and you get a jumpy mouse if your box is doing a
lot of work (like a heavy nfs server, say). Would this driver do
the same to that box?
On Fri, Jun
On Fri, Jun 08, 2001 at 06:20:46PM +0200, Pavel Machek wrote:
> Hi!
>
> > > > If you still have your 3-button MouseSystems (or any other serial) mouse
> > > > somewhere in your driver, forgotten becase of the incredibly slow update
> > > > rate causing so much jumping of the pointer on the
Hi!
> > > If you still have your 3-button MouseSystems (or any other serial) mouse
> > > somewhere in your driver, forgotten becase of the incredibly slow update
> > > rate causing so much jumping of the pointer on the screen that it is
> > > unusable, you may want to pull it out and give it a
On Wed, Jun 06, 2001 at 11:21:34PM +, Pavel Machek wrote:
> > If you still have your 3-button MouseSystems (or any other serial) mouse
> > somewhere in your driver, forgotten becase of the incredibly slow update
> > rate causing so much jumping of the pointer on the screen that it is
> >
Hi!
>
> If you still have your 3-button MouseSystems (or any other serial) mouse
> somewhere in your driver, forgotten becase of the incredibly slow update
> rate causing so much jumping of the pointer on the screen that it is
> unusable, you may want to pull it out and give it a try.
>
> Or if
Hi!
If you still have your 3-button MouseSystems (or any other serial) mouse
somewhere in your driver, forgotten becase of the incredibly slow update
rate causing so much jumping of the pointer on the screen that it is
unusable, you may want to pull it out and give it a try.
Or if you're
On Wed, Jun 06, 2001 at 11:21:34PM +, Pavel Machek wrote:
If you still have your 3-button MouseSystems (or any other serial) mouse
somewhere in your driver, forgotten becase of the incredibly slow update
rate causing so much jumping of the pointer on the screen that it is
unusable,
Hi!
If you still have your 3-button MouseSystems (or any other serial) mouse
somewhere in your driver, forgotten becase of the incredibly slow update
rate causing so much jumping of the pointer on the screen that it is
unusable, you may want to pull it out and give it a try.
On Fri, Jun 08, 2001 at 06:20:46PM +0200, Pavel Machek wrote:
Hi!
If you still have your 3-button MouseSystems (or any other serial) mouse
somewhere in your driver, forgotten becase of the incredibly slow update
rate causing so much jumping of the pointer on the screen that it is
sorry I'm late, could you tell me where this driver/patch is?
also, my problem with USB mice on slow machines is that it takes
up too much CPU, and you get a jumpy mouse if your box is doing a
lot of work (like a heavy nfs server, say). Would this driver do
the same to that box?
On Fri, Jun
Vojtech Pavlik [EMAIL PROTECTED] writes:
Can't it make mouse jump forward and back when user suddenly stops?
In theory - yes. It doesn't seem to be a problem in practice, though.
It'll happen when a user slows down the mouse pointer motion faster than
exponentially (base 2). I haven't been
> > I ported it over to my tree. I will have to figure out how to incorporate
> > the input serial stuff without breaking all the input drivers we have. In
> > CVS we have alot of them. This will make life so much easier since all I
> > will have to do is change one file for changes I make to
On Wed, Jun 06, 2001 at 03:39:04PM -0700, James Simmons wrote:
> > > It would be nice if we had
> > >
> > > 1) A seperate serial directory under drivers.
> > >
> > > 2) A nice structure that input devices and the tty layer can use. It is
> > >just a waste to go threw the tty layer for
On Wed, Jun 06, 2001 at 03:39:04PM -0700, James Simmons wrote:
It would be nice if we had
1) A seperate serial directory under drivers.
2) A nice structure that input devices and the tty layer can use. It is
just a waste to go threw the tty layer for input devices. It
I ported it over to my tree. I will have to figure out how to incorporate
the input serial stuff without breaking all the input drivers we have. In
CVS we have alot of them. This will make life so much easier since all I
will have to do is change one file for changes I make to the tty
> > It would be nice if we had
> >
> > 1) A seperate serial directory under drivers.
> >
> > 2) A nice structure that input devices and the tty layer can use. It is
> >just a waste to go threw the tty layer for input devices. It would also
> >make serial driver writing easier if the
On Wed, Jun 06, 2001 at 01:20:53PM -0700, James Simmons wrote:
> Never noticed it until now. Very nice patch :-) I have to agree as well.
> It would be nice if we had
>
> 1) A seperate serial directory under drivers.
>
> 2) A nice structure that input devices and the tty layer can use. It is
>
> > > hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
> > >
> > > Bad trend.
> > >
> > > Serial needs to be treated just like parport: the basic hardware code,
> > > then on top of that, a selection of drivers, all peers: dumb serial
> > > port, serial mouse, joystick,
On Wed, Jun 06, 2001 at 07:01:58PM +0200, Vojtech Pavlik wrote:
> On Wed, Jun 06, 2001 at 12:31:28PM -0400, Jeff Garzik wrote:
> > hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
> >
> > Bad trend.
> >
> > Serial needs to be treated just like parport: the basic hardware
On Wed, Jun 06, 2001 at 09:17:56AM -0700, James Simmons wrote:
> Is it possible to move serio.c and serport.c up into drivers/char. I'm
> finding many drivers that use this and it is a mess to have to enable
> joysticks just to use other types of devices like touchscreens.
Possible it indeed
On Wed, Jun 06, 2001 at 12:31:28PM -0400, Jeff Garzik wrote:
> hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
>
> Bad trend.
>
> Serial needs to be treated just like parport: the basic hardware code,
> then on top of that, a selection of drivers, all peers: dumb serial
>
hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
Bad trend.
Serial needs to be treated just like parport: the basic hardware code,
then on top of that, a selection of drivers, all peers: dumb serial
port, serial mouse, joystick, etc.
--
Jeff Garzik | Andre the Giant
Is it possible to move serio.c and serport.c up into drivers/char. I'm
finding many drivers that use this and it is a mess to have to enable
joysticks just to use other types of devices like touchscreens.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a
> In 322 lines of code,
[hmm - gzipped, ach]
Including the code in a readable form is much better - many people
would glance at it and perhaps have remarks.
And in those cases where the code is too large to give,
a URL is preferable.
Andries
-
To unsubscribe from this list: send the line
Hi!
If you still have your 3-button MouseSystems (or any other serial) mouse
somewhere in your driver, forgotten becase of the incredibly slow update
rate causing so much jumping of the pointer on the screen that it is
unusable, you may want to pull it out and give it a try.
Or if you're still
Hi!
If you still have your 3-button MouseSystems (or any other serial) mouse
somewhere in your driver, forgotten becase of the incredibly slow update
rate causing so much jumping of the pointer on the screen that it is
unusable, you may want to pull it out and give it a try.
Or if you're still
In 322 lines of code,
[hmm - gzipped, ach]
Including the code in a readable form is much better - many people
would glance at it and perhaps have remarks.
And in those cases where the code is too large to give,
a URL is preferable.
Andries
-
To unsubscribe from this list: send the line
Is it possible to move serio.c and serport.c up into drivers/char. I'm
finding many drivers that use this and it is a mess to have to enable
joysticks just to use other types of devices like touchscreens.
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a
hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
Bad trend.
Serial needs to be treated just like parport: the basic hardware code,
then on top of that, a selection of drivers, all peers: dumb serial
port, serial mouse, joystick, etc.
--
Jeff Garzik | Andre the Giant
On Wed, Jun 06, 2001 at 12:31:28PM -0400, Jeff Garzik wrote:
hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
Bad trend.
Serial needs to be treated just like parport: the basic hardware code,
then on top of that, a selection of drivers, all peers: dumb serial
port,
On Wed, Jun 06, 2001 at 09:17:56AM -0700, James Simmons wrote:
Is it possible to move serio.c and serport.c up into drivers/char. I'm
finding many drivers that use this and it is a mess to have to enable
joysticks just to use other types of devices like touchscreens.
Possible it indeed is.
On Wed, Jun 06, 2001 at 07:01:58PM +0200, Vojtech Pavlik wrote:
On Wed, Jun 06, 2001 at 12:31:28PM -0400, Jeff Garzik wrote:
hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
Bad trend.
Serial needs to be treated just like parport: the basic hardware code,
then
hmmm. I just looked over this, and drivers/char/joystick/ser*.[ch].
Bad trend.
Serial needs to be treated just like parport: the basic hardware code,
then on top of that, a selection of drivers, all peers: dumb serial
port, serial mouse, joystick, etc.
Agreed.
On Wed, Jun 06, 2001 at 01:20:53PM -0700, James Simmons wrote:
Never noticed it until now. Very nice patch :-) I have to agree as well.
It would be nice if we had
1) A seperate serial directory under drivers.
2) A nice structure that input devices and the tty layer can use. It is
It would be nice if we had
1) A seperate serial directory under drivers.
2) A nice structure that input devices and the tty layer can use. It is
just a waste to go threw the tty layer for input devices. It would also
make serial driver writing easier if the api is designed
40 matches
Mail list logo
