linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Leif Lindholm <Leif.Lindholm@uab.ericsson.se>
To: linuxppc-dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: udelay not exported to kernel(?) - never mind :)
Date: Tue, 08 Jun 1999 10:39:08 +0200	[thread overview]
Message-ID: <375CD6AC.D259D76E@uab.ericsson.se> (raw)
In-Reply-To: 375C213C.90DBE256@uab.ericsson.se


Hello again

Hint: don't try to understand the ppc code by looking at how the x86 did
it :)
Especially not if you're tired.

Got a bit confused by the fact that:
a) there are different udelay:s for the loader and for the kernel itself
b) the udelay inside the kernel was an __inline__ and that's why it
didn't show up in System.map :)

apologetically
/
	Leif

[[ 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-06-08  8:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-07 19:45 udelay not exported to kernel(?) Leif Lindholm
1999-06-08  8:39 ` Leif Lindholm [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=375CD6AC.D259D76E@uab.ericsson.se \
    --to=leif.lindholm@uab.ericsson.se \
    --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 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).