From: Jon Masters <jonmasters@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: Re: xilinx_sysace
Date: Sun, 19 Sep 2004 21:18:14 +0100 [thread overview]
Message-ID: <35fb2e59040919131864c26952@mail.gmail.com> (raw)
In-Reply-To: <35fb2e5904090607241087442d@mail.gmail.com>
On Mon, 6 Sep 2004 15:24:11 +0100, Jon Masters <jonmasters@gmail.com> wrote:
> The driver works fine for me as a read only device but I'm still
> seeing occasional hard locks on writes (looks to be something not
> getting io_request_lock at the right moment - currently
> investigating). They use a kernel thread which just sits and
> compensates for the hardware not being able to signal when it is ready
> for a new request - and I think there's a race there.
It's as I thought on and off and then on again - the code checks out
ok (it's not pretty but it works) - and I seem to be getting unwanted
extra unhandled interrupts from the hardware. This driver needs a lot
of cleanup anyway - it doesn't handle these kinds of error state, nor
does it handle the removal of a mounted CompactFlash, and a dozen
other typical problems. I'll post a patch when I've solved the main
problem - moan at me by private mail if you're using this, having
similar issues, and feel like helping.
Jon.
next prev parent reply other threads:[~2004-09-19 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-09-06 14:24 xilinx_sysace Jon Masters
2004-09-19 20:18 ` Jon Masters [this message]
2004-09-23 1:12 ` [PATCH] xsa_use_interrupts flag [WAS: xilinx_sysace] Jon Masters
2004-09-23 1:12 ` Jon Masters
2004-09-23 4:51 ` Tonnerre
2004-09-23 13:40 ` Jon Masters
2004-09-23 13:40 ` Jon Masters
2004-09-23 13:36 ` Jeff Angielski
2004-09-23 13:43 ` Jon Masters
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=35fb2e59040919131864c26952@mail.gmail.com \
--to=jonmasters@gmail.com \
--cc=jonathan@jonmasters.org \
--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.