From: Jonathan Liu <net147@gmail.com>
To: "Burton, Ross" <ross.burton@intel.com>
Cc: Darren Hart <dvhart@linux.intel.com>,
"poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH] genericx86: tune for i586 instead of atom
Date: Thu, 05 Sep 2013 00:28:50 +1000 [thread overview]
Message-ID: <522743A2.6070609@gmail.com> (raw)
In-Reply-To: <CAJTo0LZt4Wmre2XOjLtTFPnmOOMvC+x0Gu-EDEQSFB_F_XkFFw@mail.gmail.com>
On 5/09/2013 12:25 AM, Burton, Ross wrote:
> On 4 September 2013 13:54, Bruce Ashfield <bruce.ashfield@windriver.com> wrote:
>>> I have confirmed it is CONFIG_MATOM=y that was causing the boot issue.
>> That would definitely make a difference. If you are using the genericx86
>> PC, the default tuning was atom+ IIRC (a line has to be drawn somewhere),
>> and you can discuss that with the Intel guys.
>>
>> But you can easily carry a configuration fragment in your own layer that
>> disables that option if you want that same BSP to work on your platform.
> I'd be inclined to say that the line for genericx86 is "atom onwards"
> and Pentium is sufficiently different to justify its own BSP.
>
> Ross
Is CONFIG_MATOM=y being used for genericx86?
Using CONFIG_MATOM=y with Linux 3.10 seems to require MOVBE instruction
which is only available on Intel Atom...
Regards,
Jonathan
next prev parent reply other threads:[~2013-09-04 14:41 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-04 1:43 [PATCH] genericx86: tune for i586 instead of atom Jonathan Liu
2013-09-04 3:23 ` Bruce Ashfield
2013-09-04 3:30 ` Jonathan Liu
2013-09-04 3:44 ` Bruce Ashfield
2013-09-04 3:56 ` Jonathan Liu
2013-09-04 4:12 ` Jonathan Liu
2013-09-04 7:46 ` Jonathan Liu
2013-09-04 12:54 ` Bruce Ashfield
2013-09-04 14:25 ` Burton, Ross
2013-09-04 14:28 ` Jonathan Liu [this message]
2013-09-04 14:49 ` Burton, Ross
2013-09-04 4:20 ` Jonathan Liu
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=522743A2.6070609@gmail.com \
--to=net147@gmail.com \
--cc=dvhart@linux.intel.com \
--cc=poky@yoctoproject.org \
--cc=ross.burton@intel.com \
/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.