From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] common/board_f: make board_init_f_mem() independent on !CONFIG_X86
Date: Mon, 23 Mar 2015 21:17:15 +0000 [thread overview]
Message-ID: <1427145435.2201.10.camel@synopsys.com> (raw)
In-Reply-To: <CAPnjgZ3a4GUpChf778V=fc7UUMnvyWTkKe1aHwkQshD-z24oUg@mail.gmail.com>
Hi Simon,
On Mon, 2015-03-23 at 11:26 -0600, Simon Glass wrote:
> On 23 March 2015 at 10:40, Alexey Brodkin <Alexey.Brodkin@synopsys.com> wrote:
> > Hi Tom, Simon,
> >
> > On Mon, 2015-03-16 at 11:03 +0300, Alexey Brodkin wrote:
> >> Even though board_init_f_mem() is not used on x86 today there's no
> >> reason to not use it in the future.
> >>
> >> Moreover board_init_f_mem() has nothing to do with any particular
> >> architecture so move it away from #else /* CONFIG_X86 */
> >>
> >> Signed-off-by: Alexey Brodkin <abrodkin@synopsys.com>
> >> Cc: Simon Glass <sjg@chromium.org>
> >> Cc: Tom Rini <trini@ti.com>
> >
> > Any comments on this one?
> > This is a prerequisite for ARC updates so would be good to have it
> > merged sometime soon.
>
> I must have missed something as it did not seem to change anything for ARC.
I meant this series -
http://lists.denx.de/pipermail/u-boot/2015-March/208179.html
In particular here I wanted to use board_init_f_mem():
http://lists.denx.de/pipermail/u-boot/2015-March/208183.html
Note that in the previous patch
http://lists.denx.de/pipermail/u-boot/2015-March/208182.html I re-used
former X86-only code sections in common/board_f.c - that's why I did
need board_init_f_mem() to be separated from #ifdef CONFIG_X86 #else - I
wanted to use both branches :)
> This breaks building on x86 though, so we can't take this patch as is. E.g.:
>
> x86: + crownbay
> +common/board_f.c: In function ?board_init_f_mem?:
> +common/board_f.c:1092:5: error: lvalue required as left operand of assignment
> + gd = (struct global_data *)top;
> + ^
That's why I wanted your opinion :)
Sandbox didn't show any problems and I didn't do makeall.
Because in case of X86 "gd" is an alias to get_fs_gd_ptr() we cannot do
such assignments.
So then we'll need to keep board_init_f_mem() disabled for X86 like
that:
--->8---
#ifndef CONFIG_X86
ulong board_init_f_mem(ulong top)
{
/* Leave space for the stack we are running with now */
top -= 0x40;
top -= sizeof(struct global_data);
top = ALIGN(top, 16);
gd = (struct global_data *)top;
memset((void *)gd, '\0', sizeof(*gd));
#ifdef CONFIG_SYS_MALLOC_F_LEN
top -= CONFIG_SYS_MALLOC_F_LEN;
gd->malloc_base = top;
#endif
return top;
}
#endif
--->8---
Do you think that's OK? If so I'll send v2 shortly.
-Alexey
next prev parent reply other threads:[~2015-03-23 21:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-16 8:03 [U-Boot] [PATCH] common/board_f: make board_init_f_mem() independent on !CONFIG_X86 Alexey Brodkin
2015-03-23 16:40 ` Alexey Brodkin
2015-03-23 17:26 ` Simon Glass
2015-03-23 21:17 ` Alexey Brodkin [this message]
2015-03-23 21:18 ` Simon Glass
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=1427145435.2201.10.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 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.