All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: [PATCH] Revert "spl: Drop bd_info in the data section"
Date: Tue, 13 Apr 2021 06:44:37 +1200	[thread overview]
Message-ID: <CAPnjgZ2_mUepmzn=f7m3Jx0RACQDre4Wvsd3ye6vsHFw4hioEA@mail.gmail.com> (raw)
In-Reply-To: <20210412183800.GA1310@bill-the-cat>

Hi Tom,

On Tue, 13 Apr 2021 at 06:38, Tom Rini <trini@konsulko.com> wrote:
>
> On Tue, Apr 13, 2021 at 06:26:08AM +1200, Simon Glass wrote:
> > Hi Tom,
> >
> > On Tue, 13 Apr 2021 at 06:18, Tom Rini <trini@konsulko.com> wrote:
> > >
> > > On Tue, Apr 13, 2021 at 05:49:19AM +1200, Simon Glass wrote:
> [snip]
> > > > As to a weak function, what would the default behaviour be? If we can
> > > > define that, then it would be better IMO.
> > > >
> > > > When we try to refactor things, weak functions and undefined (or
> > > > arch-specific behaviour) can really make things tough.
> > >
> > > Well, what was the problem you were trying to solve here?  I assumed
> > > there was a case where things actively broke, with the previous design,
> > > and it's not just the 64byte savings in some cases.  But is it?
> >
> > Yes the region of memory is not writable, so must be allocated at runtime.
>
> Where, on x86?  Some ARM cases?  That's one of the other things to sort
> out here.

Yes, on coral and likely newer things to come...For ARM I don't know
of any such problems.

Regards,
Simon

  reply	other threads:[~2021-04-12 18:44 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-08 16:56 [PATCH] Revert "spl: Drop bd_info in the data section" Alexandru Gagniuc
2021-04-08 23:55 ` Simon Glass
2021-04-09 19:20   ` Alex G.
2021-04-09 20:24     ` Adam Ford
2021-04-09 20:53       ` Tom Rini
2021-04-10  0:29         ` Tim Harvey
2021-04-12 13:25           ` Tom Rini
2021-04-12 13:51             ` Alex G.
2021-04-12 14:40               ` Tom Rini
2021-04-12 15:21                 ` Alex G.
2021-04-12 16:26                   ` Tom Rini
2021-04-12 17:49                     ` Simon Glass
2021-04-12 18:18                       ` Tom Rini
2021-04-12 18:26                         ` Simon Glass
2021-04-12 18:38                           ` Tom Rini
2021-04-12 18:44                             ` Simon Glass [this message]
2021-04-16 20:40                               ` Tim Harvey
2021-04-16 23:16                                 ` Adam Ford
2021-04-19  2:26                                   ` Alex G.
2021-04-19 15:32                       ` Tom Rini
2021-04-19 17:33 ` Tom Rini
2021-04-20 14:17 xiaobo

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='CAPnjgZ2_mUepmzn=f7m3Jx0RACQDre4Wvsd3ye6vsHFw4hioEA@mail.gmail.com' \
    --to=sjg@chromium.org \
    --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 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.