From: Adam Carter <adamcarter3@gmail.com>
To: "gentoo-user@lists.gentoo.org" <gentoo-user@lists.gentoo.org>
Subject: Re: [gentoo-user] Missing CPU options in make menuconfig
Date: Thu, 21 Jul 2016 12:56:14 +1000 [thread overview]
Message-ID: <CAC=wYCE3q57bqPtHS116_nJHFsR_wUtNQOGB14A8Vc41an4Skw@mail.gmail.com> (raw)
In-Reply-To: <478808c6-5aba-53d3-704d-a67ce606dca5@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2857 bytes --]
The experimental use flag turns on the other arch's in gentoo-sources.
Perhaps that will help identify which is the relevant patch?
On Thu, Jul 21, 2016 at 11:07 AM, Fernando Rodriguez <cyklonite@gmail.com>
wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA256
>
> On 07/20/2016 07:38 PM, Fernando Rodriguez wrote:
> > On 07/20/2016 02:54 PM, Neil Bothwick wrote:
> >> On Wed, 20 Jul 2016 14:33:04 -0400, Fernando Rodriguez wrote:
> >
> >>> I don't use gentoo sources but I remember reading about gentoo patches
> >>> for processor specific optimizations and being tempted to try them. Is
> >>> it possible that is what you're refering to?
> >>>
> >>> The vanilla sources only shows 5 choices for me on amd64:
> >>> (X) Opteron/Athlon64/Hammer/K8
> >>> ( ) Intel P4 / older Netburst based Xeon
> >>> ( ) Core 2/newer Xeon
> >>> ( ) Intel Atom
> >>> ( ) Generic-x86-64
> >>>
> >>> And it shows a different set of options when I run it on an x86
> machine.
> >
> >> That's what I get here, but help lists all the ones I get in
> >> gentoo-sources, apart from MNATIVE, which indicates to me that those
> >> options should be available, once I work out how to switch them on.
> >
> > Disable CONFIG_64BIT and you'll get them all.
>
> And for future references, here's how I found out:
>
> 1. On the sources where you have the options highlight one of them and
> press ? (help). You'll see X86_32 under "Depends on:".
>
> 2. Hit ESC twice and then twice again to return to a menu with
> search functionality. Then type /X86_32 and hit enter. You'lll see that
> the option depends on !64BIT, so you need to disable CONFIG_64BIT for
> X86_32 to be available.
>
> 3. After disabling CONFIG_64BIT on the kernel where the options where
> missing
> I searched X86_32 again and this time it has [=y] next to it so it came
> on automatically and the options showed up but for some options you
> need to
> enable manually after enabling the dependencies.
>
> - --
>
> Fernando Rodriguez
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2
>
> iQIcBAEBCAAGBQJXkCBTAAoJEPbOFX/5UlwcR8sP/2kwuumtlSymDTyPj4CFS0Q7
> noRYWAzutRKDb6GTrobwB5zDVwJTUORuoRE+XXQFeVWRQhjSI2wsaRGL/Cn8duhW
> QTdgtvrV8T6bdcjftVbeExFvKTDrMXUAEbd+XyRObj7r13454GtYdgOIpktxwDrH
> D2a3bR2NX7fMxFfSBk4osv3UkoL3xM201MXwUhZgOtTaX/DAw12gSg1ljTJ8UV7O
> snu+Td9YHcoohrmBpN4yX7uaBL4LnZZnBv59TZekXDv6DGyc70QZO97gNGOvG2SC
> www7wsM28/hrKqeQI5CNcpl6UvibQGndThld7y1Y5YeByHEBHt31yZp97g1Ira5T
> 2iadpgoSFiMaCy2+BXfIjktLbIe9E5vH15dVMKxuWazrf7Zf9XszxuU6nZE3RiN5
> J9ytAwL/RESjQwB11p3LLf/1zgyYAtIzt/N7QrbvJmHmjj7WyRMK6QCLJsew7izl
> g/Hjsqvq73QvNdRfjbxTK19sOO1clpJfAdvyHELR+TVvJDAooWFj/8KBfSGCimkv
> 6bVnDFKIB/ov/o3ZhX121FHq/zH6SH/CxbVozIuTTiowumgftgPMapEiXRIvp/+S
> ar8dcUF+xiRcKOmx4mBctOxQQ6R0z0o1oWItyjioyB0Rb09kMVjNCQuvq9IpPzLn
> kl+C7ndrh4etobK9nv2A
> =fojV
> -----END PGP SIGNATURE-----
>
>
[-- Attachment #2: Type: text/html, Size: 3611 bytes --]
next prev parent reply other threads:[~2016-07-21 2:56 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-20 17:50 [gentoo-user] Missing CPU options in make menuconfig Neil Bothwick
2016-07-20 18:03 ` Alexander Kapshuk
2016-07-20 18:29 ` [gentoo-user] " Holger Hoffstätte
2016-07-21 7:20 ` Neil Bothwick
2016-07-21 12:48 ` Andrew Savchenko
2016-07-20 18:33 ` [gentoo-user] " Fernando Rodriguez
2016-07-20 18:54 ` Neil Bothwick
2016-07-20 23:38 ` Fernando Rodriguez
2016-07-21 1:07 ` Fernando Rodriguez
2016-07-21 2:56 ` Adam Carter [this message]
2016-07-21 7:18 ` Neil Bothwick
2016-07-21 7:17 ` Neil Bothwick
2016-07-21 10:56 ` Fernando Rodriguez
2016-07-21 10:59 ` Fernando Rodriguez
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='CAC=wYCE3q57bqPtHS116_nJHFsR_wUtNQOGB14A8Vc41an4Skw@mail.gmail.com' \
--to=adamcarter3@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/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