From: Julian Brown <julian@codesourcery.com>
To: Marek Vasut <marex@denx.de>
Cc: qemu-devel@nongnu.org, Sandra Loosemore <sandra@codesourcery.com>,
Chris Wulff <crwulff@gmail.com>,
Andrew Jenner <Andrew_Jenner@mentor.com>
Subject: Re: [Qemu-devel] [PATCH v3 1/2] Add generic Nios II board.
Date: Fri, 18 May 2018 21:16:48 +0100 [thread overview]
Message-ID: <20180518211648.5d849941@octopus> (raw)
In-Reply-To: <49dbe9f7-0558-12d4-363a-fe13099f86bd@denx.de>
On Fri, 18 May 2018 21:50:55 +0200
Marek Vasut <marex@denx.de> wrote:
> On 05/18/2018 09:23 PM, Julian Brown wrote:
> > This patch adds support for a generic MMU-less Nios II board that
> > can be used e.g. for bare-metal compiler testing. Nios II booting
> > is also tweaked so that bare-metal binaries start executing in RAM
> > starting at 0x00000000, rather than an alias at 0xc0000000, which
> > allows features such as unwinding to work when binaries are linked
> > to start at the beginning of the address space.
> >
> So why dont you just use the 10m50 GHRD for this , why do you need
> custom board ?
I think because we wanted a board with no MMU, since our startup code
doesn't support that. Maybe Andrew can confirm/deny?
Thanks,
Julian
next prev parent reply other threads:[~2018-05-18 20:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-18 19:23 [Qemu-devel] [PATCH v3 0/2] Nios II generic board config and semihosting support Julian Brown
2018-05-18 19:23 ` [Qemu-devel] [PATCH v3 1/2] Add generic Nios II board Julian Brown
2018-05-18 19:50 ` Marek Vasut
2018-05-18 20:16 ` Julian Brown [this message]
2018-05-21 9:46 ` Andrew Jenner
2018-05-18 19:23 ` [Qemu-devel] [PATCH v3 2/2] Add Nios II semihosting support Julian Brown
2018-05-18 19:52 ` Marek Vasut
2018-05-18 20:19 ` Julian Brown
2018-05-18 20:28 ` Marek Vasut
2018-05-18 21:35 ` Sandra Loosemore
2018-08-02 21:56 ` Sandra Loosemore
2018-08-13 1:03 ` Julian Brown
2018-05-18 19:49 ` [Qemu-devel] [PATCH v3 0/2] Nios II generic board config and " Marek Vasut
2018-05-18 22:33 ` no-reply
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=20180518211648.5d849941@octopus \
--to=julian@codesourcery.com \
--cc=Andrew_Jenner@mentor.com \
--cc=crwulff@gmail.com \
--cc=marex@denx.de \
--cc=qemu-devel@nongnu.org \
--cc=sandra@codesourcery.com \
/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.