From: Benjamin Herrenschmidt <bh40@calva.net>
To: David Edelsohn <dje@watson.ibm.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: bootstrap stuffs
Date: Mon, 15 Feb 1999 19:20:22 +0100 [thread overview]
Message-ID: <19990215192022.006915@mail.mipsys.com> (raw)
In-Reply-To: <9902151757.AA75924@marc.watson.ibm.com>
On Mon, Feb 15, 1999, David Edelsohn <dje@watson.ibm.com> wrote:
> As Gabriel correctly explained, a "sync" instruction may be
>necessary before interrupts are enabled if some off-chip operation, like
>modifying an interrupt controller on the bus, was performed. That is
>because of the bus operations which need to complete before interrupts can
>be enabled, not because of the enabling itself.
Yep, I knew this case, the sync after switching them OFF was just a
paranoid move on my part. Thanks for the tips.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[[ 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. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
next prev parent reply other threads:[~1999-02-15 18:20 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-02-14 14:02 bootstrap stuffs Benjamin Herrenschmidt
1999-02-14 17:03 ` David Edelsohn
1999-02-14 18:58 ` Benjamin Herrenschmidt
1999-02-15 17:57 ` David Edelsohn
1999-02-15 18:20 ` Benjamin Herrenschmidt [this message]
1999-02-16 0:02 ` Paul Mackerras
1999-02-16 11:24 ` Gabriel Paubert
1999-02-16 11:44 ` Gabriel Paubert
1999-02-16 16:43 ` Geert Uytterhoeven
1999-02-16 17:39 ` Gabriel Paubert
1999-02-16 18:11 ` Benjamin Herrenschmidt
1999-02-17 6:23 ` Cort Dougan
[not found] <19990216134514.022163@mail.mipsys.com>
1999-02-16 13:18 ` Gabriel Paubert
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=19990215192022.006915@mail.mipsys.com \
--to=bh40@calva.net \
--cc=dje@watson.ibm.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.