From: Dan Malek <dan@embeddededge.com>
To: Wolfgang Denk <wd@denx.de>
Cc: Seb James <s.james@magtech.co.uk>,
rtai@rtai.org, linuxppc-dev@lists.linuxppc.org
Subject: Re: timebase interrupts on an mpc8xx
Date: Wed, 28 May 2003 07:12:15 -0400 [thread overview]
Message-ID: <3ED4998F.8010108@embeddededge.com> (raw)
In-Reply-To: 20030527200329.D7EEFC6162@atlas.denx.de
Wolfgang Denk wrote:
> I disagree. I think Wolfgang Grandegger is right;
Sorry, I didn't see any other replies to this message.
> ... it's caused by
> reading sivec without a pending interrupt.
What? That had been updated a long time ago, is it missing again?
> BTW: it seems the interrupt handling code becomes worse. I guess you
> don't care about this any more?
I care alot. There have been changes I have totally disagreed with,
but they were checked in anyway. Not much I can do about it but hope
I get time to fix it in the future.
> ... At least it was working when you
> did... Now the 2_4_devel code is crap.
I agree, but it wasn't my choice. People that don't even use the code
seemed to this was the way to go..........
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
parent reply other threads:[~2003-05-28 11:12 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20030527200329.D7EEFC6162@atlas.denx.de>]
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=3ED4998F.8010108@embeddededge.com \
--to=dan@embeddededge.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=rtai@rtai.org \
--cc=s.james@magtech.co.uk \
--cc=wd@denx.de \
/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).