All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] nds32: toolchains for building ?
Date: Thu, 10 Nov 2011 12:12:46 -0500	[thread overview]
Message-ID: <201111101212.47902.vapier@gentoo.org> (raw)
In-Reply-To: <CACCg+XO3Mnc-oG4qtw6sC7Mar9W5aGP9ciqOFAQHRGnn-CZWgw@mail.gmail.com>

On Thursday 10 November 2011 12:01:46 Macpaul Lin wrote:
> 2011/11/11 Mike Frysinger <vapier@gentoo.org>:
> > what's the difference between v0 v1 v1f ?
> 
> It should be described in detail in the README, however,
> the v0 toolchain will be phased out in recent.
> So it becomes not so important. XD
> 
> The version numbers v0, v1, v1f, v2, v2f, v3, and v3m are meant to
> instruction set (ISA) versions.
> Currently, the first SoC ag101 can be adapted with v0 toolchain only.
> The second SoC is soft core ag101p, which can run the most compatible
> v1 instruction sets.
> While v1f means v1 ISA + floating point ISA.
> Other details of v2 and v3 ISA should be able to be found though url
> http://www.andestech.com/
> 
> However, I don't know where exactly url of the document is. :p
> Please use v0 toolchain to play with adp-ag101 board.
> Although you can use v1 toolchain to build the binary for ag101 SoC,
> it couldn't be booted up.
> For the backward compatibility, of course, you can use v0 and v1
> toolchain to build binary for ag101p SoC.
> Both of the binaries could run correctly.

so the ISA version only affects the generated libraries right ?  i can still 
use any of the compilers to output any ISA version ?

i grabbed the v1f and it seems to build the one nds32 board in the tree fine.

i ripped it down to the min needed for u-boot, so people can grab the 4.3MiB:
	http://dev.gentoo.org/~vapier/u-boot/nds32.tar.xz
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20111110/49b28397/attachment.pgp 

  reply	other threads:[~2011-11-10 17:12 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-03 17:58 [U-Boot] nds32: toolchains for building ? Mike Frysinger
2011-11-04  8:24 ` 馬克泡
2011-11-04 22:22   ` Mike Frysinger
2011-11-04 23:20     ` Mike Frysinger
2011-11-05  1:35       ` 馬克泡
2011-11-05 17:04         ` Mike Frysinger
2011-11-10  6:22           ` Macpaul Lin
2011-11-10 16:28             ` Mike Frysinger
2011-11-10 17:01               ` Macpaul Lin
2011-11-10 17:12                 ` Mike Frysinger [this message]
2011-11-11  2:01                   ` Macpaul Lin
2011-11-11  2:08                     ` Macpaul Lin
2011-11-11  2:42                     ` Mike Frysinger
2011-11-11  2:53                       ` Macpaul Lin

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=201111101212.47902.vapier@gentoo.org \
    --to=vapier@gentoo.org \
    --cc=u-boot@lists.denx.de \
    /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.