[Bug 234578] Support for Sierra Wireless EM7455 modem

2021-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=234578 Aleks Michajlow changed: What|Removed |Added CC||a...@alexmihajlov.ru --- Comment

[Bug 256296] "No Device" error after using asynchronous API of libusb once

2021-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256296 Bug ID: 256296 Summary: "No Device" error after using asynchronous API of libusb once Product: Base System Version: Unspecified Hardware: Any OS: Any

[Bug 256296] "No Device" error after using asynchronous API of libusb once

2021-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256296 --- Comment #1 from Sergii --- Forgot to say that this happens on 12.2, but I don't think it has changed since. -- You are receiving this mail because: You are the assignee for the bug. ___ free

[Bug 256296] "No Device" error after using asynchronous API of libusb once

2021-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256296 Hans Petter Selasky changed: What|Removed |Added CC||hsela...@freebsd.org --- Com

[Bug 256296] "No Device" error after using asynchronous API of libusb once

2021-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256296 --- Comment #3 from Sergii --- Hi, I don't know what kind of event comes and might need to investigate callbacks more, but why mark device as gone in this case? It's not gone, it's just closed. -- You are receiving this mail because: You

[Bug 256296] "No Device" error after using asynchronous API of libusb once

2021-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256296 Tomasz "CeDeROM" CEDRO changed: What|Removed |Added CC||to...@cedro.info --- Comm

[Bug 256296] "No Device" error after using asynchronous API of libusb once

2021-05-31 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=256296 --- Comment #5 from Sergii --- Created attachment 225431 --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=225431&action=edit Bug reproducer > Sergii is it possible to open device again after closing? It should not be > possible t

Re: eGalax USB touchscreen issues

2021-05-31 Thread Vladimir Kondratyev
On 29.05.2021 23:27, Mark Kane wrote: > On 2021-05-28 05:37, Vladimir Kondratyev wrote: >> Yes, hpen(4) supports them. >> >> It is required to apply some quirks though as TouchScreen usage page >> is handled with hmt(4) driver by default. >> Try attached patch and don't forget to enable usbhid(4) t