From: Lee Revell <rlrevell@joe-job.com>
To: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [Unichrome-devel] Dragging window in X causes soundcard interrupts to be lost
Date: Sat, 31 Jul 2004 20:25:39 -0400 [thread overview]
Message-ID: <1091319939.20819.67.camel@mindpipe> (raw)
In-Reply-To: <40FB0092.3070800@shipmail.org>
On Sun, 2004-07-18 at 18:58, Thomas Hellstrom wrote:
> Hi, Lee.
>
> Most of the code is inherited from VIA, but as far as I know, there
> are no locks held except the DRM lock when DRI is used, which it isn't
> in your case.
>
Thomas,
Do you have the original driver source from VIA handy? This is looking
more and more like a hardware bug - 2D acceleration engine activity
causes interrupts from the PCI slot to be disabled for long periods.
Maybe it disables interrupts to prevent other processes writing to the
shared video/system RAM as it DMAs. I would like to verify that the
problem still occurs with their driver, before I try to convince them
there's a hardware issue with the EPIA boards.
On that note, assuming I verify the bug, does anyone have any
recommendations for getting VIA to take me seriously? The problem is
very easy to reproduce.
Lee
next parent reply other threads:[~2004-08-01 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1089952196.25689.7.camel@mindpipe>
[not found] ` <40F78D21.10305@shipmail.org>
[not found] ` <40F793C1.2080908@shipmail.org>
[not found] ` <1090001316.27995.3.camel@mindpipe>
[not found] ` <40F8298E.8080508@shipmail.org>
[not found] ` <1090010147.30435.2.camel@mindpipe>
[not found] ` <1090107507.10795.1.camel@mindpipe>
[not found] ` <40FA3AEC.9050906@shipmail.org>
[not found] ` <1090190244.22282.8.camel@mindpipe>
[not found] ` <40FB0092.3070800@shipmail.org>
2004-08-01 0:25 ` Lee Revell [this message]
2004-07-31 23:37 ` [Unichrome-devel] Dragging window in X causes soundcard interrupts to be lost Alan Cox
2004-08-01 0:56 ` Lee Revell
2004-09-01 18:57 ` Lee Revell
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=1091319939.20819.67.camel@mindpipe \
--to=rlrevell@joe-job.com \
--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.