public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: Jean Delvare <jdelvare@suse.de>,
	Daniel Drake <dsd@reactivated.net>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Adrian Bunk <bunk@stusta.de>
Subject: Re: via irq quirk breakage
Date: Tue, 30 Jan 2007 14:25:31 +0000	[thread overview]
Message-ID: <20070130142531.790b13a0@localhost.localdomain> (raw)
In-Reply-To: <45BEAEE3.9080003@yahoo.com.au>

> Well it works because I know I need that particular quirk applied to
> my USB IRQ. But definitely it is a hack because I've otherwise got no
> idea what I'm doing ;)

The VIA quirks depend upon so many interacting things - the BIOS irq
routing data being correct, the ACPI tables being coded by someone who
had more than ten minutes to ship the product etc.

If you are feeling really really bored Nick you can work each IRQ routing
back using the chip data sheet. It's utterly tedious but may give an
answer.

Alan

      parent reply	other threads:[~2007-01-30 14:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-01-24  0:33 via irq quirk breakage Nick Piggin
2007-01-29 15:00 ` Jean Delvare
2007-01-29 15:51   ` Alan
2007-01-30 12:29     ` Jean Delvare
2007-01-30 16:05       ` Alan
2007-01-30  2:35   ` Nick Piggin
2007-01-30  7:54     ` Jean Delvare
2007-01-30  8:32       ` Nick Piggin
2007-01-30 11:47       ` Sergey Vlasov
2007-01-30 12:25         ` [PATCH] VIA IRQ quirk breakage fix Jean Delvare
2007-01-30 13:38           ` Nick Piggin
2007-01-30 13:49             ` Jean Delvare
2007-01-30 16:21               ` Alan
2007-01-30 16:17                 ` Jean Delvare
2007-01-30 18:02               ` Andrew Morton
2007-01-31  2:37           ` Andrew Morton
2007-02-01  7:39             ` Jean Delvare
2007-01-30 14:56       ` via irq quirk breakage Alan
2007-01-30 14:50         ` Jeff Garzik
2007-01-30 14:25     ` Alan [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=20070130142531.790b13a0@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=bunk@stusta.de \
    --cc=dsd@reactivated.net \
    --cc=jdelvare@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nickpiggin@yahoo.com.au \
    /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