Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: David Daney <ddaney@caviumnetworks.com>
To: Manuel Lauss <mano@roarinelk.homelinux.net>
Cc: LMO <linux-mips@linux-mips.org>, Ralf Baechle <ralf@linux-mips.org>
Subject: Re: [PATCH v2] Alchemy: cpu feature override constants.
Date: Tue, 25 Nov 2008 15:23:48 -0800	[thread overview]
Message-ID: <492C8904.5040202@caviumnetworks.com> (raw)
In-Reply-To: <20081125231230.GA10366@roarinelk.homelinux.net>

Manuel Lauss wrote:
[...]
> +#define cpu_has_tlb		1
> +#define cpu_has_4kex		1
> +#define cpu_has_3k_cache	0
> +#define cpu_has_4k_cache	1
> +#define cpu_has_tx39_cache	0
> +#define cpu_has_fpu		0
> +#define cpu_has_32fpr		0
> +#define cpu_has_counter		1
> +#define cpu_has_watch		1
> +#define cpu_has_divec		1
> +#define cpu_has_vce		0
> +#define cpu_has_cache_cdex_p	0
> +#define cpu_has_cache_cdex_s	0
> +#define cpu_has_mcheck		1
> +#define cpu_has_ejtag		1
> +#define cpu_has_llsc		1
> +#define cpu_has_mips16		0
> +#define cpu_has_mdmx		0
> +#define cpu_has_mips3d		0
> +#define cpu_has_smartmips	0
> +#define cpu_has_vtag_icache	0
> +#define cpu_has_dc_aliases	0
> +#define cpu_has_ic_fills_f_dc	1
> +#define cpu_has_pindexed_cache	0
> +#define cpu_has_mips32r1	1
> +#define cpu_has_mips32r2	0
> +#define cpu_has_mips64r1	0
> +#define cpu_has_mips64r2	0
> +#define cpu_has_dsp		0
> +#define cpu_has_mipsmt		0
> +#define cpu_has_userlocal	0
> +#define cpu_has_nofpuex		0
> +#define cpu_has_64bits		0
> +#define cpu_has_64bit_zero_reg	0
> +#define cpu_has_vint		0
> +#define cpu_has_veic		0
> +#define cpu_has_inclusive_pcaches 0
> +
> +#define cpu_dcache_line_size()	32
> +#define cpu_icache_line_size()  32

The probe routines in cpu-probe.c should get at least some of that 
correct.  How about just overriding the things that cpu-probe.c doesn't 
get right?

David Daney

  reply	other threads:[~2008-11-25 23:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-11-25 23:12 [PATCH v2] Alchemy: cpu feature override constants Manuel Lauss
2008-11-25 23:23 ` David Daney [this message]
2008-11-26  5:50   ` Manuel Lauss
2008-11-26  7:51     ` Ralf Baechle
2008-11-26  8:08       ` Manuel Lauss
2008-11-26  8:34         ` Ralf Baechle
2008-11-26 12:48 ` Sergei Shtylyov

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=492C8904.5040202@caviumnetworks.com \
    --to=ddaney@caviumnetworks.com \
    --cc=linux-mips@linux-mips.org \
    --cc=mano@roarinelk.homelinux.net \
    --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