Re: webcamd based touchscreen problem on Pi3

2018-03-26 Thread Bernd Walter 
On Mon, Mar 26, 2018 at 01:28:06AM +0200, Bernd Walter wrote:
> I somehow suspect that the device is dropping data, when the driver isn't
> retrieving it fast enough.
> I can't say for sure however, because usbdump has more interupt packets than
> there is events on the /dev/input , although X and Y coordinates come in the
> same packet.
> But I couldn't isolate the button packets yet.

The 10" (not the early model I had before) is working fine now using wmt(4).
I'd tested with wmt(4) before, but it failed.
Interestingly xf86-input-mouse via usbhidlib did work with mouse emulation on
the 7", which the 10" doesn't have, but the emulation of the device was bad
and in touch mode X crashed on both displays during device init.
uep(4) doesn't work at all, it is for a completely different protocol used on
some older eGalax devices - obviously some with resistive touch, but not sure.
Similar the egalax_ts.c in webcamd is only for the older eGalax devices.
Have to see why wmt(4) doesn't like the older devices, maybe this can be fixed.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-25 Thread Bernd Walter 
On Mon, Mar 26, 2018 at 01:11:28AM +0200, Bernd Walter wrote:
> On Mon, Mar 12, 2018 at 12:12:47PM +0100, Bernd Walter wrote:
> > On Sat, Mar 10, 2018 at 01:03:39AM +0100, Bernd Walter wrote:
> > > On Fri, Mar 09, 2018 at 02:25:39PM +0100, Bernd Walter wrote:
> > > So the older 7" HDMI C Rev 1.1 with the non IPS panel won't even attach, 
> > > but
> > > it always needed some special binary support for Linux, no surprises here.
> > > The newer Rev 2.1 with the IPS panel claims to be the same and work with
> > > webcamd, at least I get data via /dev/input/event0, which looks reasonable
> > > with evdev-dump.
> > > That's an interesting starting point.
> > 
> > I've got a new model of the 10" HDMI B.
> > It behaves differently.
> > First of all - uep seems to take it, which it didn't for any of
> > the previous displays I'd tested.
> > I had to remove the driver from the loader.conf to have webcamd attach to 
> > it.
> > webcamd attaches fine and it delivers touch events:
> > [29]sa# evdev-dump /dev/input/event0
> > /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_TRACKING_ID 0x
> > /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_POSITION_X 0x01CF
> > /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_POSITION_Y 0x025E
> > /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_PRESSURE 0x0005
> > /dev/input/event0  3041705595.425438 EV_KEY BTN_TOUCH 0x0001
> > /dev/input/event0  3041705595.425438 EV_ABS ABS_X 0x01CF
> > /dev/input/event0  3041705595.425438 EV_ABS ABS_Y 0x025E
> > /dev/input/event0  3041705595.425438 EV_ABS ABS_PRESSURE 0x0005
> > /dev/input/event0  3041705595.425438 EV_SYN SYN_REPORT 0x
> > 
> > Whatever had been the cause for my previous problem, they obviously
> > have fixed them in firmware.
> 
> Unfortunately I still have some problems.
> [63]sa# evdev-dump /dev/input/event1
> /dev/input/event1  3043946310.664423 EV_ABS ABS_MT_TRACKING_ID 0x003F
> /dev/input/event1  3043946310.664423 EV_ABS ABS_MT_POSITION_X 0x01C9
> /dev/input/event1  3043946310.664423 EV_ABS ABS_MT_POSITION_Y 0x0112
> /dev/input/event1  3043946310.664423 EV_KEY BTN_TOUCH 0x0001
> /dev/input/event1  3043946310.664423 EV_ABS ABS_X 0x01C9
> /dev/input/event1  3043946310.664423 EV_ABS ABS_Y 0x0112
> /dev/input/event1  3043946310.664423 EV_SYN SYN_REPORT 0x
> /dev/input/event1  3043946310.784395 EV_ABS ABS_MT_TRACKING_ID 0x
> /dev/input/event1  3043946310.784395 EV_KEY BTN_TOUCH 0x
> /dev/input/event1  3043946310.784395 EV_SYN SYN_REPORT 0x
> 
> 
> 
> 
> /dev/input/event1  3043946316.944324 EV_ABS ABS_MT_TRACKING_ID 0x0040
> /dev/input/event1  3043946316.944324 EV_ABS ABS_MT_POSITION_X 0x01CE
> /dev/input/event1  3043946316.944324 EV_ABS ABS_MT_POSITION_Y 0x00FE
> /dev/input/event1  3043946316.944324 EV_KEY BTN_TOUCH 0x0001
> /dev/input/event1  3043946316.944324 EV_ABS ABS_X 0x01CE
> /dev/input/event1  3043946316.944324 EV_ABS ABS_Y 0x00FE
> /dev/input/event1  3043946316.944324 EV_SYN SYN_REPORT 0x
> /dev/input/event1  3043946317.004303 EV_ABS ABS_MT_TRACKING_ID 0x
> /dev/input/event1  3043946317.004303 EV_KEY BTN_TOUCH 0x
> /dev/input/event1  3043946317.004303 EV_SYN SYN_REPORT 0x
> 
> 
> 
> /dev/input/event1  3043946319.744283 EV_ABS ABS_MT_TRACKING_ID 0x0041
> /dev/input/event1  3043946319.744283 EV_ABS ABS_MT_POSITION_X 0x020E
> /dev/input/event1  3043946319.744283 EV_ABS ABS_MT_POSITION_Y 0x00D8
> /dev/input/event1  3043946319.744283 EV_KEY BTN_TOUCH 0x0001
> /dev/input/event1  3043946319.744283 EV_ABS ABS_X 0x020E
> /dev/input/event1  3043946319.744283 EV_ABS ABS_Y 0x00D8
> /dev/input/event1  3043946319.744283 EV_SYN SYN_REPORT 0x
> /dev/input/event1  3043946319.864240 EV_ABS ABS_MT_TRACKING_ID 0x
> /dev/input/event1  3043946319.864240 EV_KEY BTN_TOUCH 0x
> /dev/input/event1  3043946319.864240 EV_SYN SYN_REPORT 0x
> 
> 
> 
> /dev/input/event1  3043946322.004229 EV_ABS ABS_MT_TRACKING_ID 0x0042
> /dev/input/event1  3043946322.004229 EV_ABS ABS_MT_POSITION_X 0x0209
> /dev/input/event1  3043946322.004229 EV_ABS ABS_MT_POSITION_Y 0x00CD
> /dev/input/event1  3043946322.004229 EV_KEY BTN_TOUCH 0x0001
> /dev/input/event1  3043946322.004229 EV_ABS ABS_X 0x0209
> /dev/input/event1  3043946322.004229 EV_ABS ABS_Y 0x00CD
> /dev/input/event1  3043946322.004229 EV_SYN SYN_REPORT 0x
> 
> 
> 
> 
> /dev/input/event1  3043946325.454187 EV_ABS ABS_MT_POSITION_X 0x016A
> /dev/input/event1  3043946325.454187 EV_ABS ABS_MT_POSITION_Y 0x00D2
> /dev/input/event1  3043946325.454187 EV_ABS ABS_X 0x016A
> /dev/input/event1  3043946325.454187 EV_ABS ABS_Y 0x00D2
> /dev/input/event1  3043946325.454187 EV_SYN SYN_REPORT 0x
> /dev/input/event1  3043946325.574174 EV_ABS ABS_MT_POSITION_X 0x016B
> /dev/input/event1  3043946325.574174 EV_ABS ABS_X 0x016B
> /dev/input/event1

Re: webcamd based touchscreen problem on Pi3

2018-03-25 Thread Bernd Walter 
On Mon, Mar 12, 2018 at 12:12:47PM +0100, Bernd Walter wrote:
> On Sat, Mar 10, 2018 at 01:03:39AM +0100, Bernd Walter wrote:
> > On Fri, Mar 09, 2018 at 02:25:39PM +0100, Bernd Walter wrote:
> > So the older 7" HDMI C Rev 1.1 with the non IPS panel won't even attach, but
> > it always needed some special binary support for Linux, no surprises here.
> > The newer Rev 2.1 with the IPS panel claims to be the same and work with
> > webcamd, at least I get data via /dev/input/event0, which looks reasonable
> > with evdev-dump.
> > That's an interesting starting point.
> 
> I've got a new model of the 10" HDMI B.
> It behaves differently.
> First of all - uep seems to take it, which it didn't for any of
> the previous displays I'd tested.
> I had to remove the driver from the loader.conf to have webcamd attach to it.
> webcamd attaches fine and it delivers touch events:
> [29]sa# evdev-dump /dev/input/event0
> /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_TRACKING_ID 0x
> /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_POSITION_X 0x01CF
> /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_POSITION_Y 0x025E
> /dev/input/event0  3041705595.425438 EV_ABS ABS_MT_PRESSURE 0x0005
> /dev/input/event0  3041705595.425438 EV_KEY BTN_TOUCH 0x0001
> /dev/input/event0  3041705595.425438 EV_ABS ABS_X 0x01CF
> /dev/input/event0  3041705595.425438 EV_ABS ABS_Y 0x025E
> /dev/input/event0  3041705595.425438 EV_ABS ABS_PRESSURE 0x0005
> /dev/input/event0  3041705595.425438 EV_SYN SYN_REPORT 0x
> 
> Whatever had been the cause for my previous problem, they obviously
> have fixed them in firmware.

