gt; CC: sta...@vger.kernel.org
Applied, thanks.
--
Jiri Kosina
SUSE Labs
CROSOFT,
> USB_DEVICE_ID_MS_PIXART_MOUSE), HID_QUIRK_ALWAYS_POLL },
> { HID_USB_DEVICE(USB_VENDOR_ID_MICROSOFT,
> USB_DEVICE_ID_MS_POWER_COVER), HID_QUIRK_NO_INIT_REPORTS },
> { HID_USB_DEVICE(USB_VENDOR_ID_MICROSOFT,
> USB_DEVICE_ID_MS_SURFACE_PRO_2), HID_QUIRK_NO_INIT_REPORTS },
>
t
> to index field->usage (HIDIOCGCOLLECTIONINDEX) or field->value in
> HIDIOC{G,S}USAGES arrays, thus, avoiding speculation in the first load.
>
> Signed-off-by: Breno Leitao
> Cc:
Applied, thanks.
--
Jiri Kosina
SUSE Labs
gt;
> All errors (new ones prefixed by >>):
>
>drivers/hid/hid-microsoft.o: In function `ms_probe':
> >> hid-microsoft.c:(.text+0x2d7): undefined reference to
> >> `input_ff_create_memless'
Now fixed in the branch as below. Thanks!
From: Jiri Kos
HID_DG_STYLUS;
> ^~
>drivers/hid/hid-multitouch.c: In function 'mt_input_configured':
>drivers/hid/hid-multitouch.c:1527:12: error: 'struct hid_input' has no
> member named 'application'
> switch (hi->application) {
>^~
That is my mismerge. I've fixed it now.
Thanks for the report and sorry for the noise.
--
Jiri Kosina
SUSE Labs
dler to disable the interrupts while acquiring the lock.
> The callback may be invoked either in IRQ or BH context depending on the
> USB host controller.
> Use the _irqsave() variant of the locking primitives.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: se
_feature +1209 drivers/hid/hid-multitouch.c
Thanks, I've fixed that up in the branch.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
_PTP_BUTTONS'
> >> undeclared here (not in a function); did you mean
> >> 'MT_QUIRK_IGNORE_DUPLICATES'?
>MT_QUIRK_WIN8_PTP_BUTTONS,
>^
>MT_QUIRK_IGNORE_DUPLICATES
Ah, that's my mismerge (the for-next branch is OK), I'll f
th a Cooler Master Devastator with
> kbpoll=32, resulting in delay between events of 32 ms(values were taken
> from evtest).
>
> Signed-off-by: Filip Alac <filipa...@gmail.com>
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line
input: USB HID v1.11 Mouse
> [PixArt HP USB Optical Mouse] on usb-:00:14.0-2/input0
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ch.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
> In addition, if bNumDescriptors of the hid descriptor have an incorrect
> value, this can also cause out-of-bounds while approaching hdesc->desc[n].
>
> So check the size of hid descriptor and bNumDescriptors.
Applied to for-4.14/upstream-fixes. Thanks,
--
Jiri Kosina
SUSE Labs
--
To un
device, but apparently only 4.12 actually does so. Could you please
confirm that with usbmon traces?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
8191 instead of 65535).
>
> For reference, here are the full reports:
I am all for verbose changelogs, but including the rdesc dump is probably
a little bit too much :) So I've striped that and applied to
for-4.14/upstream-fixes.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this l
On Wed, 9 Aug 2017, Arvind Yadav wrote:
> usb_device_id are not supposed to change at runtime. All functions
> working with usb_device_id provided by work with
> const usb_device_id. So mark the non-const structs as const.
Applied to for-4.14/upstream.
--
Jiri Kosina
out the ID number.
Yeah, well, the symbolic names don't necessarily have to be used if the
device doesn't have any real recognizable branding name ...
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
f the original
> USB_DEVICE_ID_LOGITECH_C077 define or in the value assigned to
> it (0xc007).
This is something for Oliver to figure out -- Oliver, that appeared
through your commit a415457733b5f; are you able to still find out the
details?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To u
usb-:00:1d.0-1.1.1.1/input0
... this is most likely caused by e399396a6b0, and fix for that is queued
in hid.git as cf601774c9f ("HID: usbhid: fix "always poll" quirk"); I'm
planning to send it to Linus' tomorrow, but if you can double-check that
it does fix your issue as well,
yesterday pull request, sorry for
that. Applied now to for-4.13/upstream-fixes and will be sending upstream
next week.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 13 Jun 2017, Benjamin Tissoires wrote:
> BTW, the merge with your for-next branch is going to be tricky :(
I've just pushed the for-next merge. Second/third pair of eyes (scripted
eyes even better :) ) would be appreciated.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe f
in
> > 4.12-rc5, and you have 360 in your patch:
> > - { HID_USB_DEVICE(USB_VENDOR_ID_LOGITECH,
> > USB_DEVICE_ID_LOGITECH_G920_WHEEL) }
> > is added twice (the one in CONFIG_HID_LOGITECH should be dropped IMO).
>
> Only this one is would require a change now.
This
ching-fix' of
hid.git, and if no more issues are discovered, I'll push that to Linus
this week so that we finally get rid of this long-lasting PITA (while
still heading towards 'automatic' proper matching -- Benjamin already had
some proposals how to tackle this).
Thanks,
--
Jiri Ko
On Fri, 9 Jun 2017, Jiri Kosina wrote:
> This is something I've been wanting to fix for ages, but never really got
> to it. So let's take this as the final impulse to do it.
So I'd suggest to go with something like the below for 4.12-rc. Hmm?
From: Jiri Kosina <jkos...@suse.cz
ial and let it attach
as a 'last resort driver' if none of the specific driver picked the device
up during probe. But I don't think our current driver model allows this
easily ... or is there way I am not seeing?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line &
ed by Dell.
Ah, so you didn't mean "device IDs" in the sense of VID/PID, but branding
names.
Queued in for-4.12/upstream-fixes branch.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majo
On Tue, 6 Jun 2017, Sebastian Parschauer wrote:
> This mouse is also known under other IDs.
Do you know (some of the) other IDs?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vg
On Tue, 25 Apr 2017, Vasilis Liaskovitis wrote:
> Like other switches, the Aten CS-1758 KVM switch needs a quirk to avoid
> spewing errors:
>
> [12599018.071059] usb 5-2: input irq status -75 received
> [12599018.079053] usb 5-2: input irq status -75 received
Applied, thanks.
On Fri, 3 Mar 2017, Jaejoong Kim wrote:
> Jaejoong Kim (2):
> HID: cp2112: use proper hidraw name with minor number
> HID: hiddev: reallocate hiddev's minor number
Applied to for-4.12/hiddev. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line &qu
wacom) already
> retrieves the features manually.
Applied to for-4.12/nuke-no-init-reports-quirk. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
=2,
> resulting in a polling rate of 500Hz (verified with evhz).
>
> Signed-off-by: Tobias Jakobi <tjak...@math.uni-bielefeld.de>
Applied to for-4.12/upstream. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb&
escendent above a printk
>
> Signed-off-by: Joe Perches <j...@perches.com>
Applied to for-4.12/upstream. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More major
iver vendor" in case the driver seems to assume
initialized reports) at least for a few years.
I think that either doing it at a connect time, or during first
EVIOCGUSAGE ioctl() call is a must.
Otherwise, I'd be super-happy to finally get rid of this giant PITA.
Thanks!
and when we have some
> rapid open/closes on the mouse device.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
etty sure there are more.
So we'd rather be careful not to break hiddev by default.
I'll think about your RFC a little bit more.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel
On Thu, 12 Jan 2017, Johan Hovold wrote:
> These patches fix DMA buffers on stack and information leaks in the
> corsair HID driver.
>
> Note that this series has only been compile tested.
Adding Clément to CC, and applying to for-4.10/upstream-fixes branch.
Thanks!
--
Jiri Kosi
On Thu, 5 Jan 2017, Grant Grundler wrote:
> Local "#define DRIVER_LICENSE" obfuscates which license is used
> in MODULE_LICENSE(). "fgrep -R MODULE_LICENSE" is more informative
> when the string is hard coded in MODULE_LICENSE.
Applied to hid.git#for-4.11/upstream.
On Sat, 10 Dec 2016, Benjamin Tissoires wrote:
> Ouch. Sorry, I should have spotted this during review.
>
> Jiri, could you apply the following simple fix:
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-us
On Mon, 5 Dec 2016, Pan Bian wrote:
> Function hid_post_reset() should return negative error codes on
> failures. However, in its implementation, it incorrectly returns 1.
> This patch fixes the bug, returning proper error codes on failures.
Applied to for-4.10/upstream. Thanks,
--
Ji
lator_enable(ihid->pdata.supply);
>^~~~
> >> drivers/hid/i2c-hid/i2c-hid.c:1139:2: error: implicit declaration of
> >> function 'regulator_disable' [-Werror=implicit-function-declaration]
> regulator_disable(ihid->pdata.supply);
> ^~~~~~
On Thu, 3 Nov 2016, Oliver Neukum wrote:
> Like many similar devices it needs a quirk to work.
> Issuing the request gets the device into an irrecoverable state.
Applied to hid.git#for-4.9/upstream-fixes.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send th
y.
>
> Signed-off-by: Steinar H. Gunderson <sgunder...@bigfoot.com>
Applied for 4.9-rc. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Mon, 3 Oct 2016, Heiner Kallweit wrote:
> The hid-led driver works fine under 4.8.0, however with the next
> kernel from today I get this:
Queued in hid.git for 4.9-rc. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb&q
point of the change really.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
ng to a heap overflow.
Thanks for the fix. I've added Cc: stable, applied it to
for-4.7/upstream-fixes branch, and will be including it in a pull request
to Linus shortly.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body
; sizeof(u8)*U1_FEATURE_REPORT_LEN,
> HID_FEATURE_REPORT, HID_REQ_SET_REPORT);
I've already applied patch that fixes this (an one more callsite with the
same issue); I CCed you on the patch earlier today.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list:
help text as well, and applied. Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
let's remove the old USB LED driver.
>
> Signed-off-by: Heiner Kallweit <hkallwe...@gmail.com>
> Acked-by: Greg Kroah-Hartman <gre...@linuxfoundation.org>
I am applying this to hid.git#for-4.8/hid-led so that it goes together
with the addition of hid-led driver.
Greg, if you have a
> No changes, just resubmission to ensure absence of undesired line breaks
Line breaks are OK, but still your mailer converted tabs to space, which
equally breaks the application process.
I've fixed that up manually and applied, but please look into
reconfiguring your MUA for any future subm
do. It'll save me from rather boring hand-editting of the patch,
and we'll double-check whether your Thunderbird is now properly configured
as a bonus :)
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the bo
stream-fixes going to Linus then.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
e of the recent patches in
> for-4.6/upstream-fixes touches atkbd. I'd be very interested in which
> one exactly causes this.
Exactly, I don't see any possible relationship whatsoever.
Sedat, for-4.6/upstream-fixes branch has only a couple of commits, so it
should take just a very short while to b
he issue go away.
> > Unsure what is the cause.
>
> Hmm, this is quite curious, none of the recent patches in
> for-4.6/upstream-fixes touches atkbd. I'd be very interested in which
> one exactly causes this.
It's indeed odd.
Sedat, the kernel in question is compiled by gcc, rig
away.
Thanks for the useful report!
> Unsure what is the cause. On the way, try to look this evening or
> tommorrow into this.
I don't seem to see the beginning of this thread anywhere.
What hardware is this?
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
This patch clearly depends on some LED subsystem API that's not currently
merged. Please let me know once this changes so that we could proceed with
this patch.
I'm putting it on hold for now.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linu
nterrupt-IN endpoint is halted there's
> no need to submit the input URB until the halt has been
> cleared.
In addition to this being an actual fix, it's a nice cleanup as well.
Thanks a lot; queuing for 4.6.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send t
bandaids
being added to the generic code, I haven't been able to come up with
anything better.
So the aproach is fine with me ... perhaps a short comment before testing
HID_STARTED wouldn't hurt as well, as it has a potential of making code
reader's head spin.
Thanks,
--
Jiri Kosina
re, and we'll probably apply the quirk to all devices from these
guys that we identify to be of a keyboard type.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More
flags here at all.
On Mon, 7 Mar 2016, Sedat Dilek wrote:
> So, if Clang is producing wrong X86 code here, is it possible to turn
> interrupts on/off manually? But, hmm that affects other places as well
> in the Linux sources, so.
This issue needs to be handled in the c
July/088780.html
Seems like it has been reported already, but noone dared to fix it yet.
This basically makes LLVM unusable for compiling the kernel.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.
;
> might_sleep();
>
> local_irq_disable();
> pool = get_work_pool(work);
> if (!pool) {
> local_irq_enable();
> return false;
> }
>
> spin_lock(>lock); <--- XXX: spin_lock_irq() ???
No, this is fine. IR
> Also, I did create and test a patch to use HID_QUIRK_IGNORE which I can
> send if you feel strongly about it.
Applied to for-4.5/upstream-fixes.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to
B_DEVICE_ID_AKAI_MPKMINI2,
> HID_QUIRK_NO_INIT_REPORTS },
If the (proclaimed) HID device is completely silent, wouldn't
HID_QUIRK_IGNORE be more appropriate?
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sat, 23 Jan 2016, Raphael Assenat wrote:
> The correct product ID for the old version of the raphnet 4nes4snes
> device was 0x0a9d, not 0x0a8d.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the b
So if we do this in userspace, I think usb_modeswitch is not a bad choice.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
is to -stable. As you guys seem to be the ones
able to test it with your hardware, would you guys (Ioan-Adrian? Jason?)
be willing to prepare the backport and submit it once it passes your
testing?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscr
of(hid_dev->dev.parent->parent, struct usb_device, dev)
> + to_usb_device(hid_dev->dev.parent->parent)
Applied to hid.git#for-4.5/upstream.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
.com>
> Signed-off-by: Adrien Vergé <adrienve...@gmail.com>
Reviewed-by: Benjamin Tissoires <benjamin.tissoi...@redhat.com>
Reviewed-by: Jiri Kosina <jkos...@suse.cz>
Greg, I guess it makes sense to take both 1/2 and 2/2 together as a whole.
Would you mind adding the tag
usbhid state, calling hid_input_report()
> with the spinlock unlocked, allowing the device driver to grab the
> lock first, finish and then grab the lock afterwards in hid_ctrl().
>
> This patch implements the 2nd solution.
>
> Signed-off-by: Ioan-Adrian Ratiu <a...
; I'll continue to research this more in depth, but progress is slow
> because I don't have much time, I'm doing this in my spare time because
> it's my girlfriend's tablet.
Oh, now I understand the level of severity of this bug! :-)
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscr
understand the problem rather than papering it over
with more or less random fixes.
First, have you tried to run your usecase on your system with lockdep
enabled?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
you have already done the full analysis that shows that usbhid->lock is
indeed not needed, this absolutely needs to go into changelog as proper
justification.
Could you please reformulate the changelog in this respect and resubmit?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from
the lock
> after the hid_input_report() call and the deadlock dissapears.
I think the proper fix actually is to spin_lock_irqsave() in hid_ctrl(),
isn't it?
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message
into the kernel.
> [1] https://github.com/neoreeps/surface-pro-3/blob/master/wily_surface.patch
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Tue, 27 Oct 2015, savoca wrote:
> Adding support for device 0x07e8 (SP4 Type Cover)
>
> Signed-off-by: savoca <alex.de...@daqri.com>
Thanks for the patch.
The authorship and signoffs should same real names though. Could you
please resend with that fixed?
--
Jiri K
> + { USB_VENDOR_ID_XIN_MO, USB_DEVICE_ID_XIN_MO_DUAL_ARCADE,
> HID_QUIRK_NOGET | HID_QUIRK_MULTI_INPUT },
>
> { 0, 0 }
> };
> --
> 2.5.0
>
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
at every 'return -1' occurence in the kernel and
convert it to something else? That can keep you busy for quite some time:
$ git grep 'return -1' | wc -l
9167
The only cleanup I'd imagine at least remotely possible in this case would
be to convert the ->connect() callbac
com>
I've fixed up the formatting and applied to hid.git#for-4.3/upstream-fixes
(please note that this doesn't guarantee that this patch will not go to
4.3 still, because it alone is not going to be reason for pull request,
but might eventually piggy-back on something that'll be needed for 4
v->clamed flags accordingly.
Could you please be more specific about the -EPERM mapping you are talking
about?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More m
e getting confused again and
again nevertheless.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
t accurate would of
course be usbkbd-boot, but that might be equally confusing.
The drawback I can see in renaming the driver is various embedded folks
having he name hardcoded in their scripts.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe l
.
Signed-off-by: Don Zickus dzic...@redhat.com
---
I mistyped the usb mailing list address, so this patch never made it there.
Resending with the correct address. Sorry for the spam.
Hmm, good catch.
I've added Cc: stable and applied to for-4.3/upstream.
Thanks,
--
Jiri Kosina
SUSE Labs
.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Initramfs declares that :
most - Add most filesystem and all harddrive drivers
and it is a hardware driver, but not detected as such by initramfs
harddrive and hardware is not the same though.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb
/upstream, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
kernel a corded hid keyboard does work but this
specific keyboard does not work anymore.
The keybaord works fine after boot
Do you have the driver (hid-logitech-hidpp) present in the initrd? It
needs to be loaded at the time you are trying to use the keyboard.
--
Jiri Kosina
SUSE Labs
On Wed, 8 Jul 2015, Jiri Kosina wrote:
Bug as submitted on: https://bugzilla.kernel.org/show_bug.cgi?id=100631
Mailing it to this mailing list on advice of greg k-h
--
Cannot use the logitech
kernel can do about. I am not saying it
doesn't bring the LEDs up to a proper state again once auto-resumed. But I
hate the LEDs going off a few seconds after I stop typing (i.e. once the
keyboard gets auto-suspended).
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line
-suspended).
That is the point. Unless you give the option to override, they
shouldn't autosuspend.
Ah, you're right, I completely forgot about the logic we've put into
hidinput_count_leds() quite some time ago. Sorry for the noise,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send
this any more, I am afraid we'll have to move the default
into the kernel.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
patch hasn't been lost, it's still in my trivial-todo inbox, and will
eventually be processed.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org
/labq2/
and the LoggerPro for Linux software shown at
http://www.vernier.com/downloads/logger-pro-linux/.
Signed-off-by: Dennis O'Brien dennis.obr...@eqware.net
Acked-by: Greg Kroah-Hartman gre...@linuxfoundation.org
Applied to hid.git#for-4.2/upstream.
Thanks,
--
Jiri Kosina
SUSE Labs
,
HID_GROUP_LOGITECH_DJ_DEVICE,
:: The code at line 1504 was first introduced by commit
:: 3a61e97563d78a2ca10752902449570d8433ce76 HID: logitech-hidpp: support
combo keyboard touchpad TK820
:: TO: Benjamin Tissoires benjamin.tissoi...@redhat.com
:: CC: Jiri Kosina jkos...@suse.cz
Thanks
On Thu, 28 May 2015, Greg KH wrote:
On Thu, May 28, 2015 at 04:58:54PM +0200, Jiri Kosina wrote:
On Thu, 21 May 2015, Dennis O'Brien wrote:
From: Dennis O'Brien dennis.obr...@eqware.net
Removes Vernier Software Technology devices from the ldusb
driver and the hid_ignore_list
it himself through his tree).
Greg ... ?
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
(with Benjamin's nit taken into account). Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
,
HID_QUIRK_NO_INIT_REPORTS },
{ USB_VENDOR_ID_MSI, USB_DEVICE_ID_MSI_GT683R_LED_PANEL,
HID_QUIRK_NO_INIT_REPORTS },
{ USB_VENDOR_ID_NEXIO, USB_DEVICE_ID_NEXIO_MULTITOUCH_PTI0750,
HID_QUIRK_NO_INIT_REPORTS },
--
2.1.4
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line
device.
With this patch each controller gets its own /dev/input/jsX device,
which is more natural and less confusing than having all inputs going
to the same place.
Applied, thanks.
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body
a frequently re-appearing topic, we'll have to come up with more
generic aproach.
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line unsubscribe linux-usb in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo
, USB_DEVICE_ID_PRODIGE_CORDLESS,
HID_QUIRK_NOGET },
{ USB_VENDOR_ID_QUANTA, USB_DEVICE_ID_QUANTA_OPTICAL_TOUCH_3001,
HID_QUIRK_NOGET },
{ USB_VENDOR_ID_QUANTA, USB_DEVICE_ID_QUANTA_OPTICAL_TOUCH_3008,
HID_QUIRK_NOGET },
--
2.1.4
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from
,
HID_QUIRK_ALWAYS_POLL },
{ USB_VENDOR_ID_LOGITECH, USB_DEVICE_ID_LOGITECH_C077,
HID_QUIRK_ALWAYS_POLL },
{ USB_VENDOR_ID_MGE, USB_DEVICE_ID_MGE_UPS, HID_QUIRK_NOGET },
{ USB_VENDOR_ID_MICROSOFT, USB_DEVICE_ID_MS_TYPE_COVER_3,
HID_QUIRK_NO_INIT_REPORTS },
--
Jiri Kosina
SUSE Labs
1 - 100 of 210 matches
Mail list logo
