From: <tho...@be...> - 2005-12-03 15:04:03
|
After much web surfing, I've concluded I'm going to have to write a driver for touchscreen, regardless of what controller I use. The ucb1400 seems to be the most common controller used on arm-linux platforms, so I guess I'll stick with that. I did find some "patches" for a ucb1400 touch driver that maybe I can use once I understand more about the device driver architecture. Three questions: 1) Do I really need to write a driver, or is there an easier way? 2) What kernel configuration is required? 3) Is the documentation pointed to on the gumstix wiki (on Linux device drivers) the best place to start? The reason I ask about #3 is that it seems like there has been a recent change in the input driver architecture (/dev/inputx?). I don't want to invest time in getting up to speed on something that is (or soon will be) obsolete. Thanks, Dave Thomas |
From: <tho...@be...> - 2005-12-05 02:17:54
|
Found the following patches for UCB1400 support: http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-March/027990.html Should these work on the gum's kernel? I guess I need to configure the kernel for sound before applying the patches? (Some of the patched files don't exist in the gum's kernel source tree). Thanks, Dave Thomas |
From: Craig H. <cr...@gu...> - 2005-12-05 17:39:17
|
Those patches I think are for the ALSA driver, which I believe are all now rolled into the mainline kernel with 2.6.13 or 2.6.14 -- once I finally get that kernel working, it should all just be there. I'll make a big push and see if I can't get this stupid dual-ethernet thing working under the new 2.6.1[34] smc driver, or else just junk the new driver and forward-port the old driver instead. C On Dec 4, 2005, at 10:34 AM, <tho...@be...> wrote: > Found the following patches for UCB1400 support: > > http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-March/ > 027990.html > > Should these work on the gum's kernel? I guess I need to configure > the kernel for sound before applying the patches? (Some of the > patched files don't exist in the gum's kernel source tree). > > Thanks, > > Dave Thomas > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD > SPLUNK! > http://ads.osdn.com/?ad_id=7637&alloc_id=16865&op=click > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Bas v. K. <bas...@gm...> - 2005-12-08 15:45:49
|
Problem with the ALSA touch screen driver in the kernel is that it depends on pci, which doesn't work/doesn't compile/is not needed with the gumstix... regards, Bas On 12/5/05, Craig Hughes <cr...@gu...> wrote: > Those patches I think are for the ALSA driver, which I believe are > all now rolled into the mainline kernel with 2.6.13 or 2.6.14 -- once > I finally get that kernel working, it should all just be there. I'll > make a big push and see if I can't get this stupid dual-ethernet > thing working under the new 2.6.1[34] smc driver, or else just junk > the new driver and forward-port the old driver instead. > > C > > On Dec 4, 2005, at 10:34 AM, <tho...@be...> wrote: > > > Found the following patches for UCB1400 support: > > > > http://lists.arm.linux.org.uk/pipermail/linux-arm-kernel/2005-March/ > > 027990.html > > > > Should these work on the gum's kernel? I guess I need to configure > > the kernel for sound before applying the patches? (Some of the > > patched files don't exist in the gum's kernel source tree). > > > > Thanks, > > > > Dave Thomas > > > > > > > > ------------------------------------------------------- > > This SF.net email is sponsored by: Splunk Inc. Do you grep through > > log files > > for problems? Stop! Download the new AJAX search engine that makes > > searching your log files as easy as surfing the web. DOWNLOAD > > SPLUNK! > > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > > _______________________________________________ > > gumstix-users mailing list > > gum...@li... > > https://lists.sourceforge.net/lists/listinfo/gumstix-users > > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through log fi= les > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! > http://ads.osdn.com/?ad_id=3D7637&alloc_id=3D16865&op=3Dclick > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users > |
From: <tho...@be...> - 2005-12-10 22:52:45
|
Bas, Just now saw your post (after I've spent a few hours trying to get 2.6.14 to build!) So, I guess that's a dead end. What's my best option for adding touch to the gum? I thought using the ucb1400 would minimize driver developement time, but that doesn't appear to be true. My screen is a Microtouch, 4 wire resistive. 3M has a controller chip, and linux drivers, but only in binary form. I'm prepared to write my own, but surely I'd be reinventing the wheel? (Craig-- 2.6.14 does has been building away for about an hour now, after I got quilt working) Thanks, Dave Thomas >> Problem with the ALSA touch screen driver in the kernel is that it >> depends on pci, which doesn't work/doesn't compile/is not needed with >> the gumstix... >> regards, >> Bas |
From: Bas v. K. <bas...@gm...> - 2005-12-11 20:00:41
|
> > What's my best option for adding touch to the gum? I thought using the u= cb1400 would minimize driver developement time, but that doesn't appear to = be true. > Your fastest option right now is to use a serial port and the touch screen driver card that goes with your 3m touch screen (that's what we opted for at the moment). Keep in mind that if you use a breakout gs board to custom connect to the touch screen card, you'll need to add level shifters for RS232. The 3M boards need 5V or more, which can be taken directly from the gumstix power connector (the cards have a regulator on board). If you don't have space for the extra touch screen board in your application, you'll have to change the kernel drivers so that they don't depend on pci anymore. I guess that shouldn't be too difficult, but if you haven't done any kernel driver development before, it might take you the better part of a week to get somewhere... Regards, Bas |
From: Craig H. <cr...@gu...> - 2005-12-11 23:00:57
|
Bas, just curious if you've gone further than I have with the =20 touchscreen thing and found it doesn't work on gumstix. I'm getting =20 some errors in MODPOST about some symbols it didn't find, but at =20 least some of those symbols are in fact in the kernel (they show up =20 in System.map), so I'm not sure the messages aren't just spurious. =20 Certainly everything seems to compile fine without needing PCI stuff =20 to be turned on; though as I mentioned before, the AC97 stuff is =20 located in a directory under sound/pci but doesn't seem to actually =20 depend on any PCI stuff. C On Dec 11, 2005, at 12:00 PM, Bas van Klinkenberg wrote: >> >> What's my best option for adding touch to the gum? I thought =20 >> using the ucb1400 would minimize driver developement time, but =20 >> that doesn't appear to be true. >> > > Your fastest option right now is to use a serial port and the touch > screen driver card that goes with your 3m touch screen (that's what we > opted for at the moment). Keep in mind that if you use a breakout gs > board to custom connect to the touch screen card, you'll need to add > level shifters for RS232. The 3M boards need 5V or more, which can be > taken directly from the gumstix power connector (the cards have a > regulator on board). > If you don't have space for the extra touch screen board in your > application, you'll have to change the kernel drivers so that they > don't depend on pci anymore. I guess that shouldn't be too difficult, > but if you haven't done any kernel driver development before, it might > take you the better part of a week to get somewhere... > > Regards, > Bas > > > ------------------------------------------------------- > This SF.net email is sponsored by: Splunk Inc. Do you grep through =20 > log files > for problems? Stop! Download the new AJAX search engine that makes > searching your log files as easy as surfing the web. DOWNLOAD =20 > SPLUNK! > http://ads.osdn.com/?ad_idv37&alloc_id=16865&op=3Dclick > _______________________________________________ > gumstix-users mailing list > gum...@li... > https://lists.sourceforge.net/lists/listinfo/gumstix-users |
From: Bas v. K. <bas...@gm...> - 2005-12-13 11:15:44
|
On 12/12/05, Craig Hughes <cr...@gu...> wrote: > Bas, just curious if you've gone further than I have with the > touchscreen thing and found it doesn't work on gumstix. I'm getting > some errors in MODPOST about some symbols it didn't find, but at > least some of those symbols are in fact in the kernel (they show up > in System.map), so I'm not sure the messages aren't just spurious. > Certainly everything seems to compile fine without needing PCI stuff > to be turned on; though as I mentioned before, the AC97 stuff is > located in a directory under sound/pci but doesn't seem to actually > depend on any PCI stuff. > Craig, that would be good news, I'll dive into it again tonight and see where I went wrong. Hopefully I can get it to work, I'll post the results here. Best regards, Bas |