From: Lee Revell <rlrevell@joe-job.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: Linux Kernel Mailing List <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:56:35 -0400 [thread overview]
Message-ID: <1091321794.20819.96.camel@mindpipe> (raw)
In-Reply-To: <1091317027.7443.29.camel@localhost.localdomain>
On Sat, 2004-07-31 at 19:37, Alan Cox wrote:
> On Sul, 2004-08-01 at 01:25, Lee Revell wrote:
> > 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.
>
> I do. There is no code in the 2D engine that touches interrupt control
> at all.
>
Yes, I saw that. This basically means it has to be a hardware bug,
correct?
> > 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.
>
> A similar problem occurs with some other chips when you write enough
> data to the chip that the FIFO fills and the PCI bus locks until the
> write can complete. Various vendors implemented this at one point for
> benchmarketing reasons and that would have a similar effect if so.
>
This was the first thing that occurred to me, but I am not really a
video driver expert, and looking at the code it's just banging bits. I
have hacked device drivers, just not video, and I don't have the
bandwidth to learn right now.
> The 2D driver source is essentially the same as the source in Xorg CVS
> barring cleanups and the accelerator code has not changed at all. You
> might want to take a look at the fifo management side of things in that
> code.
>
> > 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.
>
> I have some contact with VIA however you need to understand that the
> graphics world moves rapidly. I would be suprised if the CLE266 saw any
> more development given the CN400 has been demoed, although I certainly
> can't speak for VIA on this matter.
>
Yes, I would be happy to just get an acknowledgement of the issue.
Actually I don't even need that, I just want to know if it's fixed in
the newer ones. I have a perfectly acceptable workaround. The 2D
acceleration is pretty shoddy anyway, many things seem to work better
with NoAccel. I still love the EPIA board.
Maybe you could forward this on to them? Off the record is fine.
Lee
next prev parent reply other threads:[~2004-08-01 0:56 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 ` [Unichrome-devel] Dragging window in X causes soundcard interrupts to be lost Lee Revell
2004-07-31 23:37 ` Alan Cox
2004-08-01 0:56 ` Lee Revell [this message]
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=1091321794.20819.96.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=alan@lxorguk.ukuu.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.