public inbox for linux-parisc@vger.kernel.org
 help / color / mirror / Atom feed
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Chen Gang <gang.chen@asianux.com>
Cc: "James E.J. Bottomley" <jejb@parisc-linux.org>,
	Helge Deller <deller@gmx.de>,
	Parisc List <linux-parisc@vger.kernel.org>
Subject: Re: [PATCH] parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000'
Date: Wed, 24 Jul 2013 07:00:43 -0700	[thread overview]
Message-ID: <1374674443.4634.3.camel@dabdike> (raw)
In-Reply-To: <51EF8C52.50403@asianux.com>


On Wed, 2013-07-24 at 16:12 +0800, Chen Gang wrote:
> For server, 64-bit kernel is widely used and '64BIT' have been alread=
y
> as the default option of a server.
>=20
> 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.  You
apparent request doesn't match the code below.

> Or when use cross-compiler 'hppa64-linux-gnu-gcc' with allmodconfig, =
it
> will report BUILD_BUG_ON:
>=20
>   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__compiletime_=
assert_581=E2=80=99 declared with attribute error: BUILD_BUG_ON failed:=
 PTE_ENTRY_SIZE !=3D sizeof(pte_t)

This shows you're using a buggy compiler.  PTE_OFFSET_SIZE is generated
as part of the build process, so you need a correct compiler.

> Signed-off-by: Chen Gang <gang.chen@asianux.com>
> ---
>  arch/parisc/Kconfig |    2 +-
>  1 files changed, 1 insertions(+), 1 deletions(-)
>=20
> 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 in 3=
2
bit mode it does make the question appear, since PA7xxx are 32 bit only=
=2E

James


--
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

  parent reply	other threads:[~2013-07-24 14:00 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 ` James Bottomley [this message]
2013-07-25  0:37   ` [PATCH] parisc: Kconfig: use 'PA8X00' as the default choise instead of 'PA7000' Chen Gang F T
2013-07-26 20:08     ` Helge Deller
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=1374674443.4634.3.camel@dabdike \
    --to=james.bottomley@hansenpartnership.com \
    --cc=deller@gmx.de \
    --cc=gang.chen@asianux.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