From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] b44 driver dev
Date: Tue, 6 Sep 2005 23:20:36 +0100 [thread overview]
Message-ID: <477ccb25a076e60eeee5778c71fa1c17@terzarima.net> (raw)
In-Reply-To: <431DD917.7060004@csh.rit.edu>
>>I'll try adding some routines that
>>look as though they flush the interrupts from the linux drivers (no
>>hardware docs for the bcm440x as far as i can find).
if you don't satisfy the source of the interrupt and it is level-triggered,
i'd expect problems. i'd also expect problems if the
interrupt is shared but not configured as level-triggered.
next prev parent reply other threads:[~2005-09-06 22:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-06 17:59 George Gensure
2005-09-06 22:20 ` Charles Forsyth [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-06 14:08 George Gensure
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=477ccb25a076e60eeee5778c71fa1c17@terzarima.net \
--to=forsyth@terzarima.net \
--cc=9fans@cse.psu.edu \
/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).