* 8260 and HPTE
@ 2002-09-11 23:32 Jim Mar
2002-09-12 4:19 ` Paul Mackerras
0 siblings, 1 reply; 2+ messages in thread
From: Jim Mar @ 2002-09-11 23:32 UTC (permalink / raw)
To: linuxppc-embedded@lists.linuxppc.org
Hello,
I am using 2.4.18 on a proprietary 8260 board. It appears that
CPU_FTR_HPTE_TABLE is not supported for the 8260(603e). Therefore,
MMU_init_hw in ppc_mmu.c returns without patching create_hpte and
flush_hash_page in hashtable.S or allocating hash memory.
However, a Data Access Exception(0x300) eventually calls create_hpte,
trashing my memory.
What am I missing here?
Jim
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: 8260 and HPTE
2002-09-11 23:32 8260 and HPTE Jim Mar
@ 2002-09-12 4:19 ` Paul Mackerras
0 siblings, 0 replies; 2+ messages in thread
From: Paul Mackerras @ 2002-09-12 4:19 UTC (permalink / raw)
To: jmar; +Cc: linuxppc-embedded@lists.linuxppc.org
Jim Mar writes:
> I am using 2.4.18 on a proprietary 8260 board. It appears that
> CPU_FTR_HPTE_TABLE is not supported for the 8260(603e). Therefore,
> MMU_init_hw in ppc_mmu.c returns without patching create_hpte and
> flush_hash_page in hashtable.S or allocating hash memory.
>
> However, a Data Access Exception(0x300) eventually calls create_hpte,
> trashing my memory.
This is fixed in the official 2.4.19 and in the current linuxppc_2_4
and linuxppc_2_4_devel trees. The code that calls hash_page (which calls
create_hpte) in the DSI handler is in a feature section, which means
it gets overwritten with NOPs if we don't have a hash table.
Paul.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2002-09-12 4:19 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2002-09-11 23:32 8260 and HPTE Jim Mar
2002-09-12 4:19 ` Paul Mackerras
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).