From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: Multilib Development Update
Date: Tue, 21 Jun 2011 09:35:31 -0500 [thread overview]
Message-ID: <4E00AC33.6080500@windriver.com> (raw)
In-Reply-To: <BANLkTimMLo4g7uWsrhAr=hun4wZ6AaDjQg@mail.gmail.com>
On 6/21/11 8:02 AM, Frans Meulenbroeks wrote:
> As I already asked before: what is the benefit having this in embedded systems?
>
> If I am doing an embedded system I know the target hardware, and there is no
> need to have e.g. both 32 and 64 bit libs.
64-bit database on a 32-bit system.
64-bit "userspace" device drivers on a 32-bit system.
Being able to run a binary application for compatibility. This is fairly common
in some embedded areas where they need something like mips o32, but the rest of
the system is running n32 for performance.
etc...
This is something that most embedded systems won't use, but there are a large
class of devices, primarily Carrier Grade devices, that do require mixed-mode
systems.
--Mark
> Frans.
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
next prev parent reply other threads:[~2011-06-21 14:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-21 12:14 Multilib Development Update Richard Purdie
2011-06-21 12:28 ` Koen Kooi
2011-06-21 13:31 ` Richard Purdie
2011-06-21 13:02 ` Frans Meulenbroeks
2011-06-21 13:30 ` Richard Purdie
2011-06-21 13:33 ` Eric Bénard
2011-06-21 16:43 ` Khem Raj
2011-06-21 17:00 ` Richard Purdie
2011-06-21 14:35 ` Mark Hatle [this message]
2011-06-21 14:32 ` Khem Raj
2011-06-21 14:51 ` Mark Hatle
2011-06-29 9:10 ` [Multilib] a problem of SHLIBSDIR Lu, Lianhao
2011-06-29 9:49 ` Richard Purdie
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=4E00AC33.6080500@windriver.com \
--to=mark.hatle@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
/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