From: Eugene Surovegin <ebs@ebshome.net>
To: Wrobel Heinz-r39252 <Heinz.Wrobel@freescale.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: [RFC] [PATCH] ppc32: workaround for spurious IRQs on PQ2
Date: Wed, 27 Apr 2005 00:15:27 -0700 [thread overview]
Message-ID: <20050427071527.GA440@gate.ebshome.net> (raw)
In-Reply-To: <DF02D66C37C26B4C8018BF84F0E37FEC08440764@zwg18exm01.ea.freescale.net>
On Wed, Apr 27, 2005 at 08:54:44AM +0200, Wrobel Heinz-r39252 wrote:
> Eugene,
>
> check slides 17, 20-22 out of my SNDF 2004 presentation H1125 found at
> http://www.freescale.com/webapp/sps/site/overview.jsp?nodeId=052577pzMPYZjg286165422098
>
Thanks a lot for the link, looks like my interpretation of events was
correct.
As a side note, I'd be great if _User manual_ has all this
information (and I always rant about Moto/Freescale manuals on
#mklinux) :)
--
Eugene
next prev parent reply other threads:[~2005-04-27 7:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-27 6:54 [RFC] [PATCH] ppc32: workaround for spurious IRQs on PQ2 Wrobel Heinz-r39252
2005-04-27 7:15 ` Eugene Surovegin [this message]
2005-04-27 7:39 ` Pantelis Antoniou
-- strict thread matches above, loose matches on Subject: below --
2005-04-26 19:21 Eugene Surovegin
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=20050427071527.GA440@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=Heinz.Wrobel@freescale.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).