Unfortunately I still have some problems.
[63]sa# evdev-dump /dev/input/event1
/dev/input/event1  3043946310.664423 EV_ABS ABS_MT_TRACKING_ID 0x003F
/dev/input/event1  3043946310.664423 EV_ABS ABS_MT_POSITION_X 0x01C9
/dev/input/event1  3043946310.664423 EV_ABS ABS_MT_POSITION_Y 0x0112
/dev/input/event1  3043946310.664423 EV_KEY BTN_TOUCH 0x0001
/dev/input/event1  3043946310.664423 EV_ABS ABS_X 0x01C9
/dev/input/event1  3043946310.664423 EV_ABS ABS_Y 0x0112
/dev/input/event1  3043946310.664423 EV_SYN SYN_REPORT 0x
/dev/input/event1  3043946310.784395 EV_ABS ABS_MT_TRACKING_ID 0x
/dev/input/event1  3043946310.784395 EV_KEY BTN_TOUCH 0x
/dev/input/event1  3043946310.784395 EV_SYN SYN_REPORT 0x




/dev/input/event1  3043946316.944324 EV_ABS ABS_MT_TRACKING_ID 0x0040
/dev/input/event1  3043946316.944324 EV_ABS ABS_MT_POSITION_X 0x01CE
/dev/input/event1  3043946316.944324 EV_ABS ABS_MT_POSITION_Y 0x00FE
/dev/input/event1  3043946316.944324 EV_KEY BTN_TOUCH 0x0001
/dev/input/event1  3043946316.944324 EV_ABS ABS_X 0x01CE
/dev/input/event1  3043946316.944324 EV_ABS ABS_Y 0x00FE
/dev/input/event1  3043946316.944324 EV_SYN SYN_REPORT 0x
/dev/input/event1  3043946317.004303 EV_ABS ABS_MT_TRACKING_ID 0x
/dev/input/event1  3043946317.004303 EV_KEY BTN_TOUCH 0x
/dev/input/event1  3043946317.004303 EV_SYN SYN_REPORT 0x



/dev/input/event1  3043946319.744283 EV_ABS ABS_MT_TRACKING_ID 0x0041
/dev/input/event1  3043946319.744283 EV_ABS ABS_MT_POSITION_X 0x020E
/dev/input/event1  3043946319.744283 EV_ABS ABS_MT_POSITION_Y 0x00D8
/dev/input/event1  3043946319.744283 EV_KEY BTN_TOUCH 0x0001
/dev/input/event1  3043946319.744283 EV_ABS ABS_X 0x020E
/dev/input/event1  3043946319.744283 EV_ABS ABS_Y 0x00D8
/dev/input/event1  3043946319.744283 EV_SYN SYN_REPORT 0x
/dev/input/event1  3043946319.864240 EV_ABS ABS_MT_TRACKING_ID 0x
/dev/input/event1  3043946319.864240 EV_KEY BTN_TOUCH 0x
/dev/input/event1  3043946319.864240 EV_SYN SYN_REPORT 0x



/dev/input/event1  3043946322.004229 EV_ABS ABS_MT_TRACKING_ID 0x0042
/dev/input/event1  3043946322.004229 EV_ABS ABS_MT_POSITION_X 0x0209
/dev/input/event1  3043946322.004229 EV_ABS ABS_MT_POSITION_Y 0x00CD
/dev/input/event1  3043946322.004229 EV_KEY BTN_TOUCH 0x0001
/dev/input/event1  3043946322.004229 EV_ABS ABS_X 0x0209
/dev/input/event1  3043946322.004229 EV_ABS ABS_Y 0x00CD
/dev/input/event1  3043946322.004229 EV_SYN SYN_REPORT 0x




/dev/input/event1  3043946325.454187 EV_ABS ABS_MT_POSITION_X 0x016A
/dev/input/event1  3043946325.454187 EV_ABS ABS_MT_POSITION_Y 0x00D2
/dev/input/event1  3043946325.454187 EV_ABS ABS_X 0x016A
/dev/input/event1  3043946325.454187 EV_ABS ABS_Y 0x00D2
/dev/input/event1  3043946325.454187 EV_SYN SYN_REPORT 0x
/dev/input/event1  3043946325.574174 EV_ABS ABS_MT_POSITION_X 0x016B
/dev/input/event1  3043946325.574174 EV_ABS ABS_X 0x016B
/dev/input/event1  3043946325.574174 EV_SYN SYN_REPORT 0x

All 5 blocks are a single touch, which means finger on screen for a short
moment.
On the first 3 I get position data and BTN_TOUCH 1 as well as BTN_TOUCH 0.
But this is not consistent, sometime I get only a 1

Re: webcamd based touchscreen problem on Pi3

2018-03-12 Thread Bernd Walter 
On Sat, Mar 10, 2018 at 01:03:39AM +0100, Bernd Walter wrote:
> On Fri, Mar 09, 2018 at 02:25:39PM +0100, Bernd Walter wrote:
> > On Fri, Mar 09, 2018 at 01:19:54PM +0100, Hans Petter Selasky wrote:
> > > On 03/09/18 12:40, Bernd Walter wrote:
> > > >Will do the quirk test later.
> > > 
> > > I don't see any stalls during plug-in, so it might be a request webcamd 
> > > issues, which the device doesn't support. Try building webcamd with 
> > > debug support.
> > 
> > It is already build with debug.
> > But I don't see anything of special interest in the output.
> > 
> > [24]sa# webcamd -d ugen0.4
> > Linux video capture interface: v2.00
> > IR NEC protocol handler initialized
> > IR RC5(x/sz) protocol handler initialized
> > IR RC6 protocol handler initialized
> > IR JVC protocol handler initialized
> > IR Sony protocol handler initialized
> > IR SANYO protocol handler initialized
> > IR LIRC bridge handler initialized
> > IR XMP protocol handler initialized
> > b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded 
> > successfully
> > USB Video Class driver (1.1.1)
> > cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
> > pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
> > pvrusb2: Debug mask is 31 (0x1f)
> > USBVision USB Video Device Driver for Linux : 0.9.11
> > Attached to ugen0.4[0]
> > INFO: 0003:0EEF:0005.0001: input: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] 
> > on usb-/dev/usb-/dev/usb/input0
> > 
> > DBG: 0003:0EEF:0005.0001: Kicking head 1 tail 0
> > Creating /dev/input/event0
> > 
> > I will redo a test with raspbian.
> > Waveshare delivered a binary kernel (so much about GPL) for their 7" HDMI C
> > until they changed something in the device firmware and upgraded for a newer
> > panel about 2-3 years ago.
> > This is the 10.1" HMDI B and it is a very early version I have, which 
> > however
> > should use a firmware similar to the newer 7" HDMI C.
> > I will retest with a stock Raspbian image to be sure I wasn't accidently
> > using a Waveshare image back then.
> > As far as I can see the Linux drivers just quirk the device to the egalaxy
> > driver, so they do know the Waveshare by ID.
> > I couldn't spot a difference between Linux and what is included in the 
> > webcamd
> > source.
> 
> So the older 7" HDMI C Rev 1.1 with the non IPS panel won't even attach, but
> it always needed some special binary support for Linux, no surprises here.
> The newer Rev 2.1 with the IPS panel claims to be the same and work with
> webcamd, at least I get data via /dev/input/event0, which looks reasonable
> with evdev-dump.
> That's an interesting starting point.

I've got a new model of the 10" HDMI B.
It behaves differently.
First of all - uep seems to take it, which it didn't for any of
the previous displays I'd tested.
I had to remove the driver from the loader.conf to have webcamd attach to it.
webcamd attaches fine and it delivers touch events:
[29]sa# evdev-dump /dev/input/event0
/dev/input/event0  3041705595.425438 EV_ABS ABS_MT_TRACKING_ID 0x
/dev/input/event0  3041705595.425438 EV_ABS ABS_MT_POSITION_X 0x01CF
/dev/input/event0  3041705595.425438 EV_ABS ABS_MT_POSITION_Y 0x025E
/dev/input/event0  3041705595.425438 EV_ABS ABS_MT_PRESSURE 0x0005
/dev/input/event0  3041705595.425438 EV_KEY BTN_TOUCH 0x0001
/dev/input/event0  3041705595.425438 EV_ABS ABS_X 0x01CF
/dev/input/event0  3041705595.425438 EV_ABS ABS_Y 0x025E
/dev/input/event0  3041705595.425438 EV_ABS ABS_PRESSURE 0x0005
/dev/input/event0  3041705595.425438 EV_SYN SYN_REPORT 0x

