linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Robin Gilks <robin.gilks@tait.co.nz>
To: Dan Malek <dan@embeddedalley.com>
Cc: ppc embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Possibly OT: bdi2000 virtual memory on 2.6 kernel
Date: Wed, 15 Nov 2006 10:32:18 +1300	[thread overview]
Message-ID: <455A35E2.5000303@tait.co.nz> (raw)
In-Reply-To: <3F51F683-985D-461F-99B1-3F729388B6CD@embeddedalley.com>

Dan Malek wrote:
> 
> On Nov 13, 2006, at 10:17 PM, Robin Gilks wrote:
> 
>> Debugging a 2.6.18 kernel on a powerpc target
> 
> Which processor, specifically?
> What do your MMU XLAT and PTBASE configuration
> lines look like?
> 
> Thanks.
> 
>     -- Dan
> 
Hi Dan

Running a 859T processor with the following bdi2000 config lines
MMU     XLAT
PTBASE  0xf0
WSPR    149     0x0082000F


in .config (for the kernel build) I have
CONFIG_BDI_SWITCH=y

Memory dumping 0xf0 - its pointing to abatron_pteptrs which contains the 
  pointer to swapper_pg_dir as expected so it all looks OK.

What I'm NOT doing is using a hardware breakpoint to get beyond the 
decompress stage and then loading the vmlinux image before proceeding. 
I'm just loading up vmlinux in ddd, allowing uboot to tftp the kernel 
binary in and decompressing it and then just letting it rip. This 
approach seems OK as far as maintaining breakpoints across multiple runs 
goes, so I assume its OK.

-- 
Robin



=======================================================================
This email, including any attachments, is only for the intended
addressee.  It is subject to copyright, is confidential and may be
the subject of legal or other privilege, none of which is waived or
lost by reason of this transmission.
If the receiver is not the intended addressee, please accept our
apologies, notify us by return, delete all copies and perform no
other act on the email.
Unfortunately, we cannot warrant that the email has not been
 altered or corrupted during transmission.
=======================================================================

      reply	other threads:[~2006-11-14 21:32 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-14  3:17 Possibly OT: bdi2000 virtual memory on 2.6 kernel Robin Gilks
2006-11-14 17:39 ` Dan Malek
2006-11-14 21:32   ` Robin Gilks [this message]

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=455A35E2.5000303@tait.co.nz \
    --to=robin.gilks@tait.co.nz \
    --cc=dan@embeddedalley.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;
as well as URLs for NNTP newsgroup(s).