Summary: | Hyperpen input driver improvements | ||||||
---|---|---|---|---|---|---|---|
Product: | xorg | Reporter: | Egbert Eich <eich> | ||||
Component: | Input/hyperpen | Assignee: | Egbert Eich <eich> | ||||
Status: | RESOLVED INVALID | QA Contact: | Xorg Project Team <xorg-team> | ||||
Severity: | normal | ||||||
Priority: | high | CC: | erik.andren | ||||
Version: | git | Keywords: | patch | ||||
Hardware: | x86 (IA32) | ||||||
OS: | All | ||||||
URL: | http://bugs.xfree86.org/show_bug.cgi?id=257 | ||||||
Whiteboard: | 2011BRB_Reviewed | ||||||
i915 platform: | i915 features: | ||||||
Attachments: |
|
Description
Egbert Eich
2005-01-26 03:20:04 UTC
Created attachment 1753 [details] [review] See above. component shift. Is this emerged to xorg HEAD os of today? I've added a patch which I cannot test due to the lack of equipment. Only thin I can do is to make sure it compiles. Therefore I cannot recommend to stick this into any release. Anyone with a hyperpen please test - then we can include this in CVS. Marking broken (status null/blank) bugs in xorg with no activity in a long time as fixed. Please reopen if you think it's necessary, but first do a search if a similar bug report is already filed and in a NEW/ASSIGNED state. These bugs do not currently show in most search results as they do not have any status. Sorry for this janitorial spam, you know where to send hate mails to when your inbox gets full of bugs you're subscribed to. This bug should not be closed! There is a patch in here which still needs to be applied. Sorry about the phenomenal bug spam, guys. Adding xorg-team@ to the QA contact so bugs don't get lost in future. That patch is full of noise old monolithic noise. Please send a patch based on current git to xorg-devel for review. Mass closure: This bug has been untouched for more than six years, and is not obviously still valid. Please reopen this bug or file a new report if you continue to experience issues with current releases. |
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.