linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Dan Malek <dan@embeddededge.com>
To: Rudolf Ladyzhenskii <rudolf.ladyzhenskii@act-aus.net>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: BDI2000 PTEs
Date: Wed, 28 Nov 2001 01:19:57 -0500	[thread overview]
Message-ID: <3C04820D.5070904@embeddededge.com> (raw)
In-Reply-To: B164B53F5BD6D511888D009027732E1A02498E@ntserver.act.domain


Rudolf Ladyzhenskii wrote:


> All I need for kernel debugging is BAT only translation. I cleared it
> according to BDI2000 manual.

Ummm....I think you need more than that for debugging loadable modules.
The BAT translation won't work for loadable modules, you have to find
all of their code and data through page tables.

> I looked at 2.4.14 kernel. It only has BDI2000 support in file
> /arch/ppc/kernel/head_8xx.S

Well hell....I wonder why they were never updated in 2.4.14.  Take
a look at the PowerPC development kernels, then.

> Which lines do I have to add?

Add this right after the 'bl load_up_mmu':


        /* Add helper information for the Abatron bdiGDB debugger.
         * We do this here because we know the mmu is disabled, and
         * will be enabled for real in just a few instructions.
         */
        lis     r5, abatron_pteptrs@h
        ori     r5, r5, abatron_pteptrs@l
        stw     r5, 0xf0(r0)    /* This much match your Abatron config */
        lis     r6, swapper_pg_dir@h
        ori     r6, r6, swapper_pg_dir@l
        tophys(r5, r5)
        stw     r6, 0(r5)


Good Luck.


	-- Dan


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

  reply	other threads:[~2001-11-28  6:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-28  4:51 BDI2000 PTEs Rudolf Ladyzhenskii
2001-11-28  6:19 ` Dan Malek [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-11-29  0:35 Rudolf Ladyzhenskii
2001-11-28  3:49 Rudolf Ladyzhenskii
2001-11-28  4:28 ` Dan Malek

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=3C04820D.5070904@embeddededge.com \
    --to=dan@embeddededge.com \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rudolf.ladyzhenskii@act-aus.net \
    /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;
as well as URLs for NNTP newsgroup(s).