All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Edelsohn <dje@watson.ibm.com>
To: Dave Weis <djweis@plconline.com>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: modifying boot loader
Date: Mon, 29 Mar 1999 18:36:50 -0500	[thread overview]
Message-ID: <9903292336.AA42910@marc.watson.ibm.com> (raw)
In-Reply-To: Message from Dave Weis <djweis@plconline.com> of "Mon, 29 Mar 1999 15:48:07 CST." <Pine.LNX.3.95.990329154458.29373G-100000@catbert.desm.plconline.com>


	What are you actually trying to accomplish?  The values at
pin_obj_start are not magic numbers or instructions but user-friendly
values mapped at address 0.  It is trying to map values 0x0 and 0XBADFCA11
(bad function call) so that dereferencing a data pointer or a PowerOpen
ABI function pointer at address zero (0) will produce a visual clue.  This
is produced by assembly like:

addr0:
       .long   0
       .long   0xBADFCA11

And you make the linker map label addr0 at physical address 0.

David

[[ This message was sent via the linuxppc-dev mailing list.  Replies are ]]
[[ not  forced  back  to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. Please check http://lists.linuxppc.org/ ]]
[[ and http://www.linuxppc.org/ for useful information before posting.   ]]

  reply	other threads:[~1999-03-29 23:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-03-29 21:48 modifying boot loader Dave Weis
1999-03-29 23:36 ` David Edelsohn [this message]
1999-03-29 23:38   ` Dave Weis
1999-03-29 23:49     ` David Edelsohn
1999-03-30  3:05       ` Dave Weis
1999-03-30  4:05         ` David Edelsohn
1999-03-30  4:25           ` Dave Weis
1999-03-30  8:13             ` Gabriel Paubert
1999-03-30 14:51               ` David A. Gatwood
1999-03-31  7:12                 ` Erik Karlberg
1999-03-30  9:38           ` Gary Thomas
  -- strict thread matches above, loose matches on Subject: below --
1999-03-30  9:52 Andrew J Benie
1999-03-30 14:12 ` Norman R Weathers

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=9903292336.AA42910@marc.watson.ibm.com \
    --to=dje@watson.ibm.com \
    --cc=djweis@plconline.com \
    --cc=linuxppc-dev@lists.linuxppc.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.