From: Mark Hatle <mark.hatle@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: tweaking insane.bbclass to handle MIPS SEAD-3?
Date: Thu, 18 Apr 2013 09:08:31 -0500 [thread overview]
Message-ID: <516FFE5F.7040901@windriver.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1304180833040.10184@oneiric>
On 4/18/13 7:38 AM, Robert P. J. Day wrote:
>
> students from a class of mine last year are currently playing with a
> MIPS SEAD-3:
>
> http://www.mips.com/products/development-kits/mips-sead-3/
>
> and asked for some assistance getting oe/yocto to build for that kit.
> they started with the routerstation pro content, and just wanted to
> reproduce the same rootfs to run on the SEAD-3 (they would use the
> provided u-boot and kernel for now). the biggest issue was changing
> the endianness of the build.
>
> got an email this morning, they have a working rootfs, i asked for
> details on everything they had to do, but for now, here's the final
> issue they dealt with:
>
> "Attached rootfs created for RS Pro, but with mips32el (little endian
> config) and soft floating point. I had to comment out the endianess
> check Python code from the insane.bbclass file to get the build to
> work."
I'm interested in what changes are required. Both mips and mipsel are defined
in the insane class. If you define 'mips', but end up building little endian,
you WILL get errors. But if the arch is defined as mipsel, then no errors
should be generated.
If the arch is 'mips32' and 'mips32el' then those are simply not defined at this
point. But before defining them, what is the difference between mips and mips32?
(I have no experience with this particular board, so I don't know what the
actual gcc configuration is for building functional software.)
> so if someone wants to adjust insane.bbclass to recognize and handle
> a SEAD-3, go for it. i'll post full details when i get them in case
> there was anything else relevant.
>
> rday
>
next prev parent reply other threads:[~2013-04-18 14:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-18 12:38 tweaking insane.bbclass to handle MIPS SEAD-3? Robert P. J. Day
2013-04-18 14:08 ` Mark Hatle [this message]
2013-04-18 14:25 ` Robert P. J. Day
2013-04-18 15:08 ` Mark Hatle
2013-04-18 15:44 ` Robert P. J. Day
2013-04-18 16:02 ` Mark Hatle
2013-04-18 16:07 ` Robert P. J. Day
2013-04-18 17:14 ` Robert P. J. Day
2013-04-19 9:36 ` Paul Eggleton
2013-04-19 10:53 ` Robert P. J. Day
2013-04-19 11:09 ` Paul Eggleton
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=516FFE5F.7040901@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