a broken-out version with separate changes, that'd be great.
Thanks,
--
Jiri Kosina
-
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
of the device,
so just adding it to blacklist should suffice.
Thanks,
--
Jiri Kosina
SUSE Labs
-
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
this *is* a blacklisted ID ...
Yes, so it definitely should be ignored and not claimed by the usbhid
subsystem.
Could you please verify in /sys/bus/usb/drivers/usbhid whether this device
is really claimed by the usbhid driver? Do you have other HID devices in
the system?
--
Jiri Kosina
-
To unsubscribe from
.
This also makes me to speed up with one of my items on TODO list - rename
usbmouse and usbkbd to something that wouldn't be so confusing and
wouldn't make people think that they should enable these drivers if they
want support for USB keyboards/mice. Will queue this for 2.6.22.
--
Jiri Kosina
SUSE
,
this line looks bogus to me.
--
Jiri Kosina
-
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/
thoroughly soon, if noone beats me with it)
From: Jiri Kosina [EMAIL PROTECTED]
8250: fix possible deadlock between serial8250_handle_port() and
serial8250_interrupt()
Commit 40b36daa introduced possibility that serial8250_backup_timeout() -
serial8250_handle_port() locks port.lock
On Mon, 23 Apr 2007, Jeremy Fitzhardinge wrote:
I got this on resume; it looks like a Bluetooth and/or USB problem.
PM: Removing info for No Bus:hci0
BUG: sleeping function called from invalid context at net/core/sock.c:1523
in_atomic():1, irqs_disabled():0
1 lock held by khubd/180:
#0:
whether this will be processed properly in time when
going to suspend.
Thanks,
--
Jiri Kosina
-
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
that it is also possible to obtain -mm tree through
git, which provides very convenient means for bisecting. This is what I
usually do.
--
Jiri Kosina
-
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
.
Thanks. Cc's added.
Remains unsolved in 2.6.21-rc3-mm2.
Does a PS/2 keyboard behave for you?
Nowadays I forward all USB HID related issues to Jiri Kosina ;) (CCed).
Hi,
more importantly, does 2.6.21-rc3 work for you? There are not that many
USB HID/hidinput specific patches in -mm, so
On Fri, 9 Mar 2007, Jiri Kosina wrote:
If this is present also in vanilla and not only in -mm, could you please
try reverting commits 4237081e573b99a48991aa71364b0682c444651c and
d4ae650a904612ffb7edd3f28b69b022988d2466 and let me know if the
situation gets any better?
Hi Jiri,
or even
the parser
code has been rewritten. The hid_parser structure in question is living
for very short time anyway, so it shouldn't be that big issue.
Thanks.
From: Jiri Kosina [EMAIL PROTECTED]
Subject: [PATCH] HID: allocate hid_parser through vmalloc()
hid_parser is non-trivially large structure
,
--
Jiri Kosina
-
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/
situation?
Thanks,
--
Jiri Kosina
-
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/
- no failure so far.
Thanks for testing. The patch fixing this already went to Linus in todays
HID/USB HID update (which has not yet been merged).
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
what I am currently implementing also
for the new hidraw userspace interface.
Thanks,
--
Jiri Kosina
-
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
HID debugging, but
usb debug should be more interesting now) and send us the logs?
Thanks,
--
Jiri Kosina
-
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
to get
any free pages eventually ... ?
--
Jiri Kosina
-
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/
keyboards.
Do you happen to have USB Legacy setting in BIOS? If so, could you try
turning it off?
Also, does this happen only with one particular type of keyboard, or with
various ones?
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
the
result?
--
Jiri Kosina
-
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/
been deleted from CC in the middle of the
thread, so sorry for superfluous reply. However, the fact about usbkbd
still applies - it is almost certain that you don't want to use it, and
you'd better keep it unloaded.
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux
that they
could be applied directly using patch -p1 against toplevel of the kernel
tree (your patch was just against hid-core.c, but without any path)
- please inline patches in message and do not attach them, if possible
I will submit the patch to stable team.
Thanks,
--
Jiri Kosina
SUSE Labs
and mouse is switched to HID mode, if they support it)?
Marcel, do you have any idea how this could happen?
Thanks,
--
Jiri Kosina
-
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
#define DEBUG and #define DEBUG_DATA
and send us the output?
--
Jiri Kosina
-
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
DISK drive
Looks like it's related to some change in drivers/ide. As there have been
only 13 patches in this area between rc2 and rc3, it should take only 3 or
4 reboots to figure the offending patch using git-bisect - could you
please give it a try?
Thanks,
--
Jiri Kosina
-
To unsubscribe
... ?
--
Jiri Kosina
-
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/
can check this in
/sys)? When the quirk works correctly, only the keyboard interface should
be bound to usbhid driver. Please check the binding both before and after
suspend/resume cycle, and let me know.
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux
driver works again. So i think this is
maybe a problem in X?
... but there is something apparently wrong either with the appletouch
driver or X. Could you test via evtest whether the events are properly
generated by the kernel? If they do, I'd say it is almost certainly X bug.
Thanks,
--
Jiri
is really trivial to
use - see the manpage for the example on the process of bisecting.
--
Jiri Kosina
-
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
://www.mail-archive.com/linux-kernel@vger.kernel.org/msg128743.html
--
Jiri Kosina
-
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
this started to happen after
bluez-utils update, as you stated in the mail above some time ago?
Thanks,
--
Jiri Kosina
-
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
should be rather rewritten not to allocate such large contignuous
chunks of memory through kmalloc().
--
Jiri Kosina
-
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
of max_loop which is large enough. Or am I just blind?
The while (nbl max_loop) which immediately follows is then going to
corrupt memory, right?
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
: Thomas Renninger [EMAIL PROTECTED]
Date: Tue Feb 27 12:13:00 2007 -0500
Hi,
there have been other issues reproted with this patch, it is probably
going to be reverted - see http://lkml.org/lkml/2007/3/23/104 and the
thread that follows.
--
Jiri Kosina
-
To unsubscribe from this list: send
).
--
Jiri Kosina
-
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 Sun, 25 Mar 2007, Parag Warudkar wrote:
Yes this is a USB keyboard. Any hint as to where I should start
looking to make the driver not emit input event for keycode==0?
Was it always doing that? I'll add Jiri Kosina to the CC list as he's
involved with HID now.
Something (some
this could be possibly caused solely by
newer versions of bluez-utils, as Amedee stated in some of the threads
above?
--
Jiri Kosina
-
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
* for paravirtualization. The following will never clobber any registers:
--
Jiri Kosina
-
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
it nevertheless, but it'd be
much more convenient if you manage to send a patch.
Thanks,
--
Jiri Kosina
-
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
reverted to see if it helps?
I am unfortunately not able to reproduce it here on x86_64.
Thanks,
--
Jiri Kosina
-
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
On Thu, 12 Apr 2007, Jiri Kosina wrote:
Could you please
- try booting without any HID devices plugged in (i.e. usb mice, usb
keyboards) if the problem persists?
- recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps?
Do you compile with CONFIG_HIDRAW?
--
Jiri Kosina
On Thu, 12 Apr 2007, Jiri Kosina wrote:
- try booting without any HID devices plugged in (i.e. usb mice, usb
keyboards) if the problem persists?
- recompile 2.6.21-rc6-mm1 with git-hid.patch reverted to see if it helps?
Do you compile with CONFIG_HIDRAW?
Helge,
with your .config, my
the boot succeeds. When manually trying to modprobe ipmi_si after that,
the modprobe itself hangs, but the machine remains usable otherwise.
I still wonder if this could be related to what Helge was originally
reporting.
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe
On Thu, 12 Apr 2007, Jiri Kosina wrote:
CONFIG_IPMI_SI=y
hangs upon boot on the already mentioned printk from ipmi_si. With
CONFIG_IPMI_SI=m
the boot succeeds. When manually trying to modprobe ipmi_si after that,
the modprobe itself hangs, but the machine remains usable otherwise.
Actually
On Thu, 12 Apr 2007, Helge Hafting wrote:
The last messages (handwritten, somewhat shortened)
calling hid_init+0x0/0x10()
returned 0
ran for 0 msec
calling hid_init+0x0/0x50()
usbcore registered new interface driver hiddev
and then it hangs completely.
OK, so it hangs somewhere nearby
at different stages of boot, depending on your
local configuration/kernel version used.
Is vanilla 2.6.21-rc6 ok? If so, would you have time to bisect the
offending patch?
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
in the output (it should
read something like hid-core.c: report descriptor (size XY, read YZ) =
... some hexadecimal numbers. This should be output by the time the HID
device is connected.
This output is generated in usb_hid_configure() function in hid-core.c
--
Jiri Kosina
-
To unsubscribe from
On Wed, 21 Feb 2007, Adrian Bunk wrote:
Every file should include the headers containing the prototypes for
it's global functions.
Applied, thanks.
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
quite probable to me - I have been playing yesterday with
another masterpiece from Logitech (S510 keyboard), which also requires
fixing its report descriptor on-the-fly because it is fully usable :(
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
it, instead of being a kernel issue?
Thanks,
--
Jiri Kosina
-
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/
the
branch you switched to, which seems wrong to me.
This definitely worked previously (and works on other installations of
gitweb outside the kernel.org), so it might be worth fixing.
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body
to manually raise the brightness on the LCD. Quite annoying :)
I have bisected this to your commit
994efacdf9a087b52f71e620b58dfa526b0cf928
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
something like X?
I observed it only on console, but didn't experiment with it too much yet.
--
Jiri Kosina
-
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
Is this really a right thing to do?
--
Jiri Kosina
-
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/
calls from backlight driver, which won't get handled
properly by your code, in result confusing the brightness status.
I would suggest applying something like the patch below instead, if you
find it OK.
From: Jiri Kosina [EMAIL PROTECTED]
[PATCH] ibm-acpi: handle power calls from backlight
properly, which doesn't necessairly mean we will get
bd-props.power == FB_BLANK_UNBLANK, right?
--
Jiri Kosina
-
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
thing to do?
Also, it would be great if anyone who actually owns the hardware could
test that this makes the scrollwheel work.
Thanks.
From: Jiri Kosina [EMAIL PROTECTED]
[PATCH] [Bluetooth] hid quirks - mightymouse quirk
This patch allows bluetooth hid devices to use quirks which
to cause the bug)?
--
Jiri Kosina
-
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/
|6 +-
24 files changed, 1793 insertions(+), 1727 deletions(-)
Adrian Bunk (1):
HID: hid-debug.c should #include linux/hid-debug.h
Jiri Kosina (8):
USB HID: use CONFIG_HID_DEBUG for outputting report descriptor
HID: fix bug in zeroing the last field byte
that really need merging, so just to know what would be acceptable
for you at the time being.
Thanks,
--
Jiri Kosina
-
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
(), which just looks very sad
to me.
But OK, I will leave it in there.
--
Jiri Kosina
-
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
this solution oposes your taste (The point of a header file is to
*declare* things, not to have big data structures in), so I would
probably not go this way.
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL
On Sun, 4 Mar 2007, Mark Lord wrote:
This patch prevents total system lockup when using rfcomm devices.
I acknowledge that this patch fixes lockup for me too.
When debugging this, I also came across a different bug (spotted by
lockdep). Is the patch below applicable?
From: Jiri Kosina
system, for which there already is a
support?
Thanks,
--
Jiri Kosina
-
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
not yet
finished due to too many other pending things.
Thanks,
--
Jiri Kosina
-
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
this in my TODO, but I
guess it doesn't matter too much here.
Thanks,
--
Jiri Kosina
-
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
(declaring a byte array report) or declaring
a report which does not match the data contained. Parsing a report is
definitely a userland job.
Which is exactly what the new hidraw interface is going to provide.
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
to work on it in a future anyway.
Thanks,
--
Jiri Kosina
-
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/
kernelnewbies mailinglist
instead.
--
Jiri Kosina
-
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/
00 00
(and maybe ff 80 09 01 00 00 ?)
This doesn't look like what is currently supported by hid2hci function
switch_logitech(), but I would rather leave this to Marcel.
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
Linus,
could you please pull from 'for-linus' branch of
master.kernel.org:/pub/scm/linux/kernel/git/jikos/hid.git for-linus
to receive fixes for HID core layer and USB HID layer.
This update is needed to make the IOWarrior device driver (that got merged
during merge 2.6.21 merge
in this fashion so Li
tried to provide mechanism to augment default HID behaviour for sepcific
devices.
That's right. We could always extend the quirks so that it's long long, or
something like that, but this is also not sustainable in the long term.
--
Jiri Kosina
-
To unsubscribe from
);
will do.
--
Jiri Kosina
-
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/
is other mysterious thing? ;)
Yes, HUT is Hid Usage Table. You can obtain them from
http://www.usb.org/developers/hidpage/#Usage_Tables
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info
-g28defbea-dirty #131
[ 208.538260] -
[ 208.542611] inconsistent {hardirq-on-W} - {in-hardirq-W} usage.
[ 208.548600] swapper/0 [HC1[1]:SC0[0]:HE0:SE1] takes:
Perhaps something like the one below?
From: Jiri Kosina [EMAIL PROTECTED]
oprofile: fix potential deadlock
,SYMLINK+=input/appletouchpad
and the let Xorg use /dev/input/appletouchpad, which will always be a
symlink to the correct device.
--
Jiri Kosina
-
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
are really GCC bugs. Please examine the code
in question.
Anyway imho this time gcc got it right?
From: Jiri Kosina [EMAIL PROTECTED]
blockdev: bd_claim_by_kobject() could check value of unititalized pointer
Fixes this warning:
fs/block_dev.c: In function `bd_claim_by_kobject':
fs/block_dev.c:953
From: Jiri Kosina [EMAIL PROTECTED]
DCCP: proper optlen checking in do_dccp_getsockopt()
Robert Swiecki discovered [1] a signedness bug in checking of
optlen in do_dccp_getsockopt(). This bug can allow user to
read parts of the kernel memory.
[1] http://www.securityfocus.com/archive/1/463934/30
solution which would have reasonable
nastiness/functionality ratio.
--
Jiri Kosina
-
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
it
very badly, sorry for confusion.
Thanks,
--
Jiri Kosina
-
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/
-transport specific
The purpose of hidraw is to provide the applications the same
functionality they are having when using libhid/libusb, but in a
transport-independent way, as it is hooked to generic HID layer, which
works as a 'proxy' for different transports that use it.
--
Jiri Kosina
bug #228674. To see this bug, you must
first log in to an account with the appropriate permissions.
:)
Thanks,
--
Jiri Kosina
-
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
driver is needed or handling by (existing) generic HID layer is enough.
As an added value, hooking the hidraw code to this architecture would then
be rather a trivial task.
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
are defined in HUT 1.12 on page 62).
Thanks,
--
Jiri Kosina
-
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/
. Dan, could you please redo the patch to use the leds
infrastructure and send it to me?
Thanks,
--
Jiri Kosina
-
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
to ship a separate
userspace program along with the driver.
Thanks,
--
Jiri Kosina
-
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
this be OK by you?
Thanks,
--
Jiri Kosina
-
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/
the report, and issue input_event() itself
- pass it to hidraw and let userspace to consume it
This is going to work for the scenario you have described, right?
Thanks,
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED
me VID/PID for involved keyboards.
Fair enough, thanks.
Besides the trivial nitpicks above, I think that this fixed version is
fine. So as soon as you have the VIDs and PIDs of the hardware which
requires this, could you please update the patch and send it to me again?
Thanks,
--
Jiri Kosina
and rearranging it to be sorted again, queued for 2.6.22.
Thanks,
--
Jiri Kosina
-
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
code is
usualy more efficient than just ranting random ideas :)
Thanks,
--
Jiri Kosina
-
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
- Paul, what is the
current status please?
Thanks,
--
Jiri Kosina
-
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
of the quirk bitmask are going to be taken by
the quirk entries (so no, it's not related to the size of the table).
Thanks,
--
Jiri Kosina
-
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
] sys_socketcall+0x7a/0x261
[c01808ec] sys_ioctl+0x4c/0x68
[c0103dc8] sysenter_past_esp+0x5d/0x99
===
INFO: lockdep is turned off.
Code: Bad EIP value.
EIP: [] 0x SS:ESP 0068:c3885ddc
Kernel panic - not syncing: Fatal exception in interrupt
--
Jiri Kosina
is causing it.
--
Jiri Kosina
-
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/
will start bisection when I get back to the respective machine
(tomorrow) and will let you know.
--
Jiri Kosina
-
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
On Tue, 3 Apr 2007, Jiri Kosina wrote:
we're also having problems reproducing it on that same combination
(2.6.21-rc4 + my tree), so it points to something in -mm. Since your
trace is completely different right now it looks like something else
is fuzzing it up. Since the e1000 changes
allow it to vanish, don't worry.
We just have to make sure that new users will use hidraw instead, as it
provides more flexibility for the user, is not dependent on the underlying
transport protocol, etc.
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux-kernel
after all.
Pete, could you please resend your patch, with proper metadata, we need to
merge your one then.
Thanks,
--
Jiri Kosina
-
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
of hidraw (it's in -mm or I can send it to
you as a separate patch) and check whether you have any comments on this?
It would be good if you could use hidraw rather than reading raw usb data
through libusb.
Thanks.
--
Jiri Kosina
-
To unsubscribe from this list: send the line unsubscribe linux
1 - 100 of 6650 matches
Mail list logo