Whatever had been the cause for my previous problem, they obviously
have fixed them in firmware.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-09 Thread Bernd Walter 
On Fri, Mar 09, 2018 at 02:25:39PM +0100, Bernd Walter wrote:
> On Fri, Mar 09, 2018 at 01:19:54PM +0100, Hans Petter Selasky wrote:
> > On 03/09/18 12:40, Bernd Walter wrote:
> > >Will do the quirk test later.
> > 
> > I don't see any stalls during plug-in, so it might be a request webcamd 
> > issues, which the device doesn't support. Try building webcamd with 
> > debug support.
> 
> It is already build with debug.
> But I don't see anything of special interest in the output.
> 
> [24]sa# webcamd -d ugen0.4
> Linux video capture interface: v2.00
> IR NEC protocol handler initialized
> IR RC5(x/sz) protocol handler initialized
> IR RC6 protocol handler initialized
> IR JVC protocol handler initialized
> IR Sony protocol handler initialized
> IR SANYO protocol handler initialized
> IR LIRC bridge handler initialized
> IR XMP protocol handler initialized
> b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded 
> successfully
> USB Video Class driver (1.1.1)
> cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
> pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
> pvrusb2: Debug mask is 31 (0x1f)
> USBVision USB Video Device Driver for Linux : 0.9.11
> Attached to ugen0.4[0]
> INFO: 0003:0EEF:0005.0001: input: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on 
> usb-/dev/usb-/dev/usb/input0
> 
> DBG: 0003:0EEF:0005.0001: Kicking head 1 tail 0
> Creating /dev/input/event0
> 
> I will redo a test with raspbian.
> Waveshare delivered a binary kernel (so much about GPL) for their 7" HDMI C
> until they changed something in the device firmware and upgraded for a newer
> panel about 2-3 years ago.
> This is the 10.1" HMDI B and it is a very early version I have, which however
> should use a firmware similar to the newer 7" HDMI C.
> I will retest with a stock Raspbian image to be sure I wasn't accidently
> using a Waveshare image back then.
> As far as I can see the Linux drivers just quirk the device to the egalaxy
> driver, so they do know the Waveshare by ID.
> I couldn't spot a difference between Linux and what is included in the webcamd
> source.

So the older 7" HDMI C Rev 1.1 with the non IPS panel won't even attach, but
it always needed some special binary support for Linux, no surprises here.
The newer Rev 2.1 with the IPS panel claims to be the same and work with
webcamd, at least I get data via /dev/input/event0, which looks reasonable
with evdev-dump.
That's an interesting starting point.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-09 Thread Bernd Walter 
On Fri, Mar 09, 2018 at 01:19:54PM +0100, Hans Petter Selasky wrote:
> On 03/09/18 12:40, Bernd Walter wrote:
> >Will do the quirk test later.
> 
> I don't see any stalls during plug-in, so it might be a request webcamd 
> issues, which the device doesn't support. Try building webcamd with 
> debug support.

It is already build with debug.
But I don't see anything of special interest in the output.

[24]sa# webcamd -d ugen0.4
Linux video capture interface: v2.00
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR LIRC bridge handler initialized
IR XMP protocol handler initialized
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded 
successfully
USB Video Class driver (1.1.1)
cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
pvrusb2: Debug mask is 31 (0x1f)
USBVision USB Video Device Driver for Linux : 0.9.11
Attached to ugen0.4[0]
INFO: 0003:0EEF:0005.0001: input: USB HID v1.10 Mouse [BYZHYYZHY By ZH851] on 
usb-/dev/usb-/dev/usb/input0

DBG: 0003:0EEF:0005.0001: Kicking head 1 tail 0
Creating /dev/input/event0

I will redo a test with raspbian.
Waveshare delivered a binary kernel (so much about GPL) for their 7" HDMI C
until they changed something in the device firmware and upgraded for a newer
panel about 2-3 years ago.
This is the 10.1" HMDI B and it is a very early version I have, which however
should use a firmware similar to the newer 7" HDMI C.
I will retest with a stock Raspbian image to be sure I wasn't accidently
using a Waveshare image back then.
As far as I can see the Linux drivers just quirk the device to the egalaxy
driver, so they do know the Waveshare by ID.
I couldn't spot a difference between Linux and what is included in the webcamd
source.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-09 Thread Hans Petter Selasky 

On 03/09/18 12:40, Bernd Walter wrote:

Will do the quirk test later.


I don't see any stalls during plug-in, so it might be a request webcamd 
issues, which the device doesn't support. Try building webcamd with 
debug support.


--HPS
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-09 Thread Bernd Walter 
On Fri, Mar 09, 2018 at 09:19:11AM +0100, Roberto Fernandez Cueto wrote:
> Roberto Fernandez-Cueto schrieb am 09.03.2018 09:19
> _
> 
> I do not if this helps, but what I usually do when I get to work with a
> new touchscreen is to see if FreeBSD detects it as UHID.

I hadn't loaded uhid, but it detects the device.

> If it is recognized, then I check if the touchscreen send absolute
> coordinates or relative coordinates.
> 
> You can do it with usbhidctl(1). See the collection, items and get the
> values parsed by the HID layer.

Well, this has to wait until I found time to read more about it.
HID is something I've always hated and never really spend much time into.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-09 Thread Bernd Walter 
On Fri, Mar 09, 2018 at 09:40:00AM +0100, Hans Petter Selasky wrote:
> On 03/09/18 01:44, Bernd Walter wrote:
> >On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote:
> >>You can try running usbdump to capture USB packets.
> >>
> >>ktrace is also your friend.
> >>
> >>dd if=/dev/input/event0 bs=1
> >>
> >>Also check ownership of devices, that X.org can read from them.
> >
> 
> Can you try connecting the device through an external USB HUB?

This test has to wait for me to change the setup

> Can you capture the whole enumeration sequence. Can you also try setting 
> the UQ_NO_STRINGS quirk using usbconfig for this device and re-plug it?

This is on plug in:
[25]sa# usbdump -v -v -v -v -f 4
11:36:27.190408 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   00 05 04 00 00 00 00 00  -- -- -- -- -- -- -- --  ||
 flags 0x50 
 status 0xc03a3 

11:36:27.191546 usbus0.4 
DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 flags 0x50 
 status 0xc03a1 

11:36:27.191568 usbus0.4 SUBM-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0
 frame[0] WRITE 0 bytes
 flags 0x10 
 status 0xc00a3 

11:36:27.192542 usbus0.4 
DONE-CTRL-EP=,SPD=FULL,NFR=1,SLEN=0,IVAL=0,ERR=0
 frame[0] WRITE 0 bytes
 flags 0x10 
 status 0xc00a1 
11:36:27.203447 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 01 00 00 08 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 8 bytes
 flags 0x10 
 status 0xc01a3 

11:36:27.206539 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 8 bytes
   12 01 00 02 00 00 00 40  -- -- -- -- -- -- -- --  |...@|
 flags 0x10 
 status 0xc01a1 

11:36:27.206618 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 01 00 00 12 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 18 bytes
 flags 0x10 
 status 0xc01a3 

11:36:27.209538 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 18 bytes
   12 01 00 02 00 00 00 40  EF 0E 05 00 00 02 01 02  |...@|
 0010  03 01 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |..  |
 flags 0x10 
 status 0xc01a1 

11:36:27.209578 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 02 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 2 bytes
 flags 0x10 
 status 0xc01a3 

11:36:27.212537 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 2 bytes
   04 03 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |..  |
 flags 0x10 
 status 0xc01a1 

11:36:27.212559 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
 flags 0x10 
 status 0xc01a3 

11:36:27.215537 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
 flags 0x10 
 status 0xc01a1 

11:36:27.215561 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 03 03 09 04 02 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 2 bytes
 flags 0x10 
 status 0xc01a3 

11:36:27.218536 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 2 bytes
   1A 03 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |..  |
 flags 0x10

Re: webcamd based touchscreen problem on Pi3

2018-03-09 Thread Roberto Fernandez Cueto 
Roberto Fernandez-Cueto schrieb am 09.03.2018 09:19
_

I do not if this helps, but what I usually do when I get to work with a
new touchscreen is to see if FreeBSD detects it as UHID.

If it is recognized, then I check if the touchscreen send absolute
coordinates or relative coordinates.

You can do it with usbhidctl(1). See the collection, items and get the
values parsed by the HID layer.

