public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marek.vasut@gmail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] ARM: Generic cache ops skeleton
Date: Sun, 6 Nov 2011 19:07:29 +0100	[thread overview]
Message-ID: <201111061907.30014.marek.vasut@gmail.com> (raw)
In-Reply-To: <201111061303.12677.vapier@gentoo.org>

> On Sunday 06 November 2011 07:39:56 Marek Vasut wrote:
> > > On Saturday 05 November 2011 21:16:23 Marek Vasut wrote:
> > > > This patch should allow a CPU to register it's own cache ops. This
> > > > shall allow multiple CPUs with different cache handlings to be
> > > > supported.
> > > 
> > > sorry, what's the point ?  this would make sense if you wanted to build
> > > one u- boot image to run on multiple SoCs, but since that doesn't make
> > > sense, i don't see what this patch gets you.
> > 
> > Well that's the ultimate goal, isn't it ...
> 
> is it actually ?  i must have missed the memo.
> 
> support for multiple-SoC-support-in-a-single-image shouldn't bloat the
> single SoC case.  this code seems to do just that.  so it sounds like you
> should find a CONFIG name for this setup and start putting everything
> behind that.

That's a good point indeed. The other question is, if gcc4.6's LTO won't fix 
that for us. Surely enough though, we can't rely on that.
> 
> maybe something like CONFIG_SYS_MULTI_SOC.

Yea

> -mike

M

  reply	other threads:[~2011-11-06 18:07 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-06  1:16 [U-Boot] [PATCH] ARM: Generic cache ops skeleton Marek Vasut
2011-11-06  8:36 ` Mike Frysinger
2011-11-06 12:39   ` Marek Vasut
2011-11-06 18:03     ` Mike Frysinger
2011-11-06 18:07       ` Marek Vasut [this message]
2011-11-06 19:29         ` Simon Glass
2011-11-07  1:09           ` Mike Frysinger
2011-11-07  3:10             ` Simon Glass
2011-11-07 12:36           ` Albert ARIBAUD
2011-11-07  1:03         ` Mike Frysinger
2011-11-07 12:21 ` Albert ARIBAUD

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=201111061907.30014.marek.vasut@gmail.com \
    --to=marek.vasut@gmail.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