From: Hans-Christian Egtvedt <hans-christian.egtvedt@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] tslib: patch to replace the fixes of check_fd routine
Date: Tue, 08 Jul 2008 10:14:17 +0200 [thread overview]
Message-ID: <1215504857.12403.7.camel@localhost> (raw)
Hi,
After being annoyed too long I took a look at the problem that AVR32 did
not fully work with tslib. There seems to be a little/big endian issue
somewhere in the input layer. The attached patch is a quick fix for
that. I will try to dig in later to see what the real issue is and
where.
In the same go please remove tslib-1.0-absbit.patch and
tslib-1.0-remove-return-on-error-from-check-df.patch, since they are now
no longer needed.
And rename tslib_add_finddef_and_inputattach_utils.patch to
tslib-1.0-add-finddef-and-inputattach-utils.patch.
This also fixes the spurious messages about unknown event 0 tslib was
puring into stderr.
--
With kind regards,
Hans-Christian Egtvedt, Applications Engineer
-------------- next part --------------
A non-text attachment was scrubbed...
Name: tslib-1.0-fix-check_fd-function.patch
Type: text/x-patch
Size: 1363 bytes
Desc: not available
Url : http://busybox.net/lists/buildroot/attachments/20080708/266e39b8/attachment.bin
reply other threads:[~2008-07-08 8:14 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1215504857.12403.7.camel@localhost \
--to=hans-christian.egtvedt@atmel.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