public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: Helge Deller <deller@gmx.de>
To: Chen Gang F T <chen.gang.flying.transformer@gmail.com>
Cc: James Bottomley <James.Bottomley@HansenPartnership.com>,
	"James E.J. Bottomley" <jejb@parisc-linux.org>,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000'
Date: Fri, 26 Jul 2013 22:08:54 +0200	[thread overview]
Message-ID: <51F2D756.7040300@gmx.de> (raw)
In-Reply-To: <51F07332.6030908@gmail.com>

Hi Chen,

On 07/25/2013 02:37 AM, Chen Gang F T wrote:
> On 07/24/2013 10:00 PM, James Bottomley wrote:
>>
>> On Wed, 2013-07-24 at 16:12 +0800, Chen Gang wrote:
>>> For server, 64-bit kernel is widely used and '64BIT' have been alre=
ady
>>> as the default option of a server.
>>>
>>> So better to use 64-bit kernel as default choise instead of 32-bit
>>> kernel.
>>
>> I think this is irrelevant since we have defconfig for this.

I do have the same opinion.
It's not necessary.

=46urthermore, for a real 64 bit kernel you need to enable
CONFIG_64BIT not CONFIG_PA8X00.

> Hmm... but I still suggest when use 'allmodconfig' let 64-bit as the
> default choice (normally 64-bit is the default choice for servers).

Yeah, but we do support workstations as well.

>>> Or when use cross-compiler 'hppa64-linux-gnu-gcc' with allmodconfig=
, it
>>> will report BUILD_BUG_ON:
>>>
>>>   arch/parisc/mm/init.c: In function =E2=80=98mem_init=E2=80=99:
>>>   arch/parisc/mm/init.c:581:2: error: call to =E2=80=98__compiletim=
e_assert_581=E2=80=99 declared with attribute error: BUILD_BUG_ON faile=
d: PTE_ENTRY_SIZE !=3D sizeof(pte_t)
>>
>> This shows you're using a buggy compiler.  PTE_OFFSET_SIZE is genera=
ted
>> as part of the build process, so you need a correct compiler.
>>
>=20
> Hmm... It means the compiler assumes to build 64-bit code (hppa64), b=
ut
> our configuration is for 32-bit, they are mismatch.
>=20
> Maybe we can say hppa64-linux-gnu-gcc can not build the 32-bit parisc
> code (although it is not precise), but at least, it is not a real bug=
=2E

It's a fact:
hppa64-linux-gnu-gcc can *not* build the 32-bit parisc.
Only hppa-linux-gnu-gcc can build 32bit code.=20


> This contents wants to say: when use 'allmodconfig' for a server, we =
do
> not build a 64-bit server.
>=20
>=20
>>> Signed-off-by: Chen Gang <gang.chen@asianux.com>

Thanks for your patch, but:
NAK.

Helge

>>> ---
>>>  arch/parisc/Kconfig |    2 +-
>>>  1 files changed, 1 insertions(+), 1 deletions(-)
>>>
>>> diff --git a/arch/parisc/Kconfig b/arch/parisc/Kconfig
>>> index aa399a5..37bdecf 100644
>>> --- a/arch/parisc/Kconfig
>>> +++ b/arch/parisc/Kconfig
>>> @@ -111,7 +111,7 @@ menu "Processor type and features"
>>> =20
>>>  choice
>>>  	prompt "Processor type"
>>> -	default PA7000
>>> +	default PA8X00
>>
>> This doesn't require 64 bit: PA8xxx processors can operate happily i=
n 32
>> bit mode it does make the question appear, since PA7xxx are 32 bit o=
nly.
>>
>=20
> Yeah, 'PA8X00' can compitable with 32-bit, but it likes 64-bit, the
> following config files are for 'PA8X00':
>=20
>   a500_defconfig: for 64-bit
>   c3000_defconfig: for 32-bit
>   c8000_defconfig: for 64-bit
>   generic-64bit_defconfig: for 64-bit
>=20
> At least, we can say PA8xxx is a 64-bit processor for parisc, is it
> correct ?
>=20
> And for 'allmodconfig', if let 'PA8X00' as default choice, it will bu=
ild
> 64-bit kernel.
>=20
>=20
> Thanks.
>=20

--
To unsubscribe from this list: send the line "unsubscribe linux-parisc"=
 in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2013-07-26 20:08 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-24  8:12 [PATCH] parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000' Chen Gang
2013-07-24  8:27 ` [Suggestion] parisc: kernel: about section mismatch warning Chen Gang
2013-07-24 14:11   ` James Bottomley
2013-07-24 23:58     ` Chen Gang F T
2013-07-29  8:49       ` Chen Gang
2013-07-29 13:47         ` John David Anglin
2013-07-29 18:23           ` Helge Deller
2013-07-30  0:48           ` Chen Gang
2013-07-24 14:00 ` [PATCH] parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000' James Bottomley
2013-07-25  0:37   ` Chen Gang F T
2013-07-26 20:08     ` Helge Deller [this message]
2013-07-29  1:11       ` Chen Gang
2013-07-29  8:39         ` [Suggestion] parisc: about the warnings "unsigned expression < 0 is always false" Chen Gang

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=51F2D756.7040300@gmx.de \
    --to=deller@gmx.de \
    --cc=James.Bottomley@HansenPartnership.com \
    --cc=chen.gang.flying.transformer@gmail.com \
    --cc=jejb@parisc-linux.org \
    --cc=linux-parisc@vger.kernel.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