From: Will Wagner <will_wagner@carallon.com>
To: buildroot@busybox.net
Subject: [Buildroot] svn commit: trunk/buildroot/package/tslib
Date: Tue, 11 Mar 2008 20:39:09 +0000 [thread overview]
Message-ID: <47D6EDED.5090506@carallon.com> (raw)
In-Reply-To: <1204829421.9461.81.camel@localhost>
>> 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
Regards,
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 prev parent reply other threads:[~2008-03-11 20:39 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 [this message]
2008-06-11 14:37 ` Will Wagner
-- 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=47D6EDED.5090506@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.