From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Currently packaging Qt5
Date: Wed, 22 May 2013 15:30:44 +0200 [thread overview]
Message-ID: <20130522153044.76f14e2d@skate> (raw)
In-Reply-To: <321768C95D21724485BCE784F1BE98473EB1DC4F@DBDE04.ent.ti.com>
Dear Sundareson, Prabindh,
On Wed, 22 May 2013 13:26:53 +0000, Sundareson, Prabindh wrote:
> Ok. What I really meant is - I am "rebuilding" the drivers with the
> Buildroot toolchain (so, potentially there will be a newer binary
> package exclusively for Buildroot). With these new drivers, will
> Spenser be able to create the required recipe ?
When you mean "drivers", do you mean the kernel drivers or the
userspace libraries? As far as I know, the kernel drivers are
open-source, so anyone can rebuild them.
However, the userspace libraries are binary-only. Of course, it appears
that you work at TI, so maybe you have access to the source code of
those userspace libraries that are, for us mere mortals, binary-only.
If it's the case, rebuilding them with the Buildroot toolchain and
providing us with the resulting binary would not make much sense
unfortunately: the uClibc library that Buildroot uses in its internal
toolchain backend does not provide any kind of backward compatible ABI.
So whenever the uClibc version or configuration is changed, the ABI
might be broken. So using binary-only userspace libraries in an uClibc
context is particularly difficult, I'm afraid.
Or maybe you're talking about something else?
Best regards,
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
next prev parent reply other threads:[~2013-05-22 13:30 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 9:58 [Buildroot] Currently packaging Qt5 Thomas Petazzoni
2013-01-14 10:50 ` Daniel Nyström
2013-01-14 11:04 ` Thomas Petazzoni
2013-02-19 4:18 ` prabindh
2013-02-19 15:29 ` Thomas Petazzoni
2013-05-20 3:31 ` prabindh
2013-05-22 11:55 ` Sundareson, Prabindh
2013-05-22 12:17 ` Thomas Petazzoni
2013-05-22 12:23 ` prabindh
2013-05-22 12:31 ` Thomas Petazzoni
2013-05-22 12:36 ` prabindh
2013-05-22 13:06 ` Thomas Petazzoni
2013-05-22 13:26 ` Sundareson, Prabindh
2013-05-22 13:30 ` Thomas Petazzoni [this message]
2013-05-22 13:35 ` prabindh
2013-05-22 14:04 ` Thomas Petazzoni
2013-05-22 14:18 ` Spenser Gilliland
2013-05-22 14:39 ` Thomas Petazzoni
2013-05-22 15:57 ` prabindh
2013-05-22 17:33 ` Spenser Gilliland
2013-05-23 20:38 ` Wojciech Sleńska
2013-05-22 12:16 ` Thomas Petazzoni
2013-05-22 12:21 ` prabindh
2013-01-14 11:37 ` Luca Ceresoli
2013-01-14 11:45 ` Thomas Petazzoni
2013-01-14 12:48 ` Sagaert Johan
2013-01-14 13:10 ` Thomas Petazzoni
2013-01-17 9:03 ` Arnout Vandecappelle
2013-02-06 9:56 ` Daniel Nyström
2013-02-06 10:04 ` Thomas Petazzoni
2013-02-06 10:12 ` Frédéric COIFFIER
2013-02-06 10:43 ` Thomas Petazzoni
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=20130522153044.76f14e2d@skate \
--to=thomas.petazzoni@free-electrons.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