Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Gaisler sparc-leon
Date: Thu, 02 Sep 2010 23:50:37 +0200	[thread overview]
Message-ID: <87hbi7vmqa.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <20100902144444.cynij0yn3mw0ooc0@webmail.bluegenesis.com> (konrad@gaisler.com's message of "Thu, 02 Sep 2010 14:44:44 -0400")

>>>>> "konrad" == konrad  <konrad@gaisler.com> writes:

Hi Konrad,

 konrad> Hello everybody,
 konrad> Currently at Aeroflex Gaisler we are running a old
 konrad> Snapgear 2.0 dist. Now we are searching for a replacement
 konrad> and got from "Sam Ravnborg" <sam@ravnborg.org> the
 konrad> hint to use buildroot that we intend to switch to now. 
 konrad> Aeroflex Gaisler is marketing the OpenSource Leon3 processor
 konrad> (that is distributed as a vhdl model and can be synthesized
 konrad> by the user). The Leon3 processor is a fully SparcV8 conformant
 konrad> processor that support also a SRMMU. Linux is ported on
 konrad> it and the Leon Port is included in the recent kernels. 
 konrad> Currently I also try to submit patches for the Leon3 settings to
 konrad> GCC? and sent a copyleft assignment to FSF so I hope
 konrad> the Leon3 cpu will be in the 4.5.x toolchains soon. 

Ahh yes, I remember looking at Leon3 a number of years ago..

 konrad> From Sam Ravnborg I heard that there is the thought to
 konrad> take away the sparc port from buildroot, I would like to vote
 konrad> not doing so. In the future we plan to activly develop the Sparc
 konrad> branch of uclibc and buildroot, test and submit patches. 
 konrad> On Monday I'll submit 4.4.3 patch and sparc config settings patch
 konrad> to add a leon cpu build... 

The problem with Sparc was that noone was interested in maintaining it /
had access to hw to test stuff, and various issues with uClibc / gcc.

I have no issues keeping Sparc support if the situation changes, but
there isn't much sense in pretending to support Sparc if it doesn't
really work.

So I'll keep it for now and see what happens..

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2010-09-02 21:50 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-02 18:44 [Buildroot] Gaisler sparc-leon konrad at gaisler.com
2010-09-02 21:50 ` Peter Korsgaard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2010-09-03 13:13 konrad at gaisler.com
2010-09-03 14:50 ` Peter Korsgaard
2010-09-03 15:44   ` Michael S. Zick
2010-09-03 15:30 konrad at gaisler.com

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=87hbi7vmqa.fsf@macbook.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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