From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] tslib broken
Date: Thu, 16 Apr 2009 17:33:34 +0100 [thread overview]
Message-ID: <49E75DDE.60605@carallon.com> (raw)
Seems like tslib has got broken when it was converted to use autotools, it has lost a
couple of the customisations needed.
Attached is my patch that works as it did before. Note this patch deliberately removes a
couple of the tslib patches as I believe they are wrong - see
http://lists.busybox.net/pipermail/buildroot/2008-June/021164.html
Will
--
------------------------------------------------------------------------
Will Wagner will_wagner at carallon.com
Development Manager 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.patch
URL: <http://lists.busybox.net/pipermail/buildroot/attachments/20090416/52232eaf/attachment.diff>
next reply other threads:[~2009-04-16 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-16 16:33 Will Wagner [this message]
2009-04-17 5:00 ` [Buildroot] tslib broken Hans-Christian Egtvedt
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=49E75DDE.60605@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