From: Ivan Gorinov <ivan.gorinov@intel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] x86: enable cpu-specific functions for x86_64 target
Date: Wed, 30 May 2018 10:53:54 -0700 [thread overview]
Message-ID: <20180530175354.GA8536@intel.com> (raw)
In-Reply-To: <CAPnjgZ2=jVMbBZFf-oyNBtDB_QwgzET3btbnzi7bysJgjsMtNw@mail.gmail.com>
On Sat, May 26, 2018 at 06:53:40PM -0600, Simon Glass wrote:
> Hi Ivan,
>
> On 25 May 2018 at 16:00, Ivan Gorinov <ivan.gorinov@intel.com> wrote:
> > Add __weak prefix to the following functions to allow override:
> > misc_init_r(), checkcpu(), print_cpuinfo().
> >
> > Signed-off-by: Ivan Gorinov <ivan.gorinov@intel.com>
> > ---
> > arch/x86/cpu/x86_64/cpu.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
> >
> > diff --git a/arch/x86/cpu/x86_64/cpu.c b/arch/x86/cpu/x86_64/cpu.c
> > index 18b3e94..6f14efc 100644
> > --- a/arch/x86/cpu/x86_64/cpu.c
> > +++ b/arch/x86/cpu/x86_64/cpu.c
> > @@ -59,17 +59,17 @@ int x86_mp_init(void)
> > return 0;
> > }
> >
> > -int misc_init_r(void)
> > +__weak int misc_init_r(void)
> > {
> > return 0;
> > }
> >
> > -int checkcpu(void)
> > +__weak int checkcpu(void)
> > {
> > return 0;
> > }
> >
> > -int print_cpuinfo(void)
> > +__weak int print_cpuinfo(void)
> > {
> > return 0;
> > }
> > --
> > 2.7.4
> >
>
> We should do with with a different CPU driver I think. What exactly is
> the problem?
When I change a Minnowboard configuration (baytrail) to run in 64-bit mode,
there are two conflicting definitions of misc_init_r():
arch/x86/cpu/x86_64/cpu.c
board/intel/minnowmax/minnowmax.c
On other CPU models, functions checkcpu() and print_cpuinfo() conflict with
model-specific definitions for Tangier, Ivy Bridge, Broadwell, Quark.
prev parent reply other threads:[~2018-05-30 17:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-25 22:00 [U-Boot] [PATCH] x86: enable cpu-specific functions for x86_64 target Ivan Gorinov
2018-05-27 0:53 ` Simon Glass
2018-05-28 12:01 ` Andy Shevchenko
2018-05-30 17:53 ` Ivan Gorinov [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=20180530175354.GA8536@intel.com \
--to=ivan.gorinov@intel.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