Let's disable the splash if the user presses ESC or F1-F12 on a VT.
The F1-F12 check is to disable the splash on VT switches.
Signed-off-by: Max Staudt
---
drivers/tty/vt/keyboard.c | 24
1 file changed, 24 insertions(+)
diff --git
Let's disable the splash if the user presses ESC or F1-F12 on a VT.
The F1-F12 check is to disable the splash on VT switches.
Signed-off-by: Max Staudt
---
drivers/tty/vt/keyboard.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/tty/vt/keyboard.c
Let's disable the splash if the user presses ESC or F1-F12 on a VT.
The F1-F12 check is to disable the splash on VT switches.
Signed-off-by: Max Staudt
---
drivers/tty/vt/keyboard.c | 24
1 file changed, 24 insertions(+)
diff --git
Let's disable the splash if the user presses ESC or F1-F12 on a VT.
The F1-F12 check is to disable the splash on VT switches.
Signed-off-by: Max Staudt
---
drivers/tty/vt/keyboard.c | 24
1 file changed, 24 insertions(+)
diff --git a/drivers/tty/vt/keyboard.c
Let's disable the splash if the user presses ESC or F1-F12 on a VT.
The F1-F12 check is to disable the splash on VT switches.
Signed-off-by: Max Staudt
Reviewed-by: Oliver Neukum
---
drivers/tty/vt/keyboard.c | 11 +++
1 file changed, 11
Let's disable the splash if the user presses ESC or F1-F12 on a VT.
The F1-F12 check is to disable the splash on VT switches.
Signed-off-by: Max Staudt
Reviewed-by: Oliver Neukum
---
drivers/tty/vt/keyboard.c | 11 +++
1 file changed, 11 insertions(+)
diff --git
> Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a
> hook for my qoder stuff, and a loadable module for the meat of the
> driver.
Okay.
> Then I'll port up to the input API.
Just send me the code and I will place it into CVS.
>I have a Sparc here; does it have
Thanks, I'm loking through your driver now. Does the input api already/currently
support ps2 keyboards?
-M
On Sat, Jun 02, 2001 at 08:40:04PM -0700, James Simmons wrote:
>
> Hi!
>
>Your best bet for a kernel driver is to use the linux input api like
> the usb keyboard do. The drivers are
> Thanks, I'm loking through your driver now. Does the input api
> already/currently support ps2 keyboards?
With the current tree no. The work around is to make input api keyboards
behave as PS/2 keyboards. In 2.5.X ps2 keyboards will be input api based.
As you can see we already have PS/2
Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a hook for
my qoder stuff, and a loadable module for the meat of the driver. Then I'll port up to
the input API. The Qoder is strictly ps/2 keyboard, as far as its interface goes, so I
cannot use the input API for now.
Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a hook for
my qoder stuff, and a loadable module for the meat of the driver. Then I'll port up to
the input API. The Qoder is strictly ps/2 keyboard, as far as its interface goes, so I
cannot use the input API for now.
Thanks, I'm loking through your driver now. Does the input api
already/currently support ps2 keyboards?
With the current tree no. The work around is to make input api keyboards
behave as PS/2 keyboards. In 2.5.X ps2 keyboards will be input api based.
As you can see we already have PS/2
Thanks, I'm loking through your driver now. Does the input api already/currently
support ps2 keyboards?
-M
On Sat, Jun 02, 2001 at 08:40:04PM -0700, James Simmons wrote:
Hi!
Your best bet for a kernel driver is to use the linux input api like
the usb keyboard do. The drivers are
Input API looks nice. For now, I'll write a patch against pc_keyb.c to add a
hook for my qoder stuff, and a loadable module for the meat of the
driver.
Okay.
Then I'll port up to the input API.
Just send me the code and I will place it into CVS.
I have a Sparc here; does it have
Hi!
Your best bet for a kernel driver is to use the linux input api like
the usb keyboard do. The drivers are pretty simple to write and since all
the keyboard drivers will be port over to this api it will save a lot of
work done the road. If you need help let me know. I will be glad to
I'm beginning the process of writing a driver for the "Qoder"
keyboard-fob barcode scanner made by InterMec. It communicates with the
host computer using the PS/2 port by way of a "dock" that sits in
between the keyboard and the computer.
The dock does handshaking with the host computer, which
I'm beginning the process of writing a driver for the Qoder
keyboard-fob barcode scanner made by InterMec. It communicates with the
host computer using the PS/2 port by way of a dock that sits in
between the keyboard and the computer.
The dock does handshaking with the host computer, which means
Hi!
Your best bet for a kernel driver is to use the linux input api like
the usb keyboard do. The drivers are pretty simple to write and since all
the keyboard drivers will be port over to this api it will save a lot of
work done the road. If you need help let me know. I will be glad to
18 matches
Mail list logo