http://permalink.gmane.org/gmane.linux.kernel.input hourly 1 1901-01-01T00:00+00:00 http://gmane.org/img/gmane-25t.png http://gmane.org http://permalink.gmane.org/gmane.linux.kernel.input/5613 Hi Dmitry, Sorry, just now getting the chance to look at this... On Thu, 14 Aug 2008 23:14:35 -0400 Dmitry Torokhov <dmitry.torokhov< at >gmail.com> wrote: [...] Can you please clarify this comment? This check isn't any kind of failure; it's due to a hardware quirk with earlier prototypes. Basically, during suspend/resume, the touchpad rails stay powered. We don't want to do any sort of reset of the psmouse device, otherwise we lose data (especially if someone is waking up the device via touchpad usage or button press, we certainly don't want to reset and drop the packets). However, b1 hardware required a reset for reasons that I can't recall anymore. In both cases, the reconnect worked just fine; the difference is that a psmouse_reset was issued for b2 hardware and higher. I suppose the code should have a comment saying just that, eh? :) *nod* PSMOUSE_DEFINE_ATTR is fine for show_powered, but doesn't work for set_powered because it a) doesn't change the value if psmouse->state == PSMOUSE_IGNORE Andres Salomon 2008-08-29T06:49:59 http://permalink.gmane.org/gmane.linux.kernel.input/5612 Measured on thinkpad x60 -- difference between no usb and usb active (simulated by rmmod). Pavel Pavel Machek 2008-08-28T07:59:59 http://permalink.gmane.org/gmane.linux.kernel.input/5611 Certain modules, e.g. accessibility modules for the blind, will want to generate more than just tones through the pc speaker. This patch supports clicks and chirps. Soft clicks, for instance, provide audio feedback for a blind user when keys are pressed, or when characters appear on screen. I have written modules that make these sounds directly, by hitting the pc speaker at port 61, but it would be better if all such sounds were sequestered in the pcspkr.ko module, and under the same spinlock. This patch is a necessary prelude to modules that will take advantage of these sounds. Signed-off-by: Karl Dahlke eklhad< at >comcast.net --- drivers/input/misc/pcspkr.c2008-08-14 14:41:33.000000000 -0400 +++ drivers/input/misc/pcspkr.c.new2008-08-14 14:41:33.000000000 -0400 < at >< at > -18,6 +18,7 < at >< at > #include <linux/input.h> #include <linux/platform_device.h> #include <asm/io.h> +#include <asm/delay.h> MODULE_AUTHOR("Vojtech Pavlik <vojtech< at >ucw.cz>"); MODULE_DESCRIPTION("PC Speaker beeper driver"); < at >< at > -32,41 +33,82 < at >< at > Karl Dahlke 2008-08-28T00:32:26 http://permalink.gmane.org/gmane.linux.kernel.input/5610 Am Dienstag 26 August 2008 16:28:49 schrieb Pavel Machek: Estimate or measured quantity? Regards Oliver -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Oliver Neukum 2008-08-26T16:33:11 http://permalink.gmane.org/gmane.linux.kernel.input/5609 serio_raw only binds to non-translated devices. Enable serio_raw to bind to normal (translated) keyboards which can have non-standard extensions (like POS Keyboards). With this it is possible to send commands to the device over /dev/serio_raw<n>. Signed-off-by: Niels de Vos <niels.devos< at >wincor-nixdorf.com> Cc: Dmitry Torokhov <dmitry.torokhov< at >gmail.com> --- In ReplyTo: "[RFC][PATCH] POSKeyboard driver for exclusive keyboard access" On Fri, Aug 22, 2008 at 8:02 PM, Dmitry Torokhov <dmitry.torokhov< at >gmail.com> wrote: --- diff --git a/drivers/input/serio/serio_raw.c b/drivers/input/serio/serio_raw.c index c9397c8..470770c 100644 --- a/drivers/input/serio/serio_raw.c +++ b/drivers/input/serio/serio_raw.c < at >< at > -373,6 +373,12 < at >< at > static struct serio_device_id serio_raw_serio_ids[] = { .id = SERIO_ANY, .extra = SERIO_ANY, }, + { + .type = SERIO_8042_XL, + .proto = SERIO_ANY, + .id = SERIO_ANY, + .extra = Niels de Vos 2008-08-26T15:18:53 http://permalink.gmane.org/gmane.linux.kernel.input/5608 Hi! Hmm... so numlock now costs ~3W... perhaps we should be defaulting to numlock=off, again? Pavel Pavel Machek 2008-08-26T14:28:49 http://permalink.gmane.org/gmane.linux.kernel.input/5607 It turns out that event 0x4 merely indcates that a hotkey has been pressed, not which one. A further query is required in order to determine the actual keypress. The following patch adds support for that along with the known keycodes. Signed-off-by: Matthew Garrett <mjg< at >redhat.com> --- diff --git a/drivers/misc/hp-wmi.c b/drivers/misc/hp-wmi.c index bc6ccfb..0968304 100644 --- a/drivers/misc/hp-wmi.c +++ b/drivers/misc/hp-wmi.c < at >< at > -49,6 +49,7 < at >< at > MODULE_ALIAS("wmi:5FB7F034-2C63-45e9-BE91-3D44E2C707E4"); #define HPWMI_ALS_QUERY 0x3 #define HPWMI_DOCK_QUERY 0x4 #define HPWMI_WIRELESS_QUERY 0x5 +#define HPWMI_HOTKEY_QUERY 0xc static int __init hp_wmi_bios_setup(struct platform_device *device); static int __exit hp_wmi_bios_remove(struct platform_device *device); < at >< at > -69,7 +70,7 < at >< at > struct bios_return { struct key_entry { char type;/* See KE_* below */ -u8 code; +u16 code; u16 keycode; }; < at >< at > -79,7 +80,9 < at >< at > static struct key_entry hp_wmi_keymap[] = { {KE_SW, 0x01, SW_DOCK}, {KE_KEY, 0x Matthew Garrett 2008-08-26T13:25:25 http://permalink.gmane.org/gmane.linux.kernel.input/5606 void usbhid_submit_report(struct hid_device *hid, struct hid_report *report, unsigned char dir); would look better. Matter of taste. ditto below. ^^^^^^^ you added whitespaces there Felipe Balbi 2008-08-26T09:49:15 http://permalink.gmane.org/gmane.linux.kernel.input/5605 Hi, this patch enables full runtime power management for usbhid. Currently usbhid supports autosuspend only upon open and close. Thus it is useless for devices which are always opened, such as keyboards and mice. This patch enables the use of remote wakeup for devices that support it. It suspends idle usb hid devices after a timeout if possible unless - hiddev has opened the device - error handling is under way - a key is being held down (keyboards don't signal remote wakeup upon release of a key) - an led is active on the device (leds use too much power for a suspend device to keep lit - this can be overridden with a module parameter) Furthermore a device is resumed if this is necessary for output (to leds). If output is requested while a device is suspended, the output is queued and the device woken from within a work queue. In detail the patch - reduces granularity of locking in usbhid to avoid deadlocks - introduces locking between open/close and suspend/resume - adds detection for the conditions u Oliver Neukum 2008-08-26T09:39:13 http://permalink.gmane.org/gmane.linux.kernel.input/5604 Hello Dmitry, Dmitry Torokhov wrote: Okay, thanks for pointing this out, I'll look into using serio_raw instead. If a patch is needed I'll send you one. Great. I already saw input_dev->grab but never really understood what it would do or how it could be used. Tried it with a small test and should be sufficient for the UnifiedPOS requirements. Okay, so the driver allocates it, but never needs to do a kfree() on it, because the serio-layer takes care of it. Thanks for the infos, Niels Niels de Vos 2008-08-26T09:19:30 http://permalink.gmane.org/gmane.linux.kernel.input/5603 Hello Andrew, thanks for your review. However I will look into the suggestions of Dmitry which could include little changes to serio_raw instead of this new poskbd driver. Thanks again, Niels -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Niels de Vos 2008-08-26T08:11:29 http://permalink.gmane.org/gmane.linux.kernel.input/5602 Bug report was created: http://bugzilla.kernel.org/show_bug.cgi?id=11428 -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Németh Márton 2008-08-26T05:29:33 http://permalink.gmane.org/gmane.linux.kernel.input/5601 Your email just won you $800,000.00USD from ECOWAS. email Mr Peter Donald with your details. Full Name: Address: Sex: Age: Tel: Country Of Residence: Email Address: mr.peterdonald< at >live.com -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Foundazion Di Vittorio 2008-08-25T12:38:12 http://permalink.gmane.org/gmane.linux.kernel.input/5600 What I could find out since then is that the Linux kernel 2.6.25 is working correctly, but 2.6.26-rc3 is bad. I am about to "git bisect" the problem and I'll create a bugreport and provide the asked information. This will take some time, however, as I am currently busy with different topics. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Németh Márton 2008-08-25T06:47:04 http://permalink.gmane.org/gmane.linux.kernel.input/5599 It seems that the status of LID device is correct, but there is no LID input event. Right? Will you please enable the CONFIG_ACPI_DEBUG in kernel configuration and boot the system with the option of "acpi.debug_layer=0x00090004 acpi.debug_level=0x01f"? After pressing the LID switch several times, please attach the output of dmesg. It will be great if you can attach the output of acpidump. Of course you can open a new bug in bugzilla and attach the output of dmesg, acpidump. http://bugzilla.kernel.org/enter_bug.cgi?product=ACPI Thanks. -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Zhao Yakui 2008-08-25T01:11:47 http://permalink.gmane.org/gmane.linux.kernel.input/5598 Maybe. And in fact it already is! As I delved further in to this issue, I find that not only is there a patch in tslib to use EVIOCGRAB, but there is also a patch in the kernel to exclude the "ABS_X + ABS_Y + BTN_TOUCH" case from mousedev, making the EVIOCGRAB patch pointless. And there might even be another patch in the kdrive Xserver to use EVIOCGRAB in a different context (which might not actually be being used, I'm not sure). A twisted maze of little passages, all twisted. :-) But I am firmly against carrying patches like this which cannot go upstream. They can lead to subtle incompatibilities and can be hard to get rid of. I much prefer a solution that can work for everyone, and I currently think the BTN_TOUCH -> BTN_STYLUS change is that solution. It remains to be seen which I can push into the openmoko source tree :-) Thanks, NeilBrown -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://v Neil Brown 2008-08-24T23:48:54 http://permalink.gmane.org/gmane.linux.kernel.input/5596 Thanks Dmitry, I will take a look at the cm109 driver to see how setkeycode/getkeycode support is implemented and how this fits into the yealink code. As soon as I have done that (and cleaned up a few things) I will post the code as a patch. Best regards, -Thomas Am Freitag, den 22.08.2008, 16:02 -0400 schrieb Dmitry Torokhov: -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo< at >vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Thomas Reitmayr 2008-08-23T12:39:16 http://permalink.gmane.org/gmane.linux.kernel.input/5595 The driver(s) below do not use LINUX_VERSION_CODE nor KERNEL_VERSION. drivers/input/keyboard/bf54x-keys.c drivers/input/touchscreen/mainstone-wm97xx.c This patch removes the said #include <version.h>. Signed-off-by: Huang Weiyi <weiyi.huang< at >gmail.com> diff --git a/drivers/input/keyboard/bf54x-keys.c b/drivers/input/keyboard/bf54x-keys.c index 54ed8e2..6f227d3 100644 --- a/drivers/input/keyboard/bf54x-keys.c +++ b/drivers/input/keyboard/bf54x-keys.c < at >< at > -29,7 +29,6 < at >< at > */ #include <linux/module.h> -#include <linux/version.h> #include <linux/init.h> #include <linux/fs.h> diff --git a/drivers/input/touchscreen/mainstone-wm97xx.c b/drivers/input/touchscreen/mainstone-wm97xx.c index 283f93a..37a555f 100644 --- a/drivers/input/touchscreen/mainstone-wm97xx.c +++ b/drivers/input/touchscreen/mainstone-wm97xx.c < at >< at > -25,7 +25,6 < at >< at > #include <linux/module.h> #include <linux/moduleparam.h> -#include <linux/version.h> #include <linux/kernel.h> #include <linux/init.h> #include <linux/delay.h> -- To unsubsc Huang Weiyi 2008-08-23T05:56:18 http://permalink.gmane.org/gmane.linux.kernel.input/5594 Applied, thanks Henrik. Dmitry Torokhov 2008-08-22T20:27:57 http://permalink.gmane.org/gmane.linux.kernel.input/5592 Not that I know of. No, it is a different manufacturer, thay won't be comatible. Dmitry Torokhov 2008-08-22T20:03:44 http://permalink.gmane.org/gmane.linux.kernel.input/5591 Hi Thomas, On Fri, Aug 22, 2008 at 07:01:28PM +0200, Thomas Reitmayr wrote: Do you think that we need to add more keymaps to the kernel? What I woudl like to see is adding setkeycode/getkeycode support to yealink so proper keymap can be loaded from userspace (udev, hal, whatever) when a device is plugged into a box. USB-P1K coudl also get the new keymap loaded from userspace while keeping the current legacy keymap for existing users. No, that is not a good idea. Would you mind posting it as a patch - it is much easier to comment on it in e-mail... Thanks! Dmitry Torokhov 2008-08-22T20:02:34 Search the mailing list at Gmane query http://search.gmane.org/?group=$group=gmane.linux.kernel.input