linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Wolfgang Denk <wd@denx.de>
To: Tom Stefanski <tom.stefanski@seranoa.com>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Can't disassemble my device driver
Date: Thu, 05 Sep 2002 09:29:07 +0200	[thread overview]
Message-ID: <20020905072912.88A9711836@denx.denx.de> (raw)
In-Reply-To: Your message of "Wed, 04 Sep 2002 18:19:58 EDT." <3D76870E.5244CED5@seranoa.com>


Hi Tom,

in message <3D76870E.5244CED5@seranoa.com> you wrote:
>
> I have a adatron bdi 2000 connected to my target board and have
> successfully load the linux kernel and set breakpoint in schedule
> However when I load my device driver, it's text section is a 0xD11D6060
> and the kernel is a 0xC00xxxxx. When is disassemble any routine in my
> driver, I get all zeros.

See the hints (and utility scripts) in  section  "8.2.2.  Dynamically
Loaded   Device   Drivers   (Modules)"   of   our   documentation  at
http://www.denx.de/doc/TQM8xxL/debugging.html

>  I have MMU xlate set in the config file and I program the mmu correctly
> since I can break a schedule. Any help would be apprecciated

You also have to use PTBASE in combination with a kernel that updates
these pointers. See the BDI2000 documentation.

Wolfgang Denk

--
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd@denx.de
In theory, there is no difference between  theory  and  practice.  In
practice, however, there is.

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

  reply	other threads:[~2002-09-05  7:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-04 22:19 Can't disassemble my device driver Tom Stefanski
2002-09-05  7:29 ` Wolfgang Denk [this message]
2002-09-05 11:03 ` Neil Horman

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=20020905072912.88A9711836@denx.denx.de \
    --to=wd@denx.de \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=tom.stefanski@seranoa.com \
    /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).