From: Thomas Petazzoni via buildroot <buildroot@buildroot.org>
To: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
Cc: ARC Buildroot mailing list <arc-buildroot@synopsys.com>,
"buildroot@buildroot.org" <buildroot@buildroot.org>
Subject: Re: [Buildroot] ARC support in Buildroot
Date: Sat, 12 Aug 2023 10:38:06 +0200 [thread overview]
Message-ID: <20230812103806.2a4efc58@windsurf> (raw)
In-Reply-To: <DS7PR12MB904183FEC62ABB8A5A372E65A110A@DS7PR12MB9041.namprd12.prod.outlook.com>
On Fri, 11 Aug 2023 22:34:27 +0000
Alexey Brodkin <Alexey.Brodkin@synopsys.com> wrote:
> I'd say in coming weeks as I already started to work on clean-up and
> preparing for submission of first patches. In that sense I may handle that myself.
> One question to you though, if you prefer to have 2 patches:
> 1. Remove ARC-specific GCC & Binutils
> 2. Introduce ARCv3-specific tools: GCC, Binutils & glibc (uClibc is already upstreamed)
Are the ARCv3-specific tools going to be different than the
ARC-specific tools?
I think it could go like this:
- Update ARC-specific tools to newer versions (one patch)
- Add ARCv3 (one patch)
- Make ARC-specific tools only available for ARCv3 (one patch)
How does that sound?
Thomas
--
Thomas Petazzoni, co-owner and CEO, Bootlin
Embedded Linux and Kernel engineering and training
https://bootlin.com
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
prev parent reply other threads:[~2023-08-12 8:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 20:03 [Buildroot] ARC support in Buildroot Thomas Petazzoni via buildroot
2023-08-02 21:20 ` Alexey Brodkin via buildroot
2023-08-02 22:12 ` Thomas Petazzoni via buildroot
2023-08-03 7:59 ` Alexey Brodkin via buildroot
2023-08-06 20:51 ` Thomas Petazzoni via buildroot
2023-08-06 21:10 ` Thomas Petazzoni via buildroot
2023-08-11 20:00 ` Arnout Vandecappelle via buildroot
2023-08-11 22:25 ` Thomas Petazzoni via buildroot
2023-08-11 22:34 ` Alexey Brodkin via buildroot
2023-08-12 8:38 ` Thomas Petazzoni via buildroot [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=20230812103806.2a4efc58@windsurf \
--to=buildroot@buildroot.org \
--cc=Alexey.Brodkin@synopsys.com \
--cc=arc-buildroot@synopsys.com \
--cc=thomas.petazzoni@bootlin.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox