Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: tsbogend@alpha.franken.de (Thomas Bogendoerfer)
To: VomLehn <dvomlehn@cisco.com>
Cc: Linux MIPS Mailing List <linux-mips@linux-mips.org>,
	Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH][MIPS] Use CP0 Count register to implement more granular ndelay
Date: Fri, 13 Mar 2009 10:29:07 +0100	[thread overview]
Message-ID: <20090313092906.GA6526@alpha.franken.de> (raw)
In-Reply-To: <20090312032850.GA9379@cuplxvomd02.corp.sa.net>

On Wed, Mar 11, 2009 at 08:28:50PM -0700, VomLehn wrote:
>  #
> +# Collect various processors by instruction family
> +#
> +config MIPS1
> +	bool
> +	default y if CPU_R3000 || CPU_TX39XX
> +
> +config MIPS2
> +	bool
> +	default y if CPU_R6000
> +
> +config MIPS3
> +	bool
> +	default y if CPU_LOONGSON2 || CPU_R4300 || CPU_R4X00 || CPU_TX49XX || \
> +		CPU_VR41XX
> +
> +config MIPS4
> +	bool
> +	default y if CPU_R8000 || CPU_R10000
> +

what about all the R5k CPUs ?

Thomas.

-- 
Crap can work. Given enough thrust pigs will fly, but it's not necessary a
good idea.                                                [ RFC1925, 2.3 ]

  reply	other threads:[~2009-03-13  9:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-12  3:28 [PATCH][MIPS] Use CP0 Count register to implement more granular ndelay VomLehn
2009-03-13  9:29 ` Thomas Bogendoerfer [this message]
2009-03-13 11:32   ` Ralf Baechle
2009-03-13 17:35   ` VomLehn
     [not found] <web-5716826@test.infohit.si>
2009-03-25 17:37 ` David VomLehn
  -- strict thread matches above, loose matches on Subject: below --
2009-02-27 23:09 VomLehn
2009-02-28 21:10 ` Paul Gortmaker
2009-02-28 21:10   ` Paul Gortmaker
2009-03-10 19:18   ` VomLehn
2009-03-10 20:12     ` Ralf Baechle

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=20090313092906.GA6526@alpha.franken.de \
    --to=tsbogend@alpha.franken.de \
    --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