[<<] [<] Page 1 of 1 [>] [>>] | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Nano-X touchscreen
From: "ER" ####@####.#### Date: 24 Jun 2005 18:03:25 +0100 Message-Id: <20050624170258.1339E3D21@xprdmailfe10.nwk.excite.com> Hi all, Below is a description of the problem I'm having adding a new touchscreen device to nano-X. Your help is appreciated. Thanks, --ER ----- Original Message ----- From: "ER" ####@####.#### To: ####@####.#### Sent: Friday, June 24, 2005 10:19 AM Subject: Re: Nano-X touchscreen : : Sorry, that didn't seem to work, I still got the following after removing the timestamp. : ...... : [TOUCHME] Wrong number of bytes 0 read from touch panel (expected 6) : [TOUCHME] Wrong number of bytes 0 read from touch panel (expected 6) : ..... : : If it makes a difference, the driver is based on the tslib api. Piece of the driver looks like this: : : input_report_abs (&adc->input_d, ABS_X, adc->x_last); : input_report_abs (&adc->input_d, ABS_Y, adc->y_last); : input_report_abs (&adc->input_d, ABS_PRESSURE, : pen_down ? (ADC_VALUE_MAX - (adc->rgl[11]>>6)) : 0); : : where input_d is a struct input_dev. : If any of that makes a difference. : : thanks, : --ER : : : : --------------------------------------------------------------------- : How about leaving as short, but reading 6 bytes as suggested : by removing last structure item? : : Greg : : : Hi Greg, : : I'm working on the MW touchscreen interface and I ran into several : problems. : : I'm using kernel 2.6 and the ts_event interface is defined as : : struct ts_event { : : short pressure; : : short x; : : short y; : : short miliseconds; : : }; : : : : when I use this in the header file, I get an error: : : "Wrong number of bytes 0 read from touch panel expected 6 : : : : when I use long instead of short I get no error but I'm not getting any : response. I also print the event values and they appear to be well out of : range, for example: : : ... : : event.x: 690000, event.y: 1572867, event.pressure: 2509 : : ... : : Do you have any info/idea/docs that you help me understand this interface : so I can do this properly. : : : : Thanks, : : --ER _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Nano-X touchscreen
From: "ER" ####@####.#### Date: 24 Jun 2005 17:35:35 +0100 Message-Id: <20050624163520.D21D1BD0E0@xprdmailfe25.nwk.excite.com> Hi all, Below is a description of the problem I'm having adding a new touchscreen device to nano-X. Your help is appreciated. Thanks, --ER ----- Original Message ----- From: "ER" ####@####.#### To: ####@####.#### Sent: Friday, June 24, 2005 10:19 AM Subject: Re: Nano-X touchscreen : : Sorry, that didn't seem to work, I still got the following after removing the timestamp. : ...... : [TOUCHME] Wrong number of bytes 0 read from touch panel (expected 6) : [TOUCHME] Wrong number of bytes 0 read from touch panel (expected 6) : ..... : : If it makes a difference, the driver is based on the tslib api. Piece of the driver looks like this: : : input_report_abs (&adc->input_d, ABS_X, adc->x_last); : input_report_abs (&adc->input_d, ABS_Y, adc->y_last); : input_report_abs (&adc->input_d, ABS_PRESSURE, : pen_down ? (ADC_VALUE_MAX - (adc->rgl[11]>>6)) : 0); : : where input_d is a struct input_dev. : If any of that makes a difference. : : thanks, : --ER : : : : --------------------------------------------------------------------- : How about leaving as short, but reading 6 bytes as suggested : by removing last structure item? : : Greg : : : Hi Greg, : : I'm working on the MW touchscreen interface and I ran into several : problems. : : I'm using kernel 2.6 and the ts_event interface is defined as : : struct ts_event { : : short pressure; : : short x; : : short y; : : short miliseconds; : : }; : : : : when I use this in the header file, I get an error: : : "Wrong number of bytes 0 read from touch panel expected 6 : : : : when I use long instead of short I get no error but I'm not getting any : response. I also print the event values and they appear to be well out of : range, for example: : : ... : : event.x: 690000, event.y: 1572867, event.pressure: 2509 : : ... : : Do you have any info/idea/docs that you help me understand this interface : so I can do this properly. : : : : Thanks, : : --ER _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: Nano-X touchscreen
From: "ER" ####@####.#### Date: 24 Jun 2005 22:39:35 +0100 Message-Id: <20050624213905.7DC9B3CF4@xprdmailfe10.nwk.excite.com> Greg, It looks like I'm alone on this list. I remember subscribing a few months ago and withdrew after realizing I might be along at this. If no one have an idea, perhaps someone can explain the MOUSE_RAW, ans _TRANSFORM and how nano-X looks at the touchscreen interface. Maybe I can use the tslib in this but I'll need to understand how nanoX talks. Thanks, --ER ------------------------------------------------------------------- Date: Fri, 24 Jun 2005 10:28:36 -0600 From: Greg Haerr ####@####.#### [ Add to Address Book | Block Address | Report as Spam ] To: ####@####.#### Subject: Re: Nano-X touchscreen ER - send this to the list, Jordan Crouse will probably know the answer. Greg ----- Original Message ----- From: "ER" ####@####.#### To: ####@####.#### Sent: Friday, June 24, 2005 10:19 AM Subject: Re: Nano-X touchscreen : : Sorry, that didn't seem to work, I still got the following after removing the timestamp. : ...... : [TOUCHME] Wrong number of bytes 0 read from touch panel (expected 6) : [TOUCHME] Wrong number of bytes 0 read from touch panel (expected 6) : ..... : : If it makes a difference, the driver is based on the tslib api. Piece of the driver looks like this: : : input_report_abs (&adc->input_d, ABS_X, adc->x_last); : input_report_abs (&adc->input_d, ABS_Y, adc->y_last); : input_report_abs (&adc->input_d, ABS_PRESSURE, : pen_down ? (ADC_VALUE_MAX - (adc->rgl[11]>>6)) : 0); : : where input_d is a struct input_dev. : If any of that makes a difference. : : thanks, : --ER : : : : --------------------------------------------------------------------- : How about leaving as short, but reading 6 bytes as suggested : by removing last structure item? : : Greg : : : Hi Greg, : : I'm working on the MW touchscreen interface and I ran into several : problems. : : I'm using kernel 2.6 and the ts_event interface is defined as : : struct ts_event { : : short pressure; : : short x; : : short y; : : short miliseconds; : : }; : : : : when I use this in the header file, I get an error: : : "Wrong number of bytes 0 read from touch panel expected 6 : : : : when I use long instead of short I get no error but I'm not getting any : response. I also print the event values and they appear to be well out of : range, for example: : : ... : : event.x: 690000, event.y: 1572867, event.pressure: 2509 : : ... : : Do you have any info/idea/docs that you help me understand this interface : so I can do this properly. : : : : Thanks, : : --ER : _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Re: Nano-X touchscreen
From: Jordan Crouse ####@####.#### Date: 25 Jun 2005 01:19:36 +0100 Message-Id: <42BB98DA.3060307@cosmicpenguin.net> > : If it makes a difference, the driver is based on the tslib api. Piece of > the driver looks like this: Its a tad off topic, but I think that adding a tslib-aware driver to Microwindows would be a very good thing. I'm not going to go as far as say that we need move all our drivers to tslib en masse, since obviously there still is something to be said for very simple drivers. But supporting tslib would give us much broader support for devices, especially devices that everybody else is already using with X / QT/E / whatever. /me goes back to semi-lurking Jordan | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Re: Nano-X touchscreen
From: Jordan Crouse ####@####.#### Date: 25 Jun 2005 01:48:41 +0100 Message-Id: <42BCA9CD.4080601@cosmicpenguin.net> ER - Greetings. > : : struct ts_event { > : : short pressure; > : : short x; > : : short y; > : : short miliseconds; > : : }; > : : when I use this in the header file, I get an error: > : : "Wrong number of bytes 0 read from touch panel expected 6 Well, there are a couple of things here. First, the read is returning 0 bytes, which is unexpected, because we really don't expect to be in PD_Read unless there is something to read on the line. Does this message print out continuously, or just on an event (say when you tap the screen). The second problem is that the structure that you sent doesn't match the size of the structure that the code is reading. The number following 'expected' is just a sizeof(struct ts_event), so if your structure was being used, the sizeof(ts_event) would be 8. At one time, struct ts_event was different for different devices, so each device had its own header file that defined struct ts_event, complete with an evil #ifdef arrangement at the top of mou_touchscreen.c - Make sure that your header is the one being used. > It looks like I'm alone on this list. I remember subscribing a few months ago and withdrew after realizing I might be along at this. > If no one have an idea, perhaps someone can explain the MOUSE_RAW, ans _TRANSFORM and how nano-X looks at the touchscreen interface. Maybe I can use the tslib in this but I'll need to understand how nanoX talks. > Well, MOUSE_RAW is really pretty simple. The whole point was to provide a more generic method of handling calibration and filtering of incoming events on absolute devices like touchscreens. These devices need a bit of math applied to them to map them to the screen resolution, and most of them also need some jitter filtering applied. I decided that the best course of action would be to have a client based transform utility that then had the responsibility of passing in the transform data to the server upon load. This was done to mainly get the ugly math out of the server, but also to remove the policy of figuring out where the calibration data was stored, as well as not force a server reload after a calibration. So we have two scenarios - when one is calibrating, one wants raw data so they can do the calculations. After the data has been computed and loaded into the kernel, then the client app would want the cooked data so the touchscreen would then act like a pointer. Thats the point of the MOUSE_RAW flag - in RAW mode, data is passed straight from the touchscreen to the client with no intermediate cooking. But otherwise, the data is put through the transforms and comes out as a sane value (with hopefully as little jitter as possible). The drivers come in on the far side of this - they are responsible for reading the data, and passing to the engine. mou_touchscreen is one driver that you can use (it was created because there were four or five drivers that all did the same basic thing), but you don't have to use it. Feel free to create your own driver, as long as you can read the device file and pass the correct values to the server for processing. Hope this helps, Jordan | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Re: Nano-X touchscreen
From: "ER" ####@####.#### Date: 27 Jun 2005 15:06:25 +0100 Message-Id: <20050627140553.875C1B724@xprdmailfe17.nwk.excite.com> Hi Jordon, As per your question, the message is displayed first after a tap on the screen, then it's continually displayed. The kernel driver is build with the tslib api in mind and I was wondering if this conflicts in anyway with the nano-X touchscreen interface api. Thanks, --ER >> : : struct ts_event { >> : : short pressure; >> : : short x; >> : : short y; >> : : short miliseconds; >> : : }; >> : : when I use this in the header file, I get an error: >> : : "Wrong number of bytes 0 read from touch panel expected 6 >Well, there are a couple of things here. First, the read is returning >0 >bytes, which is unexpected, because we really don't expect to be in >PD_Read unless there is something to read on the line. >Does this message print out continuously, or just on an event (say when you tap the screen). _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Subject:
Re: [nanogui] Re: Nano-X touchscreen
From: "ER" ####@####.#### Date: 27 Jun 2005 15:23:40 +0100 Message-Id: <20050627142311.6BBD9B72D@xprdmailfe17.nwk.excite.com> Just wanted to include this. With each touchscreen event I print the following: root@arm922:~# event.x: 0000026e, event.y: 000ea600, event.pressure: 00000003, event.x: 0000026e, event.y: 000ea600, event.pressure: 00010003, timestamp: 0000 event.x: 0000026e, event.y: 000ea600, event.pressure: 00180003, timestamp: 0000 event.x: 0000026e, event.y: 000ea600, event.pressure: 014a0001, timestamp: 0000 event.x: 0000026e, event.y: 000ea600, event.pressure: 00000000, timestamp: 0000 event.x: 0000026e, event.y: 000ef420, event.pressure: 00000003, timestamp: 0000 event.x: 0000026e, event.y: 000ef420, event.pressure: 00000000, timestamp: 0000 event.x: 0000026f, event.y: 00000000, event.pressure: 00000003, timestamp: 0000 event.x: 0000026f, event.y: 00000000, event.pressure: 00010003, timestamp: 0000 event.x: 0000026f, event.y: 00000000, event.pressure: 00000000, timestamp: 0000 event.x: 0000026f, event.y: 00004e20, event.pressure: 00000003, timestamp: 0000 event.x: 0000026f, event.y: 00004e20, event.pressure: 00010003, timestamp: 0000 event.x: 0000026f, event.y: 00004e20, event.pressure: 00000000, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 00180003, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 014a0001, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 00000000, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 00000003, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 00010003, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 00180003, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 014a0001, timestamp: 0000 event.x: 0000026f, event.y: 00009c40, event.pressure: 00000000, timestamp: 0000 event.x: 0000026f, event.y: 0000ea60, event.pressure: 00180003, timestamp: 0000 event.x: 0000026f, event.y: 0000ea60, event.pressure: 014a0001, timestamp: 0000 event.x: 0000026f, event.y: 0000ea60, event.pressure: 00000000, timestamp: 0000 --- On Mon 06/27, ER < ####@####.#### > wrote: From: ER [mailto: ####@####.#### To: ####@####.#### Cc: ####@####.#### ####@####.#### Date: Mon, 27 Jun 2005 10:05:53 -0400 (EDT) Subject: Re: [nanogui] Re: Nano-X touchscreen Hi Jordon, As per your question, the message is displayed first after a tap on the screen, then it's continually displayed. The kernel driver is build with the tslib api in mind and I was wondering if this conflicts in anyway with the nano-X touchscreen interface api. Thanks, --ER >>> : : struct ts_event { >>> : : short pressure; >>> : : short x; >>> : : short y; >> : : short miliseconds; >> : : }; >>> : : when I use this in the header file, I get an error: >>> : : "Wrong number of bytes 0 read from touch panel expected 6 >>Well, there are a couple of things here. First, the read is returning 0 >>bytes, which is unexpected, because we really don't expect to be in >>PD_Read unless there is something to read on the line. >>Does this message print out continuously, or just on an event (say when you tap the screen). _______________________________________________ Join Excite! - http://www.excite.com The most personalized portal on the Web! | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
[<<] [<] Page 1 of 1 [>] [>>] |