linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Rupert Eibauer <rupert@ces.ch>
To: Kumar Gala <kumar.gala@freescale.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: [PATCH][RFT] please use this one
Date: Fri, 21 Oct 2005 20:43:16 +0200	[thread overview]
Message-ID: <200510212043.18615.rupert@ces.ch> (raw)
In-Reply-To: <B34FF652-6E5D-437D-812C-763B2D10C7CA@freescale.com>

On Friday 21 October 2005 17:23, Kumar Gala wrote:
> 
> On Oct 21, 2005, at 10:11 AM, Rupert Eibauer wrote:
> 
> > On Friday 21 October 2005 16:28, Kumar Gala wrote:
> >
> >> The concept of PPC_HIGH_BATS is already some what handled with
> >> CPU_FTR_HAS_HIGH_BATS.  I recommend you use this feature instead of
> >> introducing another one as well as a compile time option.
> >>
> >
> > CPU_FTR_HAS_HIGH_BATS only clears the high bats, but does
> > not attempt to use them. My patch will use them.
> 
> I understand, I'm suggesting you expand CPU_FTR_HAS_HIGH_BATS to  
> include your additional functionality.

How do you mean that exactly?

Do you mean making the feature always-on (not selectable in Kconfig)?
Having CONFIG_PPC_LARGE_BATS and CONFIG_HIGH_PATS always-on would
be ok for me, but for PHYS_64BIT should be left up to the platform
to decide if it should be presented to the user or not.

Do you think the other two features, CPU_FTR_BIG_PHYS and 
CPU_FTR_LARGE_BATS should be merged into one bit? They could for now, 
because there is no processor supporting only one of them.

Rupert

> 
> - kumar

  reply	other threads:[~2005-10-21 18:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-21 12:17 [PATCH][RFT] Make PPC7450Features useable Rupert Eibauer
2005-10-21 12:42 ` [PATCH][RFT] please use this one Rupert Eibauer
2005-10-21 14:28   ` Kumar Gala
2005-10-21 15:11     ` Rupert Eibauer
2005-10-21 15:23       ` Kumar Gala
2005-10-21 18:43         ` Rupert Eibauer [this message]
2005-10-21 18:34           ` Kumar Gala

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=200510212043.18615.rupert@ces.ch \
    --to=rupert@ces.ch \
    --cc=kumar.gala@freescale.com \
    --cc=linuxppc-dev@ozlabs.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).