From: Sven Luther <sven.luther@wanadoo•fr>
To: Benjamin Herrenschmidt <benh@kernel•crashing.org>
Cc: Sven Luther <sven.luther@wanadoo•fr>,
linuxppc-dev list <linuxppc-dev@lists•linuxppc.org>
Subject: Re: OF properties access ?
Date: Mon, 19 Jan 2004 11:17:28 +0100 [thread overview]
Message-ID: <20040119101728.GB18112@iliana> (raw)
In-Reply-To: <1074502892.813.41.camel@gaston>
On Mon, Jan 19, 2004 at 08:01:33PM +1100, Benjamin Herrenschmidt wrote:
> Well... You can move that code to a later place where you can printk
> and debug waht's up. It's also possible that the _set_L2CR routine
> in the kernel you are working on isn't totally correct for your CPU
> model... Do you have the 7447 recongnized at all in cputable ?
Mmm, i have :
{ /* 7457 */
0xffff0000, 0x80020000, "7457",
CPU_FTR_SPLIT_ID_CACHE | CPU_FTR_USE_TB | CPU_FTR_CAN_NAP |
CPU_FTR_L2CR | CPU_FTR_ALTIVEC_COMP | CPU_FTR_L3CR |
CPU_FTR_HPTE_TABLE | CPU_FTR_SPEC7450 | CPU_FTR_NAP_DISABLE_L2_PR |
CPU_FTR_HAS_HIGH_BATS,
COMMON_PPC | PPC_FEATURE_HAS_ALTIVEC,
32, 32,
__setup_cpu_745x
},
Which should be ok, since there seem to be no way to distinguish a 7447
from a 7457 anyway (apart from maybe L2 cache probing or such).
And indeed, the problem seems to be that i get /cpus, and not
/cpus/PowerPC,74x7. I thought that the /cpus should give the cpu per
default or something such. What should i do here, i can go look for a
PowerPC,74x7, but the board can also come with other CPUs (the 750Cxe
for now). Maybe i could remove the cpus checking code completely, and go
looking for the cpu type directly.
Friendly,
Sven Luther
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-01-19 10:17 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-13 11:46 OF properties access ? Sven Luther
2004-01-15 1:49 ` Benjamin Herrenschmidt
2004-01-15 7:44 ` Sven Luther
2004-01-17 3:48 ` Benjamin Herrenschmidt
2004-01-18 12:07 ` Sven Luther
2004-01-18 23:21 ` Benjamin Herrenschmidt
2004-01-18 14:32 ` Sven Luther
2004-01-18 14:51 ` Sven Luther
2004-01-18 15:05 ` Sven Luther
2004-01-19 9:05 ` Benjamin Herrenschmidt
2004-01-18 22:22 ` Sven Luther
2004-01-19 9:04 ` Benjamin Herrenschmidt
2004-01-19 1:35 ` Dan Malek
2004-01-19 9:01 ` Benjamin Herrenschmidt
2004-01-19 10:17 ` Sven Luther [this message]
2004-01-19 11:42 ` Benjamin Herrenschmidt
2004-01-19 12:06 ` Sven Luther
2004-01-19 21:36 ` Benjamin Herrenschmidt
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=20040119101728.GB18112@iliana \
--to=sven.luther@wanadoo$(echo .)fr \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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