public inbox for gentoo-embedded@lists.gentoo.org
 help / color / mirror / Atom feed
From: wireless <wireless@tampabay.rr.com>
To: gentoo-embedded@lists.gentoo.org
Subject: Re: [gentoo-embedded] MIPS32 Rootfs
Date: Thu, 11 Feb 2010 13:00:36 -0500	[thread overview]
Message-ID: <4B7445C4.8070800@tampabay.rr.com> (raw)
In-Reply-To: <f861ec6f1002110858o531db70cu3b5a45f63c7319a2@mail.gmail.com>

Manuel Lauss wrote:
> Hi,
> 
> On Thu, Feb 11, 2010 at 3:17 PM, wireless <wireless@tampabay.rr.com> wrote:
>> Do you have a listing of 32 bit mips dev boards your
>> codebase works with?
> 
> It should work on any little-endian MIPS32 core.  As I explained in the
> original posting, my target systems are the "Alchemy" line which are
> FPU-less MIPS32r1 cores. 


I should have stated that I know little of MIPS arch. I do
not know the differences, subtle  or published between the
M14K and the Mips32 (vanilla() cores. I mostly asked because
I know of several folks that are looking for some form of
open source embedded linux for the Microchip 32 bit
processors. Since you indicate that it should work, I'll
send  these folks to your links.



> The whole system is built with a softfloat
> toolchain to avoid the in-kernel CP1 emulator (which is sloooow).
> 
> I'll keep updating it; so if you need any other apps or use flags set then
> I'll he be more than happy to provide them (I let a few boards compile stuff
> overnight as a stability test).
> 
> Thanks,
>         Manuel Lauss




thanks,
James





  reply	other threads:[~2010-02-11 18:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10 17:34 [gentoo-embedded] MIPS32 Rootfs Manuel Lauss
2010-02-11 11:03 ` Dennis.Yxun
2010-02-11 14:17 ` wireless
2010-02-11 14:30   ` Dennis.Yxun
2010-02-11 16:58   ` Manuel Lauss
2010-02-11 18:00     ` wireless [this message]
2010-02-11 18:09       ` Manuel Lauss

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=4B7445C4.8070800@tampabay.rr.com \
    --to=wireless@tampabay.rr.com \
    --cc=gentoo-embedded@lists.gentoo.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