If it helps, let me know.

Roberto Fernandez Cueto

On Fri, Mar 09, 2018 at 01:44:34AM +0100, Bernd Walter wrote:
> On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote:
> > You can try running usbdump to capture USB packets.
> > 
> > ktrace is also your friend.
> > 
> > dd if=/dev/input/event0 bs=1
> > 
> > Also check ownership of devices, that X.org can read from them.
> 
> It happens earlier, /dev/input/event0 delivers nothing at all.
> But usbdump is interesting.
> I've booted with webcamd disabled, started usbdump and started webcamd.
> 
> This is what I get:
> [22]sa# usbdump -v -f 4
> 00:30:09.379930 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 4 bytes
> 00:30:09.382401 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 4 bytes
>    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
> 00:30:09.382448 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 4 bytes
> 00:30:09.385398 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 4 bytes
>    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
> 00:30:09.385439 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 02 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 4 bytes
> 00:30:09.388398 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 4 bytes
>    12 03 42 00 -- -- -- --  -- -- -- -- -- -- -- --  |..B.|
> 00:30:09.388434 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 02 03 09 04 12 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 18 bytes
> 00:30:09.391399 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 18 bytes
>    12 03 42 00 79 00 20 00  5A 00 48 00 38 00 35 00  |..B.y. .Z.H.8.5.|
>  0010  31 00 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |1.  |
> 00:30:09.391474 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 4 bytes
> 00:30:09.394398 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 4 bytes
>    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
> 00:30:09.394435 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 4 bytes
> 00:30:09.397398 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 4 bytes
>    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
> 00:30:09.397436 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 01 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 4 bytes
> 00:30:09.400398 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 4 bytes
>    14 03 42 00 -- -- -- --  -- -- -- -- -- -- -- --  |..B.|
> 00:30:09.400433 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 01 03 09 04 14 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 20 bytes
> 00:30:09.403398 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 20 bytes
>     14 03 42 00 59 00 5A 00  48 00 59 00 59 00 5A 00  |..B.Y.Z.H.Y.Y.Z.|
>  0010  48 00 59 00 -- -- -- --  -- -- -- -- -- -- -- --  |H.Y.|
> 00:30:09.403440 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
>  frame[0] WRITE 8 bytes
>    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
>  frame[1] READ 4 bytes
> 00:30:09.406398 usbus0.4 
> DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
>  frame[0] WRITE 8 bytes
>  frame[1] READ 4 bytes
>    04 03 09 04 -- -- -- --

Re: webcamd based touchscreen problem on Pi3

2018-03-09 Thread Hans Petter Selasky 

On 03/09/18 01:44, Bernd Walter wrote:

On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote:

You can try running usbdump to capture USB packets.

ktrace is also your friend.

dd if=/dev/input/event0 bs=1

Also check ownership of devices, that X.org can read from them.


It happens earlier, /dev/input/event0 delivers nothing at all.
But usbdump is interesting.
I've booted with webcamd disabled, started usbdump and started webcamd.

This is what I get:
[22]sa# usbdump -v -f 4
00:30:09.379930 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.382401 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.382448 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.385398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.385439 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 02 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.388398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    12 03 42 00 -- -- -- --  -- -- -- -- -- -- -- --  |..B.|
00:30:09.388434 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 02 03 09 04 12 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 18 bytes
00:30:09.391399 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 18 bytes
    12 03 42 00 79 00 20 00  5A 00 48 00 38 00 35 00  |..B.y. .Z.H.8.5.|
  0010  31 00 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |1.  |
00:30:09.391474 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.394398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.394435 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.397398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.397436 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 01 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.400398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    14 03 42 00 -- -- -- --  -- -- -- -- -- -- -- --  |..B.|
00:30:09.400433 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 01 03 09 04 14 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 20 bytes
00:30:09.403398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 20 bytes
     14 03 42 00 59 00 5A 00  48 00 59 00 59 00 5A 00  |..B.Y.Z.H.Y.Y.Z.|
  0010  48 00 59 00 -- -- -- --  -- -- -- -- -- -- -- --  |H.Y.|
00:30:09.403440 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.406398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.406437 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.409397 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
  frame[0] WRITE 8 bytes
  frame[1] READ 4 bytes
    04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.409434 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
  frame[0] WRITE 8 bytes
    80 06 03 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
  frame[1] READ 4 bytes
00:30:09.412398 usbus0.4

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Bernd Walter 
On Thu, Mar 08, 2018 at 10:10:47PM +0100, Hans Petter Selasky wrote:
> You can try running usbdump to capture USB packets.
> 
> ktrace is also your friend.
> 
> dd if=/dev/input/event0 bs=1
> 
> Also check ownership of devices, that X.org can read from them.

It happens earlier, /dev/input/event0 delivers nothing at all.
But usbdump is interesting.
I've booted with webcamd disabled, started usbdump and started webcamd.

This is what I get:
[22]sa# usbdump -v -f 4
00:30:09.379930 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.382401 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.382448 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.385398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.385439 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 02 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.388398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   12 03 42 00 -- -- -- --  -- -- -- -- -- -- -- --  |..B.|
00:30:09.388434 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 02 03 09 04 12 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 18 bytes
00:30:09.391399 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 18 bytes
   12 03 42 00 79 00 20 00  5A 00 48 00 38 00 35 00  |..B.y. .Z.H.8.5.|
 0010  31 00 -- -- -- -- -- --  -- -- -- -- -- -- -- --  |1.  |
00:30:09.391474 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.394398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.394435 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.397398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.397436 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 01 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.400398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   14 03 42 00 -- -- -- --  -- -- -- -- -- -- -- --  |..B.|
00:30:09.400433 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 01 03 09 04 14 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 20 bytes
00:30:09.403398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=20,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 20 bytes
    14 03 42 00 59 00 5A 00  48 00 59 00 59 00 5A 00  |..B.Y.Z.H.Y.Y.Z.|
 0010  48 00 59 00 -- -- -- --  -- -- -- -- -- -- -- --  |H.Y.|
00:30:09.403440 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.406398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.406437 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 00 03 00 00 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.409397 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ 4 bytes
   04 03 09 04 -- -- -- --  -- -- -- -- -- -- -- --  ||
00:30:09.409434 usbus0.4 SUBM-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=8,IVAL=0
 frame[0] WRITE 8 bytes
   80 06 03 03 09 04 04 00  -- -- -- -- -- -- -- --  ||
 frame[1] READ 4 bytes
00:30:09.412398 usbus0.4 
DONE-CTRL-EP=0080,SPD=FULL,NFR=2,SLEN=4,IVAL=0,ERR=0
 frame[0] WRITE 8 bytes
 frame[1] READ

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Bernd Walter 
On Thu, Mar 08, 2018 at 02:41:50PM -0800, Oleksandr Tymoshenko wrote:
> Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote:
> > > Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > > > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote:
> > > > > Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > > > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> > > > > > https://github.com/gonzoua/evdev-dump/tree/freebsd
> > > > > > ...
> > > > > > checking for unistd.h... yes
> > > > > > checking linux/input.h usability... no
> > > > > > checking linux/input.h presence... no
> > > > > > checking for linux/input.h... no
> > > > > > checking for /usr/include/linux/input.h... no
> > > > > > configure: error: /usr/include/linux/input.h not found
> > > > > > 4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
> > > > > > Exit 1
> > > > > 
> > > > > I've just checked, evdev-dump should be buildable:
> > > > > 
> > > > > git clone g...@github.com:gonzoua/evdev-dump.git
> > > > > cd evdev-dump
> > > > > git checkout freebsd
> > > > > sudo pkg install gawk gmake
> > > > > sh bootstrap
> > > > > ./configure
> > > > > gmake
> > > > 
> > > > That's exactly how I did.
> > > > Well - I've used git clone https://github.com/gonzoua/evdev-dump.git
> > > > Even with a fresh clone it failed at the same file.
> > > > 
> > > > I have the following:
> > > > /usr/include/dev/evdev/input.h
> > > > /usr/local/include/linux/input.h
> > > > /usr/local/include/xorg/input.h
> > > 
> > > Could you show output of "git branch" and
> > > "grep -rl /usr/include/linux/input.h ." in cloned directory?
> > 
> > [55]sa# git branch
> > * master
> > [56]sa# grep -rl /usr/include/linux/input.h .
> > ./configure.ac
> > ./autom4te.cache/output.0
> > ./autom4te.cache/output.1
> > ./configure
> > ./config.log
> 
> You need freebsd branch. master branch is unmodified
> version of upstream, all my changes are on freebsd branch.

Lol - that makes sense.

