From: Roger Luethi <rl@hellgate.ch>
To: Jeff Garzik <jeff@garzik.org>
Cc: akpm@osdl.org, Linux Kernel <linux-kernel@vger.kernel.org>,
enrico.scholz@informatik.tu-chemnitz.de, greg@kroah.com
Subject: Re: + via-rhine-on-epia-pd-needs.patch added to -mm tree
Date: Sun, 25 Jun 2006 12:14:20 +0200 [thread overview]
Message-ID: <20060625101420.GA15771@k3.hellgate.ch> (raw)
In-Reply-To: <449DBF48.2050607@garzik.org>
On Sat, 24 Jun 2006 18:40:08 -0400, Jeff Garzik wrote:
> akpm@osdl.org wrote:
> > via-rhine on epia-pd needs irq-quirk
> >
> >has been added to the -mm tree. Its filename is
> >
> > via-rhine-on-epia-pd-needs.patch
>
> It strikes me as very unwise to do this. I know that some VIA Rhine
> exist on a PCI card, which is a valid case where this quirk should -not-
> be executed.
There are PCI cards for each of Rhine-I, -II, and -III.
> The VIA quirk is only for on-motherboard devices, which have special PCI
> interrupt line behavior (makes some internal PIC connections).
What exactly does on-motherboard mean in this context? Separate chip
soldered to the motherboard? Or integrated into the south bridge? Or both?
> How can we solve this conditionally? I agree this is needed... for
VIA uses the PCI revision number to identify their chips. In fact, I have
some patch lying around that identifies the model of every Rhine ever
produced (at the time, anyway): VT86C100A, VT6102, VT8231, VT8233, VT8235,
VT8237, VT6105, VT6105L, VT6107, and VT6105M. I am not sure whether this
can be used to identify the models with this particular quirk, though.
> on-mobo devices. But 0x3065 is not always glued in, AFAIK.
Correct. But 0x3065 is fairly meaningless in VIA world.
Roger
prev parent reply other threads:[~2006-06-25 10:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200606242219.k5OMIxxY006085@shell0.pdx.osdl.net>
2006-06-24 22:40 ` + via-rhine-on-epia-pd-needs.patch added to -mm tree Jeff Garzik
2006-06-25 9:11 ` Sergey Vlasov
2006-06-25 10:14 ` Roger Luethi [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=20060625101420.GA15771@k3.hellgate.ch \
--to=rl@hellgate.ch \
--cc=akpm@osdl.org \
--cc=enrico.scholz@informatik.tu-chemnitz.de \
--cc=greg@kroah.com \
--cc=jeff@garzik.org \
--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.