From: Nils Faerber <nils.faerber@kernelconcepts.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: MIPS32 big endian support?
Date: Tue, 21 Nov 2006 12:57:28 +0100 [thread overview]
Message-ID: <4562E9A8.4090400@kernelconcepts.de> (raw)
In-Reply-To: <20061121121036.51999b8a.Richard.How@einfosolutions.com>
Richard How schrieb:
> On Mon, 20 Nov 2006 13:25:04 +0100
> Nils Faerber <nils.faerber@kernelconcepts.de> wrote:
>> Has anyone already experience with OE and MIPS32 big endian configurations?
>> I have a board here which runs big endian for which I might want to
>> create a config for toolchain (SDK) and distribution...
>>
>> So if anyone has tried that already I would be happy to read a " yes,
>> works like a charm!" ;)
>
> Hi Nils, works like a charm :) I have MIPS32 big endian development board
> and have succeeded with bitbake meta-gpe, FBReader, sylpheed and
> epdfview. Still awaiting full size screen and touch panel so I can't test
> thoroughly yet, but I have ssh-ed to the board and run GPE apps
> successfully.
Cool!
Which distribution and machine config did you use? I did not find any
big endian configs in standard OpenEmbedded...
Did you use uclibc? Gcc compile failed with uclibc and I had to add two
minor patches...
> Regards
> Richard
Cheers
nils faerber
--
kernel concepts GbR Tel: +49-271-771091-12
Dreisbachstr. 24 Fax: +49-271-771091-19
D-57250 Netphen Mob: +49-176-21024535
--
next prev parent reply other threads:[~2006-11-21 12:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 12:25 MIPS32 big endian support? Nils Faerber
2006-11-21 1:40 ` Richard How
2006-11-21 11:57 ` Nils Faerber [this message]
2006-11-22 1:05 ` Richard How
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=4562E9A8.4090400@kernelconcepts.de \
--to=nils.faerber@kernelconcepts.de \
--cc=openembedded-devel@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 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.