From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Please pull ARC changes
Date: Fri, 23 Mar 2018 13:38:48 +0000 [thread overview]
Message-ID: <1521812327.5434.12.camel@synopsys.com> (raw)
In-Reply-To: <20180323133356.GT4759@bill-the-cat.ec.rr.com>
Hi Tom,
On Fri, 2018-03-23 at 09:33 -0400, Tom Rini wrote:
> On Fri, Mar 23, 2018 at 01:23:53PM +0000, Alexey Brodkin wrote:
>
> > Hi Tom,
> >
> > This is the first batch of ARC changes for the next release.
> >
> > Here we:
> > 1. Significantly rework cache-related functionality.
> > In particular that fixes coherency problems in some corner-cases,
> > allows us to enable and disable caches in run-time and still
> > have properly running system, finally support execution from
> > real flash (before we used to run from DDR from the very beginning).
> >
> > 2. Remove string routines implemented in assembly.
> > That allows us to build and run U-Boot on wide range og ARC cores
> > with different configurations. I.e. whatever tuning is used on GCC's
> > command-line we'll get code for desired flavor of ARC.
> > Otherwise for each and every corner-case we would need to add ifdefs
> > in assembly code to accommodate missing instructions etc.
> >
> > 3. Get use of GCC's garbage collector which helps to slim-down resulting image
> > quite a bit.
> >
> > 4. Also now we may disable U-Boot self-relocation for ARC if needed either
> > by platform or for debugging purposes.
>
> FYI, all of the above would be really good to put into a signed tag,
> next time :)
Sure will do!
Do you want me to do it now as well?
> > P.S. Do you have an idea when RC1 is going to be cut?
> > We have some other pending changes and it's good to understand how much time
> > we have for finalization if we want [and we do want] to still squeeze it all
> > in the next release.
>
> Should be April 2nd, per the ReleaseCycle wiki page.
Thanks for pointing to this article - very useful indeed.
-Alexey
next prev parent reply other threads:[~2018-03-23 13:38 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-23 13:23 [U-Boot] Please pull ARC changes Alexey Brodkin
2018-03-23 13:33 ` Tom Rini
2018-03-23 13:38 ` Alexey Brodkin [this message]
2018-03-23 13:51 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2019-01-25 5:52 Alexey Brodkin
2019-01-27 3:50 ` Tom Rini
2018-12-03 11:32 Alexey Brodkin
2018-12-03 15:32 ` Tom Rini
2018-11-01 20:41 Alexey Brodkin
2018-11-02 20:30 ` Tom Rini
2018-10-15 10:22 Alexey Brodkin
2018-10-12 12:38 Alexey Brodkin
2018-10-05 14:10 Alexey Brodkin
2018-10-06 1:16 ` Tom Rini
2018-06-21 11:59 Alexey Brodkin
2018-06-21 18:21 ` Tom Rini
2018-06-18 9:29 Alexey Brodkin
2018-06-15 13:14 Alexey Brodkin
2018-06-16 2:34 ` Tom Rini
2018-05-24 13:09 Alexey Brodkin
2018-05-24 23:41 ` Tom Rini
2018-02-15 12:53 Alexey Brodkin
2018-02-15 19:07 ` Tom Rini
2018-01-19 15:08 Alexey Brodkin
2018-01-19 21:11 ` Tom Rini
2017-12-12 15:52 Alexey Brodkin
2017-12-12 15:58 ` Tom Rini
2017-12-11 8:43 Alexey Brodkin
2017-12-12 1:55 ` Tom Rini
2017-11-24 16:39 Alexey Brodkin
2017-11-24 21:33 ` Tom Rini
2017-06-29 16:39 Alexey Brodkin
2017-06-30 1:26 ` Tom Rini
2017-04-11 14:56 Alexey Brodkin
2017-04-11 15:55 ` Tom Rini
2017-03-31 19:12 Alexey Brodkin
2017-04-04 20:00 ` Tom Rini
2017-03-24 11:53 Alexey Brodkin
2017-03-24 17:37 ` Tom Rini
2016-09-16 11:30 Alexey Brodkin
2016-09-19 0:31 ` Tom Rini
2016-08-05 10:09 Alexey Brodkin
2016-08-06 2:09 ` Tom Rini
2016-07-04 8:49 Alexey Brodkin
2016-07-05 2:44 ` Tom Rini
2016-06-13 12:43 Alexey Brodkin
2016-06-19 14:08 ` Tom Rini
2016-04-21 17:11 Alexey Brodkin
2016-04-22 14:26 ` Tom Rini
2016-04-11 17:23 Alexey Brodkin
2016-04-12 2:27 ` Tom Rini
2016-02-20 8:22 Alexey Brodkin
2016-02-20 14:23 ` Tom Rini
2015-12-08 14:33 Alexey Brodkin
2015-12-08 15:00 ` Tom Rini
2015-11-17 21:41 Alexey Brodkin
2015-11-18 0:50 ` Tom Rini
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=1521812327.5434.12.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox