From: sbranden@broadcom.com (Scott Branden)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] kconfig: add CPU endian selection beconfig and leconfig
Date: Fri, 27 Nov 2015 15:45:57 -0800 [thread overview]
Message-ID: <5658EB35.3050707@broadcom.com> (raw)
In-Reply-To: <4689388.tNd2tB57aZ@wuerfel>
Hi Arnd,
Thanks for comment - I forgot to directly add you to CC list so was
going to add you in a couple days if you didn't find this patch proposal.
Response below.
On 15-11-27 07:59 AM, Arnd Bergmann wrote:
> On Thursday 26 November 2015 11:59:55 Scott Branden wrote:
>> @@ -151,6 +159,8 @@ help:
>> @echo ' kvmconfig - Enable additional options for kvm guest kernel support'
>> @echo ' xenconfig - Enable additional options for xen dom0 and guest kernel support'
>> @echo ' tinyconfig - Configure the tiniest possible kernel'
>> + @echo ' beconfig - Update current config to use big endian CPU'
>> + @echo ' leconfig - Update current config to use little endian CPU'
>>
>>
>
> Most architectures don't actually support picking the endianess, I think
> it would be better to keep this architecture specific in some form. If we
> limit it to ARM/ARM64, we might not need the leconfig target at all, because
> that is the default for all defconfig files in the kernel aside from ixp4xx,
> which we can probably ignore here.
Yes, I thought about placing le.config in arm64/configs. Then I would
need it in arm/configs also.
CONFIG_CPU_BIG_ENDIAN is currently used by arc, sh, c6x, powerpc, arm,
arm64, and mips. Then the next architecture comes along.
So to have the same feature on those architectures they would also need
le.config in their configs directory.
running "make leconfig" or "make beconfig" on architectures that do not
support CPU_BIG_ENDIAN has no harmful side affect other than the
endianness selection will not change.
For these reasons placing the functionality in kernel/configs alongside
xen.config seemed like the sensible thing to do. kernel/configs seems
like a very good place to add more .config selection options to as well.
Of course, whatever method is selected to switch between big and little
endian sharing a single defconfig I'm open to.
>
> Arnd
>
Thanks for comment.
Scott
next prev parent reply other threads:[~2015-11-27 23:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 19:59 [PATCH 0/1] kconfig: add CPU endian selection beconfig and leconfig Scott Branden
2015-11-26 19:59 ` [PATCH 1/1] " Scott Branden
2015-11-27 15:59 ` Arnd Bergmann
2015-11-27 23:45 ` Scott Branden [this message]
2015-11-27 18:39 ` Florian Fainelli
2015-11-27 23:49 ` Scott Branden
2015-11-30 19:26 ` Florian Fainelli
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=5658EB35.3050707@broadcom.com \
--to=sbranden@broadcom.com \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).