From: Alan <alan@lxorguk.ukuu.org.uk>
To: Jean Delvare <jdelvare@suse.de>
Cc: Nick Piggin <nickpiggin@yahoo.com.au>,
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:56:29 +0000 [thread overview]
Message-ID: <20070130145629.7e40deac@localhost.localdomain> (raw)
In-Reply-To: <200701300854.06083.jdelvare@suse.de>
> You have an old VT82C686 south bridge, which was tagged as "special" by
> Alan. For this chip, Alan's code only allows devices 00:00.x to be quirked.
> As my code was merely a reimplementation of Alan's idea, it does the same.
> Your USB controllers are at 00:07.x, so I'm not surprised they weren't
> quirked.
>
> Alan, why were dev_lo and dev_hi both set to 0 for the VT82C868 in your
> implementation? Is it a typo, or...?
According to the documentation the VT82C686 has the following devices on
the internal bus: bus 0 dev ? fn 0-6. dev ? being the device of the
bridge itself. Re-reading the docs unlike the other the PCI idents aren't
fixed so my assumption of dev 0 is actually unsafe. I can't see anything
in the doc which guarantees 7 either.
Alan
next prev parent reply other threads:[~2007-01-30 14:46 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 ` Alan [this message]
2007-01-30 14:50 ` via irq quirk breakage Jeff Garzik
2007-01-30 14:25 ` Alan
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=20070130145629.7e40deac@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 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.