From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/tslib
Date: Wed, 11 Jun 2008 15:37:54 +0100 [thread overview]
Message-ID: <484FE342.3070405@carallon.com> (raw)
In-Reply-To: <47D6EDED.5090506@carallon.com>
Will Wagner wrote:
>>> Log:
>>> patches for tslib
>>>
>>> Added:
>>> trunk/buildroot/package/tslib/tslib-1.0-absbit.patch
>>> trunk/buildroot/package/tslib/tslib-1.0-remove-return-on-error-from-check-df.patch
>> These two patches are actually wrong, I think the tslib error you (I)
>> see is because of big-endian architecture. I will hopefully give it a go
>> next week. As long as I remember it (-:
>
> tslib-1.0-remove-return-on-error-from-check-df.patch is definitely wrong
> - with this patch applied I get lots of error messages and inspecting
> the code the patch removes code that is needed.
>
> Not sure about the tslib-1.0-absbit.patch patch. I think it is correct
> as you only need 16 bits as ABS_MAX is 0x3f
>
Have looked at this again and the tslib-1.0-absbit.patch patch is
definitely wrong. ABS_MAX is 0x3f which means that it needs 63 bits.
There is a seperate bug with tslib though. The ioctl calls to get bit
and absbit are wrong. They pass in the size as sizeof(bit) * 8 but the
size should be in bytes and not bits. This means that it things the
variables are very large. If absbit is declared as only 32 bits (as in
the patch) then because of the size being passed to ioctl wrong that
call zeros bits as it is adjacent on the stack. Although the test for
EV_ABS has already passed is does mean that using_syn is never set.
I also think there is a performance optimisation that can be made.
Currently ts_input_read() checks is sane_fd == 0 and if so calls
check_fd(). I believe once the check has succeeded there is no need to
call it again for the device (I don't think input device capabilities
can change on the fly). The mechanism is already in place to do this,
check_fd() just needs to return >0 on success.
Attached is a patch for those two issues.
Will.
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Senior Project Engineer Office Tel: +44 (0)20 7371 2032
Carallon Ltd, Studio G20, Shepherds Building, Rockley Rd, London W14 0DA
------------------------------------------------------------------------
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: tslib-1.0-checkfd_fixes.patch
Url: http://busybox.net/lists/buildroot/attachments/20080611/34cf45c2/attachment-0001.txt
next prev parent reply other threads:[~2008-06-11 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-06 18:27 [Buildroot] svn commit: trunk/buildroot/package/tslib ninevoltz at uclibc.org
2008-03-06 18:50 ` Hans-Christian Egtvedt
2008-03-11 20:39 ` Will Wagner
2008-06-11 14:37 ` Will Wagner [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-02-18 14:16 jacmet at uclibc.org
2009-02-18 14:16 jacmet at uclibc.org
2008-12-04 16:47 egtvedt at uclibc.org
2008-12-04 16:43 egtvedt at uclibc.org
2008-07-05 4:30 ulf at uclibc.org
2008-06-03 10:17 jacmet at uclibc.org
2008-03-12 19:03 ninevoltz at uclibc.org
2007-12-11 20:11 vanokuten at uclibc.org
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=484FE342.3070405@carallon.com \
--to=will_wagner@carallon.com \
--cc=buildroot@busybox.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox