From: Dan Malek <dan@embeddededge•com>
To: Guillaume Autran <gautran@mrv•com>
Cc: linuxppc-embedded@ozlabs•org
Subject: Re: [PATCH] ppc32: fix cpm_uart_int() missing interrupts
Date: Thu, 19 May 2005 16:32:37 -0400 [thread overview]
Message-ID: <e6669029335470188ab956f01c30e82b@embeddededge.com> (raw)
In-Reply-To: <428CF693.5030100@mrv.com>
On May 19, 2005, at 4:26 PM, Guillaume Autran wrote:
> You are right, moving the event clearing statement is much easier and
> cleaner. Let the interrupt be the loop.
I also just had the thought we could check the events for non-zero,
clear them, and process only the ones we wanted. That would save
the interrupt overhead if we had high speed ports (which I really
don't like for normal RS-232 anyway :-)).
I'll move this patch ahead.
Thanks.
-- Dan
next prev parent reply other threads:[~2005-05-19 20:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-18 17:09 [PATCH] ppc32: fix CONFIG_TASK_SIZE handling on 40x Eugene Surovegin
2005-05-19 17:59 ` [PATCH] ppc32: fix cpm_uart_int() missing interrupts Guillaume Autran
2005-05-19 18:11 ` Dan Malek
2005-05-19 19:34 ` Guillaume Autran
2005-05-19 19:54 ` Dan Malek
2005-05-19 20:26 ` Guillaume Autran
2005-05-19 20:32 ` Dan Malek [this message]
2005-05-19 20:36 ` Guillaume Autran
2005-05-20 14:19 ` Dan Malek
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=e6669029335470188ab956f01c30e82b@embeddededge.com \
--to=dan@embeddededge$(echo .)com \
--cc=gautran@mrv$(echo .)com \
--cc=linuxppc-embedded@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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