On Wednesday 21 March 2007 18:03, johann deneux wrote:
On 3/21/07, Jiri Slaby [EMAIL PROTECTED] wrote:
Dmitry Torokhov napsal(a):
On 3/21/07, johann deneux [EMAIL PROTECTED] wrote:
I would suggest adding a new effect type (3d effect) and extending the
union in struct ff_effect.
Let
decide if they want to use ABS_Z events...
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
it cannot
emulate might be a better fix?)
Actually the keyboard driver should not emit input events for that key code.
Is this a USB keyboard?
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
On Sunday 25 March 2007 01:27, Parag Warudkar wrote:
Actually the keyboard driver should not emit input events for that key code.
Is this a USB keyboard?
--
Dmitry
Yes this is a USB keyboard.
Any hint as to where I should start looking to make the driver not
emit input event
Hi Pete,
On Monday 19 March 2007 21:02, Pete Zaitcev wrote:
On Wed, 7 Mar 2007 17:23:05 -0500, Dmitry Torokhov [EMAIL PROTECTED]
wrote:
It seems that if a process keeps a character device open then other
processes will also be able to get into filp-f_op-open(inode,filp)
in chrdev_open
to keep even dead modules
compilable... I think it is time for power.c to go. Now that we have ACPI
using input layer to report buttons/lid I don't see it coming back.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
Hi Greg,
On Saturday 10 March 2007 02:22, Greg KH wrote:
On Sat, Mar 10, 2007 at 02:12:04AM -0500, Dmitry Torokhov wrote:
On Saturday 10 March 2007 01:55, Greg KH wrote:
On Fri, Mar 09, 2007 at 10:54:43PM -0800, Greg KH wrote:
On Sat, Mar 10, 2007 at 01:37:34AM -0500, Dmitry Torokhov
On Sunday 25 March 2007 14:19, Pete Zaitcev wrote:
On Sun, 25 Mar 2007 01:34:02 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
+ * Without this, a touchpad may report an unchanged
position,
+ * then a sync. The input_event() eats the position
report
On 3/26/07, Pete Zaitcev [EMAIL PROTECTED] wrote:
On Sun, 25 Mar 2007 23:19:38 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
I tried to reproduce warping on console but could not for some reason. Could
you
please try the patch below and tell me if it fixes the problem for you?
+++ work
On Monday 26 March 2007 17:42, Pete Zaitcev wrote:
On Mon, 26 Mar 2007 15:30:42 -0400, Dmitry Torokhov [EMAIL PROTECTED]
wrote:
Regarding the synaptics driver and scroll problem. Yesterday I
scrolled twice through entire Remarque's Spark of Life off lib.ru
(once with 0.14.2 and once
away.
--
Dmitry
Input: remove old USB touchscreen drivers
itmtoch, mtouchusb and touchkitusb have been replaced with
composite usbtouchscreen driver and can be removed now.
Signed-off-by: Dmitry Torokhov [EMAIL PROTECTED]
---
drivers/usb/input/itmtouch.c| 271
and Display selection is
KEY_SWITCHVIDEOMODE, from the discussion they seemed the less bad
keycodes.
* keymaps are now declared initdata in order to save some memory
Everyting applied to the input tree. Used new KEY_DISPLAYTOGGLE instead
of KEY_SCREEN.
Thank you Eric.
--
Dmitry
-sudden-warps-in-mousedev.patch
Slightly different fix is already in input tree. I'd perfer waiting
for 2.6.22 as this only affects touchpads when not using synaptics X
driver (which most distributions use by default).
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux
if anything unusual
happens.
You know, I would not call turning leds on an off an unusual operation
for a keyboard.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org
,
this should not be missing.
Is there something wrong, or could there be a seemingly unrelated option
that I need to turn on?
Please make sure that you have CONFIG_USB_TOUCHSCREEN turned on.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
On 07/04/07, Andrew Morton [EMAIL PROTECTED] wrote:
On Wed, 4 Apr 2007 22:05:40 +0200 Dmitry Adamushko
[...]
o Make TASK_PREEMPTS_CURR(task, rq) return true only if the task's
prio is higher than the current's one and the task is in the active
array.
This ensures we don't make redundant
! ;)
Here is what I have in my .vimrc:
highlight RedundantWhitespace ctermbg=red guibg=red
match RedundantWhitespace /\s\+$\| \+\ze\t/
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
repeated
about 10 times.
Well, it's a late hour, so maybe I'm missing something... but it does
look to be HZ and will run time interval related issue. Like
described in (*). Or maybe we both observe similar situations but have
different reasons behind them.
-Mike
--
Best regards,
Dmitry
timer_ISR -
update_process_times() like scheduler_tick(). So if task's running
intervals are shorter than 1/HZ, it's not always accounted -- so cpu%
may be wrong for such a task...
--
Best regards,
Dmitry Adamushko
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
CPU. So
maybe something fishy is going on with accounting.
I just wonder, why it's so easily reproducible in my case for both
mainline and SD (besides a 2.6.13 mainline, but I have to re-run all
the tests letting tenp run longer for the sched_time to be
accumulated)...
--
Best regards,
Dmitry
From: Dmitry Adamushko [EMAIL PROTECTED]
o Fixed a mail client (shouldn't be white-space damaged now);
o Andrew, a patch against SD will follow.
---
o Make TASK_PREEMPTS_CURR(task, rq) return true only if the task's
prio is higher than the current's one and the task is in the active
array
.
+ if (error)
+ goto err_free_evdev;
error = device_add(evdev-dev);
if (error)
- goto err_free_evdev;
+ goto err_remove_chrdev;
error = input_register_handle(evdev-handle);
if (error)
Thank you for reviewing this!
--
Dmitry
Hi Nicolas,
On 4/9/07, Nicolas Boichat [EMAIL PROTECTED] wrote:
Hi Dmitry,
Sorry I did not receive your message originally, someone else pointed it
to me recently, and I recovered it from LKML archives.
For some reason your server does not like @insightbb.com addresses.
- Invert y axis
device polling timer when the device is open.
- Others minor fixes asked by Dmitry Torokhov.
Signed-off-by: Nicolas Boichat [EMAIL PROTECTED]
Thanks.
I've been assuming that this patch will go via Jean, since it is in
drivers/hwmon/applesmc.c. But perhaps that is inappropriate, and it is
more
On Monday 09 April 2007 18:36, Helge Hafting wrote:
On Fri, Apr 06, 2007 at 10:37:12PM -0400, Dmitry Torokhov wrote:
On Friday 06 April 2007 20:54, Helge Hafting wrote:
I have an usb touchscreen (egalax variety) that works with
the 2.6.18 kernel supplied by debian.
It fails when I
to obsolete this function.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Thursday 05 April 2007 10:23, Karl Pickett wrote:
Dmitry, please use this instead of my previous patch. Thanks to
Vincent for the code review , fixes, and testing.
Applied to the input tree; thank you Karl and Vincent.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe
On 4/10/07, Helge Hafting [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
Hmm, I am concerned because not only you don't have an input device created,
you don't even see the driver being registered with usbcore. Could you please
try booting with debug_initcall to see with what error code
if the task may preempt the current one.
Signed-off-by: Dmitry Adamushko [EMAIL PROTECTED]
---
--- linux-2.6.21-rc6-mm1/kernel/sched-orig.c2007-04-09 10:10:52.0
+0200
+++ linux-2.6.21-rc6-mm1/kernel/sched.c 2007-04-09 17:07:12.0 +0200
@@ -4022,14 +4022,14 @@ EXPORT_SYMBOL
{ pretty same / worse / much worse } feeling of
interactivity with git-gc running at the default (0) and, say, 5 or 10
nice levels?
TIA,
--
Best regards,
Dmitry Adamushko
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
684 S 0.0 0.1 0:00.06
git-repack
12366 surya 20 19 4440 228 228 S 0.0 0.0 0:00.00
git-repack
--
Best regards,
Dmitry Adamushko
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
On 4/11/07, Helge Hafting [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
*sigh* When will I learn to spell names of kernel parameters
correctly? It is initcall_debug, not debug_initcall :( Could you try
again, please?
Here is the dmesg for rc5mm4 with initcall_debug, showing how
no usbtouch
can't know.
Did another test with hackbench and git-gc both at same priorities
and captured the top output, in here all of them seem to have
same priority..
Yep, this one looks good.
thanks.
surya.
--
Best regards,
Dmitry Adamushko
-
To unsubscribe from this list: send the line unsubscribe
taking into account the old_prio, although this
slot can be prohibited by a new p-static_prio. It's only for the very
first slot so one may call it err.. a feature (?)
--
Best regards,
Dmitry Adamushko
--- linux-2.6.21-rc6-mm1/kernel/sched-orig3.c 2007
when you reload
psmouse module. I did not have time to look further.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
On 4/13/07, Dave Jones [EMAIL PROTECTED] wrote:
On Fri, Apr 13, 2007 at 03:18:32PM -0400, Dmitry Torokhov wrote:
Hi Dave,
On 4/13/07, Dave Jones [EMAIL PROTECTED] wrote:
I just had a user file the report below, which iirc, was deemed a false
positive. Didn't we add something
and analyzing the
dirrerences can highlight differences between kernel style and
author's (note that I do not advocate mechanically passing
everything though Lindent).
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
support, the i8042 driver thinks it has a keyboard to handle and tries to
handle it during the suspend, which fails. I don't know why it fails during
the second suspend, though.
Dmitry, could you please have a look?
This is wierd as i8042 does not use suspend_late/resume_early hooks and
so
On 2/8/07, Greg KH [EMAIL PROTECTED] wrote:
And it should also alow for proper power management functionality, using
the changes that Linus put into the driver core about 8 months ago.
Don't worry, I have input patches queued up next for you Dmitry :)
Greg,
Could you please forward me
On 2/21/07, CIJOML [EMAIL PROTECTED] wrote:
Hi,
can anybody reply to this and share his/her opinion?
Input core already exports uniq to udev and also via sysfs.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
On 2/21/07, Marcel Holtmann [EMAIL PROTECTED] wrote:
Hi Dmitry,
can anybody reply to this and share his/her opinion?
Input core already exports uniq to udev and also via sysfs.
so do you think it would be better to create phys as a string of the
source and destination address like src-dst
Hi Marcel,
On 2/21/07, Marcel Holtmann [EMAIL PROTECTED] wrote:
Hi Dmitry,
can anybody reply to this and share his/her opinion?
Input core already exports uniq to udev and also via sysfs.
so do you think it would be better to create phys as a string of the
source
On 2/21/07, Arkadiusz Miskiewicz [EMAIL PROTECTED] wrote:
#
# USB HID Boot Protocol drivers
#
CONFIG_USB_KBD=m
CONFIG_USB_MOUSE=m
Please do not enable USB boot protocol drivers unless generic HID
driver is not working for you.
--
Dmitry
-
To unsubscribe from this list: send the line
to the flashing of the
keyboard LEDs
in response to the kernel panic.
Could somebody fix this please?
Hi Mark,
Please try 2.6.21-rc1, it should be fixed properly there. If not
please let me know.
Thanks!
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
in this function.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
later.
Why would you not want to have what you call bitwrap as a standard
behavior? Most placed to not use modulus because they know the kind of
data they are working with but should still be fine if generic
implementation did that.
--
Dmitry
-
To unsubscribe from this list: send the line
On 2/23/07, Richard Knutsson [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
On 2/23/07, Richard Knutsson [EMAIL PROTECTED] wrote:
Milind Choudhary wrote:
On 2/23/07, Richard Knutsson [EMAIL PROTECTED] wrote:
+#define BITWRAP(nr)(1UL ((nr) % BITS_PER_LONG))
make the whole
On 2/23/07, Richard Knutsson [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
I was not talking about name (I hate BITWRAP) but behavior.
Oh, my bad :)
but mainly since it only enables wrapping of the long-type.
I'd provde BIT and separate LLBIT for ones who really need long long.
People
On 2/23/07, Richard Knutsson [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
Hm, I thought as was clear, but apparently I messed up explaining my
position:
1. I don't like BITWRAP name at all and I don't want anything like
that near input code. I think BIT is just fine.
Oh, I think I
On Friday 23 February 2007 19:44, Pete Zaitcev wrote:
On Fri, 23 Feb 2007 10:06:14 -0500, Dmitry Torokhov [EMAIL PROTECTED]
wrote:
On 2/23/07, Pete Zaitcev [EMAIL PROTECTED] wrote:
void input_release_device(struct input_handle *handle)
{
if (handle-handler-start
are not constant
but compiler will not help us in this case...
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
, but sometimes it is nice to be able to write
a = BIT(b) | BIT(c);
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
shoudl register. Tnen atkbd would bind to
that new port and function as usual. The only problem is that you
woudl need to bind you driver to the keyboard port from userspace (via
sysfs - /sys/bus/devices/serioX/drvctl)
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
On Tuesday 20 February 2007 04:19, Nicolas Ferre wrote:
Add support for the ads7843 touchscreen controller to the ads7846
driver code.
Applied to the input tree, thank you.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
}
Hm, interesting. Looks like a pointer points to nowhere in
input_unregister_device(), but I don't know which one. This may be
an evdev problem ...
Please try the patch below.
--
Dmitry
Input: use krefs for refcounting in input handlers
This should fix problems whith accessing memory
that
encodes the fact /event happened/ and not just /event happened _and_ a
caller has got scheduled back earlier than timeout.
Thanks
Eli
--
Best regards,
Dmitry Adamushko
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
at the State:
field. It should be R in case wake_up_*() was called for this task.
--
Best regards,
Dmitry Adamushko
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
On 3/1/07, Kristian Grønfeldt Sørensen [EMAIL PROTECTED] wrote:
On Thu, 2007-03-01 at 00:36 -0500, Dmitry Torokhov wrote:
Please try the patch below.
Hmmm. Is the diff against 2.6.20? All hunks except one fails when i try
it. If I pass -F 3 to patch, then one more hunk succeeds. Am I doing
On 3/1/07, Kristian Grønfeldt Sørensen [EMAIL PROTECTED] wrote:
Hmmm.
Now i get this BUG:
Does it die the same way if you just unload the button driver without
suspending?
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On 3/1/07, Kristian Grønfeldt Sørensen [EMAIL PROTECTED] wrote:
On Thu, 2007-03-01 at 15:25 -0500, Dmitry Torokhov wrote:
On 3/1/07, Kristian Grønfeldt Sørensen [EMAIL PROTECTED] wrote:
Hmmm.
Now i get this BUG:
Does it die the same way if you just unload the button driver without
On 3/5/07, Marcel Holtmann [EMAIL PROTECTED] wrote:
This also means that the current keyboard and mouse
input devices will become a HID driver.
Are you talking about usbmouse and usbkbd?
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
and providing access to
HID transports (USB/BT) then writing tiny drivers adjusting just a
part of hid_input_event and relying on default implemenattaion where
it makes sense will become a breeze.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
request though - please send patches
inline instead of attachments, or, if you need to send it as an
attachment then put patch description and signed-off-by there as well
so I don't have to reassemble it.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
Hi Marcel,
On 3/5/07, Marcel Holtmann [EMAIL PROTECTED] wrote:
Hi Dmitry,
This also means that the current keyboard and mouse
input devices will become a HID driver.
Are you talking about usbmouse and usbkbd?
no, because if I recall correctly these are the boot mode drivers and
actually
as
an attachment... Examples are: REL_WHEEL does not belong to evbit, using
input_free_device() is not allowed after input_unregister_device(), etc.
I tried to fix everything I notoiced; if you could try the patch below
and verify that it still works I will apply it to teh input tree.
Thanks.
--
Dmitry
keep Oliver's change and require attribute
implementations to offload delete me kind of actions to workqueues.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
nothing happens untul it actually gets scheduled.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
this?
There were some issues with AUX IRQ delivery test that is part of AUX
port probe. They should be fixed in the latest mainline. You might be
inetrested in this commit:
1e4865f8d469b1...
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
Hi,
It seems that if a process keeps a character device open then other
processes will also be able to get into filp-f_op-open(inode,filp)
in chrdev_open() even after a driver called cdev_del() as part of its
unwind procedure. Is this correct or am I missing something?
Thanks!
--
Dmitry
),
+ phantom%u, minor);
+
Error handling is needed.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org
On 3/7/07, Jiri Slaby [EMAIL PROTECTED] wrote:
Dmitry Torokhov napsal(a):
Hi Jiri,
Hi.
On 3/7/07, Jiri Slaby [EMAIL PROTECTED] wrote:
add sensable phantom driver
...
General question - can this driver use force-feedback mecahnisms
already present in kernel instead of exporting raw
/2 mice. The fix is confirmed to be working for
MSI K8M800 and also confirmed not to break previous fix (re. bugzilla
7833).
Changelog:
--
Dmitry Torokhov (1):
Input: i8042 - another attempt to fix AUX delivery checks
Diffstat:
-
i8042.c | 10 --
1 files changed, 8
of boot with i8042.debug
log_buf_len=131072?
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Wednesday 07 March 2007 16:50, Dmitry Torokhov wrote:
On 3/7/07, Ash Milsted [EMAIL PROTECTED] wrote:
So, I tracked this down to 2.6.21-git7, the first snapshot that gives me
this problem. Tellingly it does contain an input tree merge. I would git
bisect
but I don't have a local
On 3/27/07, Chuck Ebbert [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
The driver grabs tochpad with EVIOCGRAB ioctl to prevent input events
from bveing delivered to X through /dev/input/mice which is still in
whidespread use. That's why evtest does not work. We could as Peter
(CCed
On 3/27/07, Chuck Ebbert [EMAIL PROTECTED] wrote:
Dmitry Torokhov wrote:
And why did the mouse numbers all get rearranged in 2.6.20, e.g.
mouse1 became mouse2 for many people?
Input devices are not guaranteed to be stable.
So people with z-axis mice need to redo their X config for each
;
by
__u8 motor;
__u8 type;
Splitting type field seems to be a good idea.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
?
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
. This is not a nice API to provide. Will
try to think of some solution which would have reasonable
nastiness/functionality ratio.
The proper fix would be teach X to recognize hotplug events. I've
heard they are working on it.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
call it for reports
they don't need to do special processing on.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http
/input.
Please let me know what you think.
--
Dmitry
From: Ivo van Doorn [EMAIL PROTECTED]
Input: rfkill - Add support for input key to control wireless radio
Signed-off-by Ivo van Doorn [EMAIL PROTECTED]
Signed-off-by: Dmitry Torokhov [EMAIL PROTECTED]
---
drivers/input/misc/Kconfig
Input: polled device skeleton
Signed-off-by: Dmitry Torokhov [EMAIL PROTECTED]
---
drivers/input/misc/Kconfig | 11 ++
drivers/input/misc/Makefile|1
drivers/input/misc/input-polldev.c | 149 +
include/linux/input-polldev.h | 46
On Thursday 29 March 2007 23:06, Li Yu wrote:
Dmitry Torokhov wrote:
On 3/28/07, Jiri Kosina [EMAIL PROTECTED] wrote:
The crucial thing here is that all reports but the ones that the driver
registered to will be processed in a standard way by the generic hid bus
layer, and those reports
and manage lifetime for all components
at once.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
dropped it because it
went oops.
- git-block is back, minus the problematic unplugging rework.
- Lots of x86 updates.
- lguest is being redone and has been dropped
- The IDE development tree has been restored
Andrew,
Did you drop git-input? I do not see it anywhere
--
Dmitry
On 3/30/07, James Bottomley [EMAIL PROTECTED] wrote:
On Fri, 2007-03-30 at 09:15 -0400, Dmitry Torokhov wrote:
If you want to manage lifetime rules independently you might want to
not embed struct device into you subsystems objects but attach them
via pointers and use device_create(). Now
On 3/28/07, Jiri Slaby [EMAIL PROTECTED] wrote:
Jiri Slaby napsal(a):
Dmitry Torokhov napsal(a):
On Tuesday 27 March 2007 17:34, johann deneux wrote:
What about adding a member to ff_effect which would be the number of the
motor?
We can't change the layout of ff_effect too much though, so
know but for refcounted objects you can't really tell when they will
actually be freed. It depends when their last user drops off.
BTW, I can't either as I don't have any laptops with RF swtches ;)
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
rfkill_register() last (which you need to do because driver has to be
almost fully functional to be able to serve toggle_radio calls) you
can always call rfkill_free() if something fails.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
?
This would not quite work for (potentially out of tree) HID drivers
brought in after compiling generic HID driver but that should be a
very rate occurance and we still can manually bind such drivers via
sysfs bind/unbind and new_id manipulations.
--
Dmitry
-
To unsubscribe from this list: send the line
in atkbd probe but maybe we should
move that in input core and reset leds as part of
input_register_device()?
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo
On 3/30/07, Pete Zaitcev [EMAIL PROTECTED] wrote:
On Fri, 30 Mar 2007 14:14:20 -0400, Dmitry Torokhov [EMAIL PROTECTED] wrote:
I didn't like a) layering violation, and b) that they defeat filtering
unconditionally. Why have any filtering then?
Instead, I propose for USB HID driver
. The Belkin Flip KVM overloads LED usages to give software
control
over the device, providing options to flip either audio, video or both.
However,
without an input mapping to the Off-hook and Speaker LED usages, this
functionality
isn't available.
Dmitry, would adding these two LED_
Hi Dan,
On Sunday 01 April 2007 23:28, Dan Engel wrote:
On Sun, 2007-04-01 at 19:43 +0200, Jiri Kosina wrote:
On Sun, 1 Apr 2007, Dmitry Torokhov wrote:
No, I do not want to add any more LED constants to input. In fact I
think that adding constants beyond keyboard indicators
that for most
drivers hooking into parsed data would be much easier. That means that
we need to allow defining 2 hooks - one for raw data and another for
parsed reports and let drivers decice which one they want to use.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
this is related? Should I give your patch a spin to see if it
fixes the problem?
Are you saying that NumLock LED is lit or that keyboard is in NumLock
state? Does the same happen if you boot with init=/bin/bash?
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
driver should resume
work for this joystick, IOW, it should register back its input device again.
Why would we want to revert to using generic HID's implementation if we
know that it is broken for that particular device???
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe
rfkill patch that I posted before except that everything is moved in
net/ instead of being in drivers/input/misc.
I will make sure that input-polldev will get into input three tough.
--
Dmitry
From: Ivo van Doorn [EMAIL PROTECTED]
Input: rfkill - Add support for input key to control wireless
using bind/unbind via sysfs, but at
this moment there are 0 drivers for HID bus and hopefully people will
be submittin them for inclusion.
--
Dmitry
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http
On 4/2/07, Dan Engel [EMAIL PROTECTED] wrote:
On Mon, 2007-04-02 at 00:04 -0400, Dmitry Torokhov wrote:
Actually I want to keep input subystm out of the loop here, since LEDs
such as mail, charging, etc have nothing to do with user input but
rather reflect overall system/application state
101 - 200 of 27825 matches
Mail list logo
