Re: PATCH: uep(4) support for (my) eGalax touchscreen

2017-07-24 Thread Anthony Jenkins via freebsd-usb
On 07/24/2017 03:28 PM, Anthony Jenkins via freebsd-usb wrote: > I'm trying to add support for uep(4) to detect and properly emit touch > events to x11-drivers/xf86-input-egalax. What I have works, but has some > issues, particularly: > > - close(2)ing the device node causes a USB_ST_ERROR in

Re: PATCH: uep(4) support for (my) eGalax touchscreen

2017-07-24 Thread Hans Petter Selasky
On 07/24/17 22:10, Anthony Jenkins via freebsd-usb wrote: On 07/24/2017 03:28 PM, Anthony Jenkins via freebsd-usb wrote: I'm trying to add support for uep(4) to detect and properly emit touch events to x11-drivers/xf86-input-egalax. What I have works, but has some issues, particularly: -

PATCH: uep(4) support for (my) eGalax touchscreen

2017-07-24 Thread Anthony Jenkins via freebsd-usb
I'm trying to add support for uep(4) to detect and properly emit touch events to x11-drivers/xf86-input-egalax. What I have works, but has some issues, particularly: - close(2)ing the device node causes a USB_ST_ERROR in the uep_intr_callback(); it's probably from my attempt to port an

GSoC Week 6-8, add usbdump file-format to Wireshark

2017-07-24 Thread Jie Weng
Hi everyone, I'm really sorry for the late status updates. In the first week I fixed several crashes when opening files in which the length of some packets is a little longer. It was caused by a wrongly explicit cast, the cast shorten the proper length it should be. Besides, I was diving into

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

2017-07-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852 --- Comment #9 from Bipin Chandra --- tried the patch but the behavior is still same -- You are receiving this mail because: You are the assignee for the bug. ___

[Bug 220852] [cdce] [usb] raspberry pi or anything that can emulate Ethernet gadget over usb mac id not read

2017-07-24 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=220852 --- Comment #10 from Bipin Chandra --- as per one of the members at pfsense i was told the below: "It still concerns me that the device created is cdce0 and not urndis0. It looks to me as though it's not even using the