Bug 2978 - Input Driver for the Paceblade touchscreen.
Summary: Input Driver for the Paceblade touchscreen.
Status: RESOLVED WONTFIX
Alias: None
Product: xorg
Classification: Unclassified
Component: Input/other (show other bugs)
Version: unspecified
Hardware: Other Linux (All)
: high normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard: 2011BRB_Reviewed
Keywords:
Depends on:
Blocks:
 
Reported: 2005-04-11 12:04 UTC by Thomas Zander
Modified: 2011-10-31 16:53 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
Initial version (8.34 KB, patch)
2005-04-11 12:10 UTC, Thomas Zander
no flags Details | Splinter Review

Description Thomas Zander 2005-04-11 12:04:31 UTC
I wrote a input driver for the above mentioned laptop and would like it to be 
merged into the tree so it will be released in future releases of X.
Comment 1 Thomas Zander 2005-04-11 12:10:54 UTC
Created attachment 2393 [details] [review]
Initial version

Unpack in the xc/programs/Xserver/hw/xfree86/input dir.
Comment 2 Daniel Stone 2007-02-27 01:26:13 UTC
Sorry about the phenomenal bug spam, guys.  Adding xorg-team@ to the QA contact so bugs don't get lost in future.
Comment 3 Jeremy Huddleston Sequoia 2011-10-17 02:57:07 UTC
Can you change this to be based on the modular build system?  Are you willing 
to maintain it?  Can this be done in-kernel, so evdev be used instead?
Comment 4 Thomas Zander 2011-10-18 23:16:34 UTC
Since the merge request was made 6½ years ago I kind of lost interest when 
nobody replied for so long.  Next to that the hardware is now obsolete and my 
tablet got tossed about 2 years ago.

So please close this request, if nobody there wants to do the work, and I hope that this merge request response time is not representable to other contributions to xorg.
Comment 5 Jeremy Huddleston Sequoia 2011-10-31 16:53:49 UTC
Yeah, sorry... bugzilla doesn't get much attention unless there is mailing list 
commentary to go along with it.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.