From: Eugene Surovegin <ebs@ebshome.net>
To: annamaya <annamaya@yahoo.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Additional data/instruction BATs not initialized for MPC8280?
Date: Tue, 25 Jan 2005 11:10:47 -0800 [thread overview]
Message-ID: <20050125191047.GA3818@gate.ebshome.net> (raw)
In-Reply-To: <20050125174913.42739.qmail@web53805.mail.yahoo.com>
On Tue, Jan 25, 2005 at 09:49:13AM -0800, annamaya wrote:
> I have read in the specs for the MPC8280 that it has a
> G2_LE core which has 4 additional data and instruction
> BATs. However, I dont see these BATS being cleared
> early in the kernel. I only see that the first 4 pairs
> are cleared using the mtspr instructions. But my
> kernel comes up just fine and everything seems to work
> OK. Dont we need to clear the other set of I/DBATS?
> What happens when we dont do this? Thanks in advance.
Additional BATs in G2_LE core must be explicitly enabled in HID2 (HBE
bit), until then they "don't exist" :).
--
Eugene
next prev parent reply other threads:[~2005-01-25 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-25 17:49 Additional data/instruction BATs not initialized for MPC8280? annamaya
2005-01-25 19:10 ` Eugene Surovegin [this message]
2005-01-25 19:40 ` annamaya
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=20050125191047.GA3818@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=annamaya@yahoo.com \
--cc=linuxppc-embedded@ozlabs.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