Ok - it works, but I get nothing from my display, which this is more or
less already expected.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Oleksandr Tymoshenko 
Bernd Walter (ti...@cicely7.cicely.de) wrote:
> On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote:
> > Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote:
> > > > Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> > > > > https://github.com/gonzoua/evdev-dump/tree/freebsd
> > > > > ...
> > > > > checking for unistd.h... yes
> > > > > checking linux/input.h usability... no
> > > > > checking linux/input.h presence... no
> > > > > checking for linux/input.h... no
> > > > > checking for /usr/include/linux/input.h... no
> > > > > configure: error: /usr/include/linux/input.h not found
> > > > > 4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
> > > > > Exit 1
> > > > 
> > > > I've just checked, evdev-dump should be buildable:
> > > > 
> > > > git clone g...@github.com:gonzoua/evdev-dump.git
> > > > cd evdev-dump
> > > > git checkout freebsd
> > > > sudo pkg install gawk gmake
> > > > sh bootstrap
> > > > ./configure
> > > > gmake
> > > 
> > > That's exactly how I did.
> > > Well - I've used git clone https://github.com/gonzoua/evdev-dump.git
> > > Even with a fresh clone it failed at the same file.
> > > 
> > > I have the following:
> > > /usr/include/dev/evdev/input.h
> > > /usr/local/include/linux/input.h
> > > /usr/local/include/xorg/input.h
> > 
> > Could you show output of "git branch" and
> > "grep -rl /usr/include/linux/input.h ." in cloned directory?
> 
> [55]sa# git branch
> * master
> [56]sa# grep -rl /usr/include/linux/input.h .
> ./configure.ac
> ./autom4te.cache/output.0
> ./autom4te.cache/output.1
> ./configure
> ./config.log

You need freebsd branch. master branch is unmodified
version of upstream, all my changes are on freebsd branch.

Run:

gmake clean
git checkout freebsd <- this step is important
sh bootstrap
./configure
gmake

Also you need bash installed, because original .h to .inc
conversion script uses some bash-isms.

-- 
gonzo
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Bernd Walter 
On Thu, Mar 08, 2018 at 02:29:44PM -0800, Oleksandr Tymoshenko wrote:
> Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote:
> > > Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> > > > https://github.com/gonzoua/evdev-dump/tree/freebsd
> > > > ...
> > > > checking for unistd.h... yes
> > > > checking linux/input.h usability... no
> > > > checking linux/input.h presence... no
> > > > checking for linux/input.h... no
> > > > checking for /usr/include/linux/input.h... no
> > > > configure: error: /usr/include/linux/input.h not found
> > > > 4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
> > > > Exit 1
> > > 
> > > I've just checked, evdev-dump should be buildable:
> > > 
> > > git clone g...@github.com:gonzoua/evdev-dump.git
> > > cd evdev-dump
> > > git checkout freebsd
> > > sudo pkg install gawk gmake
> > > sh bootstrap
> > > ./configure
> > > gmake
> > 
> > That's exactly how I did.
> > Well - I've used git clone https://github.com/gonzoua/evdev-dump.git
> > Even with a fresh clone it failed at the same file.
> > 
> > I have the following:
> > /usr/include/dev/evdev/input.h
> > /usr/local/include/linux/input.h
> > /usr/local/include/xorg/input.h
> 
> Could you show output of "git branch" and
> "grep -rl /usr/include/linux/input.h ." in cloned directory?

[55]sa# git branch
* master
[56]sa# grep -rl /usr/include/linux/input.h .
./configure.ac
./autom4te.cache/output.0
./autom4te.cache/output.1
./configure
./config.log

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Oleksandr Tymoshenko 
Bernd Walter (ti...@cicely7.cicely.de) wrote:
> On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote:
> > Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> > > https://github.com/gonzoua/evdev-dump/tree/freebsd
> > > ...
> > > checking for unistd.h... yes
> > > checking linux/input.h usability... no
> > > checking linux/input.h presence... no
> > > checking for linux/input.h... no
> > > checking for /usr/include/linux/input.h... no
> > > configure: error: /usr/include/linux/input.h not found
> > > 4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
> > > Exit 1
> > 
> > I've just checked, evdev-dump should be buildable:
> > 
> > git clone g...@github.com:gonzoua/evdev-dump.git
> > cd evdev-dump
> > git checkout freebsd
> > sudo pkg install gawk gmake
> > sh bootstrap
> > ./configure
> > gmake
> 
> That's exactly how I did.
> Well - I've used git clone https://github.com/gonzoua/evdev-dump.git
> Even with a fresh clone it failed at the same file.
> 
> I have the following:
> /usr/include/dev/evdev/input.h
> /usr/local/include/linux/input.h
> /usr/local/include/xorg/input.h

Could you show output of "git branch" and
"grep -rl /usr/include/linux/input.h ." in cloned directory?

Thanks

-- 
gonzo
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Bernd Walter 
On Thu, Mar 08, 2018 at 12:38:38PM -0800, Oleksandr Tymoshenko wrote:
> Bernd Walter (ti...@cicely7.cicely.de) wrote:
> > On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> > https://github.com/gonzoua/evdev-dump/tree/freebsd
> > ...
> > checking for unistd.h... yes
> > checking linux/input.h usability... no
> > checking linux/input.h presence... no
> > checking for linux/input.h... no
> > checking for /usr/include/linux/input.h... no
> > configure: error: /usr/include/linux/input.h not found
> > 4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
> > Exit 1
> 
> I've just checked, evdev-dump should be buildable:
> 
> git clone g...@github.com:gonzoua/evdev-dump.git
> cd evdev-dump
> git checkout freebsd
> sudo pkg install gawk gmake
> sh bootstrap
> ./configure
> gmake

That's exactly how I did.
Well - I've used git clone https://github.com/gonzoua/evdev-dump.git
Even with a fresh clone it failed at the same file.

I have the following:
/usr/include/dev/evdev/input.h
/usr/local/include/linux/input.h
/usr/local/include/xorg/input.h

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Hans Petter Selasky 

On 03/08/18 22:08, Bernd Walter wrote:

On Thu, Mar 08, 2018 at 09:08:49PM +0100, Bernd Walter wrote:

On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:

This is what I have right now:
[20]sa# cat /etc/X11/xorg.conf

Section "InputDevice"
 Identifier  "Touchscreen"
 Driver  "evdev"
 Option  "Device" "/dev/input/event0"
EndSection

Section "ServerLayout"
 Identifier  "MyLayout"
 InputDevice "Touchscreen"
EndSection


Unfortunately now I face the next problem.

