public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Thomas Hellström" <thomas@tungstengraphics.com>
To: "Németh Márton" <nm127@freemail.hu>
Cc: David Airlie <airlied@linux.ie>,
	Shankar Giri V <shankargiri@gmail.com>,
	dri-devel@lists.sourceforge.net,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] change the type of Unichrome display adapter (PCI	ID=1106:3108)
Date: Sun, 16 Mar 2008 11:05:59 +0100	[thread overview]
Message-ID: <47DCF107.2040307@tungstengraphics.com> (raw)
In-Reply-To: <47DBB442.90509@freemail.hu>

Németh Márton wrote:
> From: Márton Németh <nm127@freemail.hu>
>
> Change the type of Unichrome display adapter with PCI ID=1106:3108 to
> get rid of message "irq 16: nobody cared".
>
> See http://bugzilla.kernel.org/show_bug.cgi?id=8641 for details.
>
> Signed-off-by: Shankar Giri V <shankargiri@gmail.com>
> Signed-off-by: Márton Németh <nm127@freemail.hu>
> ---
>
> --- linux-2.6.25-rc5/drivers/char/drm/drm_pciids.h.orig	2008-03-15 10:58:49.000000000 +0100
> +++ linux-2.6.25-rc5/drivers/char/drm/drm_pciids.h	2008-03-15 10:59:31.000000000 +0100
> @@ -335,7 +335,7 @@
>  	{0x1106, 0x3118, PCI_ANY_ID, PCI_ANY_ID, 0, 0, VIA_PRO_GROUP_A}, \
>  	{0x1106, 0x3122, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
>  	{0x1106, 0x7205, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
> -	{0x1106, 0x3108, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
> +	{0x1106, 0x3108, PCI_ANY_ID, PCI_ANY_ID, 0, 0, VIA_PRO_GROUP_A}, \
>  	{0x1106, 0x3344, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
>  	{0x1106, 0x3343, PCI_ANY_ID, PCI_ANY_ID, 0, 0, 0}, \
>  	{0x1106, 0x3230, PCI_ANY_ID, PCI_ANY_ID, 0, 0, VIA_DX9_0}, \
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Microsoft
> Defy all challenges. Microsoft(R) Visual Studio 2008.
> http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
> --
> _______________________________________________
> Dri-devel mailing list
> Dri-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dri-devel
>   
Nope, this is not a correct fix. It enables a set of DMA commands not 
available on the K8M800, also it makes the via IRQ handler just report 
"Handled" when in fact the device keeps firing 200 000 or so interrupts 
per second.

I'm 99.99 % convinced that this is a hw bug, and it also appears in the 
KM400 chipsets. When VIA was asked about it they replied that IRQ 
functionality was never verified in the K8M800 since the windows driver 
never used it. They only use IRQ for video capture transfer, and there 
is no video-in on K8M800s. Other unichromes with the same IRQ register 
interface work fine.
Having said that, it's not impossible that there may be a hidden 
register somewhere that makes it all work.

The K8M800 irqs have been turned off in newer versions of the openChrome 
2D driver to work around this issue.

/Thomas






      reply	other threads:[~2008-03-16 10:06 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-15 11:34 [PATCH] change the type of Unichrome display adapter (PCI ID=1106:3108) Németh Márton
2008-03-16 10:05 ` Thomas Hellström [this message]

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=47DCF107.2040307@tungstengraphics.com \
    --to=thomas@tungstengraphics.com \
    --cc=airlied@linux.ie \
    --cc=dri-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nm127@freemail.hu \
    --cc=shankargiri@gmail.com \
    /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