linux-mips.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: David VomLehn <dvomlehn@cisco.com>
Cc: linux-mips@linux-mips.org, ralf@linux-mips.org
Subject: Re: [PATCH 3/3] mips:powertv: Integrate Cisco Powertv platform into MIPS architecture (resend)
Date: Mon, 04 May 2009 17:51:56 -0700	[thread overview]
Message-ID: <49FF8DAC.8090701@caviumnetworks.com> (raw)
In-Reply-To: <20090504225821.GA22833@cuplxvomd02.corp.sa.net>

David VomLehn wrote:
> Adds the Cisco PowerTV platform to the configuration and Make files so
> that we can build a kernel for it.
> 
> Signed-off-by: David VomLehn <dvomlehn@cisco.com>
> ---
>  arch/mips/Kconfig                   |   30 +
>  arch/mips/Makefile                  |    8 +
>  arch/mips/configs/powertv_defconfig | 1484 +++++++++++++++++++++++++++++++++++
>  3 files changed, 1522 insertions(+), 0 deletions(-)
> 
> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 99f7b6d..b23ec4c 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
[...]
>  
> +#
> +# The flag for POWERTV clock source.
> +#
> +config CEVT_POWERTV
> +	bool
> +
>  config CEVT_SB1250
>  	bool
>  
> @@ -742,6 +766,12 @@ config CSRC_R4K
>  	select CSRC_R4K_LIB
>  	bool
>  
> +#
> +# The flag for POWERTV clock event.
> +#
> +config CSRC_POWERTV
> +	bool
> +
>  config CSRC_SB1250
>  	bool
>  

Could/should CEVT_POWERTV and CSRC_POWERTV be either eliminated or moved 
to your processor specific directory?  That is where the corresponding 
code lives.

David Daney

  reply	other threads:[~2009-05-05  0:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-04 22:58 [PATCH 3/3] mips:powertv: Integrate Cisco Powertv platform into MIPS architecture (resend) David VomLehn
2009-05-05  0:51 ` David Daney [this message]
2009-05-28 21:35   ` David VomLehn

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=49FF8DAC.8090701@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=dvomlehn@cisco.com \
    --cc=linux-mips@linux-mips.org \
    --cc=ralf@linux-mips.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).