[112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen'
[112753.536] (**) evdev touchscreen: always reports core events
[112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0"
[112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5
[112753.598] (--) evdev: evdev touchscreen: Found absolute axes
[112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes
[112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one.
[112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes
[112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen
[112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen
[112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5
[112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, 
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" 
(type: TOUCHSCREEN, id 6)
[112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes.
[112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1
[112753.600] (**) evdev touchscreen: (accel) acceleration profile 0
[112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000
[112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4
[112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument

[26]sa-moeller> xinput
  Virtual core pointer id=2[master pointer  (3)]
 Virtual core XTEST pointer   id=4[slave  pointer  (2)]
 Touchscreen  id=6[slave  pointer  (2)]
 sysmouse id=8[slave  pointer  (2)]
  Virtual core keyboardid=3[master keyboard (2)]
  Virtual core XTEST keyboard  id=5[slave  keyboard (3)]
  kbdmux   id=7[slave  keyboard (3)]

Everything looks good so far, at least in my eyes.
Well - wheel emulation and such sounds a bit strange, as if it is handled
as a touchpad and not like a touchscreen.
But it says type touchscreen, so I assume that's ok.
However, I get no touch events.
I've started xev fullscreen and still nothing.

Somewhere else I've read that /dev/input/event0 should deliver something
if read and a touch happens, but this is not the case for me.

Any ideas how I can debug this thing?
There was a reference somewhere about a commandline programm to run against
an evdev, but I can't find it anymore.


xinput test delivers nothing on the touchscreen.

Neither evtest nor evdev-dump compiles because they are both missing
linux include files at some point.
https://cgit.freedesktop.org/~whot/evtest/
[48]sa> make
make  all-am
cc -DHAVE_CONFIG_H -I.  -g -O2 -MT evtest.o -MD -MP -MF .deps/evtest.Tpo -c 
-o evtest.o evtest.c
evtest.c:46:10: fatal error: 'linux/version.h' file not found
#include 
  ^
1 error generated.
*** Error code 1

Stop.
make[1]: stopped in /home/ticso/evtest
*** Error code 1

Stop.
make: stopped in /home/ticso/evtest
Exit 1

https://github.com/gonzoua/evdev-dump/tree/freebsd
...
checking for unistd.h... yes
checking linux/input.h usability... no
checking linux/input.h presence... no
checking for linux/input.h... no
checking for /usr/include/linux/input.h... no
configure: error: /usr/include/linux/input.h not found
4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
Exit 1

The touchscreen itself should be functional as it has a touch area outside
the display, which is interpreted by the USB controller to change the
backlight.
The exact same display also worked fine on Raspbian.


This is with webcamd compiled with debug support.

[18]sa# /usr/local/sbin/webcamd -d ugen0.5
Linux video capture interface: v2.00
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR LIRC bridge handler initialized
IR XMP protocol handler initialized
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV receiver chip loaded 
successfully
USB Video Class driver (1.1.1)
cpia2: V4L-Driver for Vision CPiA2 based cameras v3.0.1
pvrusb2: V4L in-tree version:Hauppauge WinTV-PVR-USB2 MPEG2 Encoder/Tuner
pvrusb2: Debug mask is 31 (0x1f)
USBVision USB Video Device Driver for

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Bernd Walter 
On Thu, Mar 08, 2018 at 09:08:49PM +0100, Bernd Walter wrote:
> On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> > This is what I have right now:
> > [20]sa# cat /etc/X11/xorg.conf 
> > 
> > Section "InputDevice"
> > Identifier  "Touchscreen"
> > Driver  "evdev"
> > Option  "Device" "/dev/input/event0"
> > EndSection
> > 
> > Section "ServerLayout"
> > Identifier  "MyLayout"
> > InputDevice "Touchscreen"
> > EndSection
> > 
> > 
> > Unfortunately now I face the next problem.
> > 
> > [112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen'
> > [112753.536] (**) evdev touchscreen: always reports core events
> > [112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0"
> > [112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5
> > [112753.598] (--) evdev: evdev touchscreen: Found absolute axes
> > [112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes
> > [112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one.
> > [112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes
> > [112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen
> > [112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen
> > [112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5
> > [112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, 
> > EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> > [112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" 
> > (type: TOUCHSCREEN, id 6)
> > [112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes.
> > [112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1
> > [112753.600] (**) evdev touchscreen: (accel) acceleration profile 0
> > [112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000
> > [112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4
> > [112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument
> > 
> > [26]sa-moeller> xinput
> >  Virtual core pointer id=2[master pointer  (3)]
> > Virtual core XTEST pointer   id=4[slave  pointer  (2)]
> > Touchscreen  id=6[slave  pointer  (2)]
> > sysmouse id=8[slave  pointer  (2)]
> >  Virtual core keyboardid=3[master keyboard (2)]
> >  Virtual core XTEST keyboard  id=5[slave  keyboard (3)]
> >  kbdmux   id=7[slave  keyboard (3)]
> > 
> > Everything looks good so far, at least in my eyes.
> > Well - wheel emulation and such sounds a bit strange, as if it is handled
> > as a touchpad and not like a touchscreen.
> > But it says type touchscreen, so I assume that's ok.
> > However, I get no touch events.
> > I've started xev fullscreen and still nothing.
> > 
> > Somewhere else I've read that /dev/input/event0 should deliver something
> > if read and a touch happens, but this is not the case for me.
> > 
> > Any ideas how I can debug this thing?
> > There was a reference somewhere about a commandline programm to run against
> > an evdev, but I can't find it anymore.
> 
> xinput test delivers nothing on the touchscreen.
> 
> Neither evtest nor evdev-dump compiles because they are both missing
> linux include files at some point.
> https://cgit.freedesktop.org/~whot/evtest/
> [48]sa> make
> make  all-am
> cc -DHAVE_CONFIG_H -I.  -g -O2 -MT evtest.o -MD -MP -MF .deps/evtest.Tpo 
> -c -o evtest.o evtest.c
> evtest.c:46:10: fatal error: 'linux/version.h' file not found
> #include 
>  ^
> 1 error generated.
> *** Error code 1
> 
> Stop.
> make[1]: stopped in /home/ticso/evtest
> *** Error code 1
> 
> Stop.
> make: stopped in /home/ticso/evtest
> Exit 1
> 
> https://github.com/gonzoua/evdev-dump/tree/freebsd
> ...
> checking for unistd.h... yes
> checking linux/input.h usability... no
> checking linux/input.h presence... no
> checking for linux/input.h... no
> checking for /usr/include/linux/input.h... no
> configure: error: /usr/include/linux/input.h not found
> 4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
> Exit 1
> 
> The touchscreen itself should be functional as it has a touch area outside
> the display, which is interpreted by the USB controller to change the
> backlight.
> The exact same display also worked fine on Raspbian.

This is with webcamd compiled with debug support.

[18]sa# /usr/local/sbin/webcamd -d ugen0.5
Linux video capture interface: v2.00
IR NEC protocol handler initialized
IR RC5(x/sz) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR SANYO protocol handler initialized
IR LIRC bridge handler initialized
IR XMP protocol handler initialized
b2c2-flexcop: B2C2 FlexcopII/II(b)/III digital TV

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Oleksandr Tymoshenko 
Bernd Walter (ti...@cicely7.cicely.de) wrote:
> On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> https://github.com/gonzoua/evdev-dump/tree/freebsd
> ...
> checking for unistd.h... yes
> checking linux/input.h usability... no
> checking linux/input.h presence... no
> checking for linux/input.h... no
> checking for /usr/include/linux/input.h... no
> configure: error: /usr/include/linux/input.h not found
> 4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
> Exit 1

I've just checked, evdev-dump should be buildable:

git clone g...@github.com:gonzoua/evdev-dump.git
cd evdev-dump
git checkout freebsd
sudo pkg install gawk gmake
sh bootstrap
./configure
gmake

-- 
gonzo
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Bernd Walter 
On Thu, Mar 08, 2018 at 08:11:31PM +0100, Bernd Walter wrote:
> This is what I have right now:
> [20]sa# cat /etc/X11/xorg.conf 
> 
> Section "InputDevice"
> Identifier  "Touchscreen"
> Driver  "evdev"
> Option  "Device" "/dev/input/event0"
> EndSection
> 
> Section "ServerLayout"
> Identifier  "MyLayout"
> InputDevice "Touchscreen"
> EndSection
> 
> 
> Unfortunately now I face the next problem.
> 
> [112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen'
> [112753.536] (**) evdev touchscreen: always reports core events
> [112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0"
> [112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5
> [112753.598] (--) evdev: evdev touchscreen: Found absolute axes
> [112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes
> [112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one.
> [112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes
> [112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen
> [112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen
> [112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5
> [112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, 
> EmulateWheelInertia: 10, EmulateWheelTimeout: 200
> [112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" 
> (type: TOUCHSCREEN, id 6)
> [112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes.
> [112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1
> [112753.600] (**) evdev touchscreen: (accel) acceleration profile 0
> [112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000
> [112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4
> [112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument
> 
> [26]sa-moeller> xinput
>  Virtual core pointer id=2[master pointer  (3)]
> Virtual core XTEST pointer   id=4[slave  pointer  (2)]
> Touchscreen  id=6[slave  pointer  (2)]
> sysmouse id=8[slave  pointer  (2)]
>  Virtual core keyboardid=3[master keyboard (2)]
>  Virtual core XTEST keyboard  id=5[slave  keyboard (3)]
>  kbdmux   id=7[slave  keyboard (3)]
> 
> Everything looks good so far, at least in my eyes.
> Well - wheel emulation and such sounds a bit strange, as if it is handled
> as a touchpad and not like a touchscreen.
> But it says type touchscreen, so I assume that's ok.
> However, I get no touch events.
> I've started xev fullscreen and still nothing.
> 
> Somewhere else I've read that /dev/input/event0 should deliver something
> if read and a touch happens, but this is not the case for me.
> 
> Any ideas how I can debug this thing?
> There was a reference somewhere about a commandline programm to run against
> an evdev, but I can't find it anymore.

xinput test delivers nothing on the touchscreen.

Neither evtest nor evdev-dump compiles because they are both missing
linux include files at some point.
https://cgit.freedesktop.org/~whot/evtest/
[48]sa> make
make  all-am
cc -DHAVE_CONFIG_H -I.  -g -O2 -MT evtest.o -MD -MP -MF .deps/evtest.Tpo -c 
-o evtest.o evtest.c
evtest.c:46:10: fatal error: 'linux/version.h' file not found
#include 
 ^
1 error generated.
*** Error code 1

Stop.
make[1]: stopped in /home/ticso/evtest
*** Error code 1

Stop.
make: stopped in /home/ticso/evtest
Exit 1

https://github.com/gonzoua/evdev-dump/tree/freebsd
...
checking for unistd.h... yes
checking linux/input.h usability... no
checking linux/input.h presence... no
checking for linux/input.h... no
checking for /usr/include/linux/input.h... no
configure: error: /usr/include/linux/input.h not found
4.765u 3.954s 0:08.64 100.8%31397+2201k 0+27io 0pf+0w
Exit 1

The touchscreen itself should be functional as it has a touch area outside
the display, which is interpreted by the USB controller to change the
backlight.
The exact same display also worked fine on Raspbian.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Bernd Walter 
On Thu, Mar 08, 2018 at 07:30:26PM +0300, Greg wrote:
> On 03/08, Hans Petter Selasky wrote:
> >On 03/08/18 17:16, Bernd Walter wrote:
> >>Hardware is a Raspberry Pi3 with current r330034.
> >>I'm trying to run a USB touchscreen.
> >>Tested wmt and uep, but neither wants to attach, although the Waveshare
> >>display I'm using is likely running an egalaxy firmware.
> >>However webcamd accepts the device and creates a /dev/input/event0.
> >>But I can't get X to use it.
> >>xf86-input-evdev-2.10.5 is installed and it created an X config file
> >>under /usr/local/share/X11/xorg.conf.d/10-evdev.conf.
> >>I also tried some google results in /etc/X11/xorg.conf, but X never
> >>touches the device:
> >
> >See here:
> >
> >https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678
> 
> Or here:
> 
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222609
> 
> But that's all about hotplug. It is definitely possible to manually 
> configure the device on the stock xorg-server package. I can't say if 
> the "google results" are correct without actually seeing them, but it 
> should explicitly specify the /dev/input/event0 path.

Thank you both for the links.
I'd already seen them and had been a bit confused if they are required or
not and also found references that a manual configuration should work.

On Thu, Mar 08, 2018 at 05:36:06PM +0100, Roberto Fernandez Cueto wrote:
> Roberto Fernandez-Cueto schrieb am 08.03.2018 17:36
> _
> 
> You have to explicitely tell Xorg that you want to use the touch with
> the layout.
> 
> Something like,
> 
> Section "ServerLayout"
>   Identifier  "MyLayout"
>   InputDevice "touchscreen"
> EndSection

Thank you - this was the missing link, why my static configuration failed.
I'd only setup the InputDevice section.

This is what I have right now:
[20]sa# cat /etc/X11/xorg.conf 

Section "InputDevice"
Identifier  "Touchscreen"
Driver  "evdev"
Option  "Device" "/dev/input/event0"
EndSection

Section "ServerLayout"
Identifier  "MyLayout"
InputDevice "Touchscreen"
EndSection


Unfortunately now I face the next problem.

[112753.535] (II) Using input driver 'evdev' for 'evdev touchscreen'
[112753.536] (**) evdev touchscreen: always reports core events
[112753.536] (**) evdev: evdev touchscreen: Device: "/dev/input/event0"
[112753.598] (--) evdev: evdev touchscreen: Vendor 0xeef Product 0x5
[112753.598] (--) evdev: evdev touchscreen: Found absolute axes
[112753.598] (--) evdev: evdev touchscreen: Found absolute multitouch axes
[112753.598] (II) evdev: evdev touchscreen: No buttons found, faking one.
[112753.598] (--) evdev: evdev touchscreen: Found x and y absolute axes
[112753.598] (--) evdev: evdev touchscreen: Found absolute touchscreen
[112753.598] (II) evdev: evdev touchscreen: Configuring as touchscreen
[112753.598] (**) evdev: evdev touchscreen: YAxisMapping: buttons 4 and 5
[112753.598] (**) evdev: evdev touchscreen: EmulateWheelButton: 4, 
EmulateWheelInertia: 10, EmulateWheelTimeout: 200
[112753.598] (II) XINPUT: Adding extended input device "evdev touchscreen" 
(type: TOUCHSCREEN, id 6)
[112753.599] (II) evdev: evdev touchscreen: initialized for absolute axes.
[112753.600] (**) evdev touchscreen: (accel) keeping acceleration scheme 1
[112753.600] (**) evdev touchscreen: (accel) acceleration profile 0
[112753.600] (**) evdev touchscreen: (accel) acceleration factor: 2.000
[112753.600] (**) evdev touchscreen: (accel) acceleration threshold: 4
[112753.601] (WW) fcntl(6, F_SETOWN): Invalid argument

[26]sa-moeller> xinput
 Virtual core pointer id=2[master pointer  (3)]
Virtual core XTEST pointer   id=4[slave  pointer  (2)]
Touchscreen  id=6[slave  pointer  (2)]
sysmouse id=8[slave  pointer  (2)]
 Virtual core keyboardid=3[master keyboard (2)]
 Virtual core XTEST keyboard  id=5[slave  keyboard (3)]
 kbdmux   id=7[slave  keyboard (3)]

Everything looks good so far, at least in my eyes.
Well - wheel emulation and such sounds a bit strange, as if it is handled
as a touchpad and not like a touchscreen.
But it says type touchscreen, so I assume that's ok.
However, I get no touch events.
I've started xev fullscreen and still nothing.

Somewhere else I've read that /dev/input/event0 should deliver something
if read and a touch happens, but this is not the case for me.

Any ideas how I can debug this thing?
There was a reference somewhere about a commandline programm to run against
an evdev, but I can't find it anymore.

-- 
B.Walter  http://www.bwct.de
Modbus/TCP Ethernet I/O Baugruppen, ARM basierte FreeBSD Rechner uvm.
___
freebsd-current@freebsd.org mailing list

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Roberto Fernandez Cueto 
Roberto Fernandez-Cueto schrieb am 08.03.2018 17:36
_

You have to explicitely tell Xorg that you want to use the touch with
the layout.

Something like,

Section "ServerLayout"
Identifier  "MyLayout"
InputDevice "touchscreen"
EndSection

On Thu, Mar 08, 2018 at 05:16:45PM +0100, Bernd Walter wrote:
> Hardware is a Raspberry Pi3 with current r330034.
> I'm trying to run a USB touchscreen.
> Tested wmt and uep, but neither wants to attach, although the Waveshare
> display I'm using is likely running an egalaxy firmware.
> However webcamd accepts the device and creates a /dev/input/event0.
> But I can't get X to use it.
> xf86-input-evdev-2.10.5 is installed and it created an X config file
> under /usr/local/share/X11/xorg.conf.d/10-evdev.conf.
> I also tried some google results in /etc/X11/xorg.conf, but X never
> touches the device:
> [ 19417.932] 
> X.Org X Server 1.18.4
> Release Date: 2016-07-19
> [ 19417.932] X Protocol Version 11, Revision 0
> [ 19417.932] Build Operating System: FreeBSD 12.0-CURRENT arm64 
> [ 19417.932] Current Operating System: FreeBSD sa 12.0-CURRENT FreeBSD 
> 12.0-CURRENT #0: Mon Mar  5 16:28:19 UTC 2018 
> ticso@sa:/usr/obj/usr/src-nfs/builder/current-anlage/head/arm64.aarch64/sys/GENERIC
>  arm64
> [ 19417.933] Build Date: 19 January 2018  09:58:28PM
> [ 19417.934]  
> [ 19417.934] Current version of pixman: 0.34.0
> [ 19417.934]Before reporting problems, check http://wiki.x.org
> to make sure that you have the latest version.
> [ 19417.934] Markers: (--) probed, (**) from config file, (==) default 
> setting,
> (++) from command line, (!!) notice, (II) informational,
> (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
> [ 19417.934] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar  7 15:59:15 
> 2018
> [ 19417.935] (==) Using config file: "/etc/X11/xorg.conf"
> [ 19417.935] (==) Using system config directory 
> "/usr/local/share/X11/xorg.conf.d"
> [ 19417.936] (==) No Layout section.  Using the first Screen section.
> [ 19417.936] (==) No screen section available. Using defaults.
> [ 19417.936] (**) |-->Screen "Default Screen Section" (0)
> [ 19417.936] (**) |   |-->Monitor ""
> [ 19417.937] (==) No monitor specified for screen "Default Screen Section".
> Using a default monitor configuration.
> [ 19417.938] (==) Automatically adding devices
> [ 19417.938] (==) Automatically enabling devices
> [ 19417.938] (==) Not automatically adding GPU devices
> [ 19417.938] (==) Max clients allowed: 256, resource mask: 0x1f
> [ 19417.938] (==) FontPath set to:
> /usr/local/share/fonts/misc/,
> /usr/local/share/fonts/TTF/,
> /usr/local/share/fonts/OTF/,
> /usr/local/share/fonts/Type1/,
> /usr/local/share/fonts/100dpi/,
> /usr/local/share/fonts/75dpi/
> [ 19417.938] (==) ModulePath set to "/usr/local/lib/xorg/modules"
> [ 19417.938] (II) The server relies on devd to provide the list of input 
> devices.
> If no devices become available, reconfigure devd or disable 
> AutoAddDevices.
> [ 19417.938] (II) Loader magic: 0x1e0018
> [ 19417.939] (II) Module ABI versions:
> [ 19417.939]X.Org ANSI C Emulation: 0.4
> [ 19417.939]X.Org Video Driver: 20.0
> [ 19417.939]X.Org XInput driver : 22.1
> [ 19417.939]X.Org Server Extension : 9.0
> [ 19417.939] (II) LoadModule: "glx"
> [ 19417.940] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
> [ 19417.951] (II) Module glx: vendor="X.Org Foundation"
> [ 19417.951]compiled for 1.18.4, module version = 1.0.0
> [ 19417.951]ABI class: X.Org Server Extension, version 9.0
> [ 19417.951] (==) AIGLX enabled
> [ 19417.951] (==) Matched modesetting as autoconfigured driver 0
> [ 19417.951] (==) Matched scfb as autoconfigured driver 1
> [ 19417.951] (==) Assigned the driver to the xf86ConfigLayout
> [ 19417.951] (II) LoadModule: "modesetting"
> [ 19417.952] (II) Loading 
> /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
> [ 19417.952] (II) Module modesetting: vendor="X.Org Foundation"
> [ 19417.952]compiled for 1.18.4, module version = 1.18.4
> [ 19417.952]Module class: X.Org Video Driver
> [ 19417.952]ABI class: X.Org Video Driver, version 20.0
> [ 19417.952] (II) LoadModule: "scfb"
> [ 19417.953] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so
> [ 19417.953] (II) Module scfb: vendor="X.Org Foundation"
> [ 19417.953]compiled for 1.18.4, module version = 0.0.4
> [ 19417.953]ABI class: X.Org Video Driver, version 20.0
> [ 19417.954] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
> [ 19417.954] (II) scfb: driver for wsdisplay framebuffer: scfb
> [ 19417.954] (--) Using syscons driver with X support (version 2.0)
> [ 19417.954] (--) using VT number 2
> 
> [ 19417.954] (WW) Falling back to old probe method for modesetting
> [ 19417.955] (EE) open /dev/dri/card0: No such file

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Greg 

On 03/08, Hans Petter Selasky wrote:

On 03/08/18 17:16, Bernd Walter wrote:

Hardware is a Raspberry Pi3 with current r330034.
I'm trying to run a USB touchscreen.
Tested wmt and uep, but neither wants to attach, although the Waveshare
display I'm using is likely running an egalaxy firmware.
However webcamd accepts the device and creates a /dev/input/event0.
But I can't get X to use it.
xf86-input-evdev-2.10.5 is installed and it created an X config file
under /usr/local/share/X11/xorg.conf.d/10-evdev.conf.
I also tried some google results in /etc/X11/xorg.conf, but X never
touches the device:


See here:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=196678


Or here:

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=222609

But that's all about hotplug. It is definitely possible to manually 
configure the device on the stock xorg-server package. I can't say if 
the "google results" are correct without actually seeing them, but it 
should explicitly specify the /dev/input/event0 path.

___
freebsd-current@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"

Re: webcamd based touchscreen problem on Pi3

2018-03-08 Thread Hans Petter Selasky 

On 03/08/18 17:16, Bernd Walter wrote:

Hardware is a Raspberry Pi3 with current r330034.
I'm trying to run a USB touchscreen.
Tested wmt and uep, but neither wants to attach, although the Waveshare
display I'm using is likely running an egalaxy firmware.
However webcamd accepts the device and creates a /dev/input/event0.
But I can't get X to use it.
xf86-input-evdev-2.10.5 is installed and it created an X config file
under /usr/local/share/X11/xorg.conf.d/10-evdev.conf.
I also tried some google results in /etc/X11/xorg.conf, but X never
touches the device:
[ 19417.932]
X.Org X Server 1.18.4
Release Date: 2016-07-19
[ 19417.932] X Protocol Version 11, Revision 0
[ 19417.932] Build Operating System: FreeBSD 12.0-CURRENT arm64
[ 19417.932] Current Operating System: FreeBSD sa 12.0-CURRENT FreeBSD 
12.0-CURRENT #0: Mon Mar  5 16:28:19 UTC 2018 
ticso@sa:/usr/obj/usr/src-nfs/builder/current-anlage/head/arm64.aarch64/sys/GENERIC
 arm64
[ 19417.933] Build Date: 19 January 2018  09:58:28PM
[ 19417.934]
[ 19417.934] Current version of pixman: 0.34.0
[ 19417.934]Before reporting problems, check http://wiki.x.org
 to make sure that you have the latest version.
[ 19417.934] Markers: (--) probed, (**) from config file, (==) default setting,
 (++) from command line, (!!) notice, (II) informational,
 (WW) warning, (EE) error, (NI) not implemented, (??) unknown.
[ 19417.934] (==) Log file: "/var/log/Xorg.0.log", Time: Wed Mar  7 15:59:15 
2018
[ 19417.935] (==) Using config file: "/etc/X11/xorg.conf"
[ 19417.935] (==) Using system config directory 
"/usr/local/share/X11/xorg.conf.d"
[ 19417.936] (==) No Layout section.  Using the first Screen section.
[ 19417.936] (==) No screen section available. Using defaults.
[ 19417.936] (**) |-->Screen "Default Screen Section" (0)
[ 19417.936] (**) |   |-->Monitor ""
[ 19417.937] (==) No monitor specified for screen "Default Screen Section".
 Using a default monitor configuration.
[ 19417.938] (==) Automatically adding devices
[ 19417.938] (==) Automatically enabling devices
[ 19417.938] (==) Not automatically adding GPU devices
[ 19417.938] (==) Max clients allowed: 256, resource mask: 0x1f
[ 19417.938] (==) FontPath set to:
 /usr/local/share/fonts/misc/,
 /usr/local/share/fonts/TTF/,
 /usr/local/share/fonts/OTF/,
 /usr/local/share/fonts/Type1/,
 /usr/local/share/fonts/100dpi/,
 /usr/local/share/fonts/75dpi/
[ 19417.938] (==) ModulePath set to "/usr/local/lib/xorg/modules"
[ 19417.938] (II) The server relies on devd to provide the list of input 
devices.
 If no devices become available, reconfigure devd or disable 
AutoAddDevices.
[ 19417.938] (II) Loader magic: 0x1e0018
[ 19417.939] (II) Module ABI versions:
[ 19417.939]X.Org ANSI C Emulation: 0.4
[ 19417.939]X.Org Video Driver: 20.0
[ 19417.939]X.Org XInput driver : 22.1
[ 19417.939]X.Org Server Extension : 9.0
[ 19417.939] (II) LoadModule: "glx"
[ 19417.940] (II) Loading /usr/local/lib/xorg/modules/extensions/libglx.so
[ 19417.951] (II) Module glx: vendor="X.Org Foundation"
[ 19417.951]compiled for 1.18.4, module version = 1.0.0
[ 19417.951]ABI class: X.Org Server Extension, version 9.0
[ 19417.951] (==) AIGLX enabled
[ 19417.951] (==) Matched modesetting as autoconfigured driver 0
[ 19417.951] (==) Matched scfb as autoconfigured driver 1
[ 19417.951] (==) Assigned the driver to the xf86ConfigLayout
[ 19417.951] (II) LoadModule: "modesetting"
[ 19417.952] (II) Loading /usr/local/lib/xorg/modules/drivers/modesetting_drv.so
[ 19417.952] (II) Module modesetting: vendor="X.Org Foundation"
[ 19417.952]compiled for 1.18.4, module version = 1.18.4
[ 19417.952]Module class: X.Org Video Driver
[ 19417.952]ABI class: X.Org Video Driver, version 20.0
[ 19417.952] (II) LoadModule: "scfb"
[ 19417.953] (II) Loading /usr/local/lib/xorg/modules/drivers/scfb_drv.so
[ 19417.953] (II) Module scfb: vendor="X.Org Foundation"
[ 19417.953]compiled for 1.18.4, module version = 0.0.4
[ 19417.953]ABI class: X.Org Video Driver, version 20.0
[ 19417.954] (II) modesetting: Driver for Modesetting Kernel Drivers: kms
[ 19417.954] (II) scfb: driver for wsdisplay framebuffer: scfb
[ 19417.954] (--) Using syscons driver with X support (version 2.0)
[ 19417.954] (--) using VT number 2

[ 19417.954] (WW) Falling back to old probe method for modesetting
[ 19417.955] (EE) open /dev/dri/card0: No such file or directory
[ 19417.955] (WW) Falling back to old probe method for scfb
[ 19417.955] scfb trace: probe start
[ 19417.955] (II) scfb(0): using default device
[ 19417.955] scfb trace: probe done
[ 19417.955] (WW) VGA arbiter: cannot open kernel arbiter, no multi-card support
[ 19417.955] scfb: PreInit 0
[ 19417.955] (II) scfb(0): Using: depth (24),   width (1280),height (800)
[ 19417.956] (II) scfb(0): Creating default Display subsection in Screen section
 "Default Screen Section" for depth/fbbpp 24/24
[