From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Linux ARM Kernel list <linux-arm-kernel@lists.arm.linux.org.uk>
Subject: Re: tricky challenge for getting round level-driven interrupt problem: help!
Date: Thu, 5 May 2005 12:32:54 +0100 [thread overview]
Message-ID: <20050505113254.GI8537@lkcl.net> (raw)
In-Reply-To: <1115243014.19844.62.camel@localhost.localdomain>
On Wed, May 04, 2005 at 10:43:35PM +0100, Alan Cox wrote:
> > hence the redesign to do alternate read-write-read-write, and making
> > reads exclusive of writes, etc.
>
> and maybe even turn the IRQ off and use a timer if its slow and not
> sensitive to latency.. ?
good suggestion...
been there, tried that [i really _am_ sending to lkml as
last resort, not first!]
jiffies equals approx 250? per second?
baud rate from PIC is determined by GPS - 4800 baud - approx
600 per second.
so that'd explain why i only got one character every 3.
*cold sweat*.
i could always use the FIQ, which will be running off the back
of the Audio DAC/ADC's interrupts, 8khz....
*shudder*...
next prev parent reply other threads:[~2005-05-05 11:24 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-03 21:56 tricky challenge for getting round level-driven interrupt problem: help! Luke Kenneth Casson Leighton
2005-05-04 1:50 ` Alan Cox
2005-05-04 20:58 ` Luke Kenneth Casson Leighton
2005-05-04 21:43 ` Alan Cox
2005-05-04 23:20 ` Luke Kenneth Casson Leighton
2005-05-05 11:32 ` Luke Kenneth Casson Leighton [this message]
2005-05-06 10:57 ` Luke Kenneth Casson Leighton
2005-05-08 12:32 ` Luke Kenneth Casson Leighton
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=20050505113254.GI8537@lkcl.net \
--to=lkcl@lkcl.net \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-arm-kernel@lists.arm.linux.org.uk \
--cc=linux-kernel@vger.kernel.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.