From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] arch: add support for OpenRISC architecture
Date: Tue, 24 Jan 2017 23:38:08 +1300 [thread overview]
Message-ID: <20170124233808.59865462@free-electrons.com> (raw)
In-Reply-To: <20170108084639.GW1913@waldemar-brodkorb.de>
Hello,
On Sun, 8 Jan 2017 09:46:39 +0100, Waldemar Brodkorb wrote:
> > I'm wondering if all Binutils version (2.25.1, 2.26.1 and 2.27) can be used on
> > openRISC? Have you considered to use the openrisc fork [1] ?
>
> Thanks for your feedback. Yes all binutils version are working fine,
> I just double checked now. So there is no need to use the github
> version for binutils. There is no Linux gdb support, yet.
> You can't use gdbserver or gdb native for now.
> You could use gdb to debug bare metal code.
Romain made numerous other comments in his review. Could you reply to
the other comments he made?
Also, could you resend an updated version that takes into account the
comments from Romain (possibly by adjusting the commit log to explain
which gcc versions, binutils versions, gdb features, etc. are
supported), and also by splitting the thing into two patches:
- one adding the architecture/toolchain support
- one adding the qemu based defconfig
Thanks a lot!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2017-01-24 10:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-07 8:48 [Buildroot] [PATCH] arch: add support for OpenRISC architecture Waldemar Brodkorb
2017-01-07 23:09 ` Romain Naour
2017-01-08 8:46 ` Waldemar Brodkorb
2017-01-24 10:38 ` Thomas Petazzoni [this message]
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=20170124233808.59865462@free-electrons.com \
--to=thomas.petazzoni@free-electrons.com \
--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