From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: Chris Wedgwood <cw@f00f.org>, Jeff Garzik <jeff@garzik.org>,
Andrew Morton <akpm@osdl.org>,
bjorn.helgaas@hp.com, linux-kernel@vger.kernel.org,
greg@kroah.com, harmon@ksu.edu, Daniel Drake <dsd@gentoo.org>,
Len Brown <len.brown@intel.com>
Subject: Re: VIA IRQ quirk, another (embarrassing) suggestion.
Date: Tue, 05 Sep 2006 16:46:06 +0100 [thread overview]
Message-ID: <1157471166.9018.64.camel@localhost.localdomain> (raw)
In-Reply-To: <1157468155.30252.17.camel@localhost.localdomain>
Ar Maw, 2006-09-05 am 15:55 +0100, ysgrifennodd Sergio Monteiro Basto:
> We have billions of VIA chip sets with VIA PCI on-board and
> VIA PCI on others chip sets, if exists, are a very few.
> So, because some exceptions, we shouldn't stop a resolution of a very
> large % of the cases.
Not true at all. Large numbers of the VIA devices on VIA boards are not
the builtin version. Devices migrate over time from one to the other.
You can tell fron the PCI northbridge what is built in (in theory) but
we need a better way to deal with all this
next prev parent reply other threads:[~2006-09-05 15:25 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-04 0:42 VIA IRQ quirk fixup only in XT-PIC mode Take 3 Sergio Monteiro Basto
2006-09-04 0:58 ` Andrew Morton
2006-09-04 5:44 ` Jeff Garzik
2006-09-03 13:52 ` Daniel Drake
2006-09-04 5:55 ` VIA IRQ quirk, another (embarrassing) suggestion Chris Wedgwood
2006-09-04 7:43 ` Jeff Garzik
2006-09-04 11:54 ` Sergio Monteiro Basto
2006-09-04 12:14 ` Jeff Garzik
2006-09-04 18:33 ` Chris Wedgwood
2006-09-05 14:55 ` Sergio Monteiro Basto
2006-09-05 15:13 ` Jeff Garzik
2006-09-06 1:14 ` [PATCH] take 4 " Sergio Monteiro Basto
2006-09-06 1:47 ` Jeff Garzik
2006-09-05 15:46 ` Alan Cox [this message]
2006-09-04 16:25 ` VIA IRQ quirk fixup only in XT-PIC mode Take 3 Sergio Monteiro Basto
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=1157471166.9018.64.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=akpm@osdl.org \
--cc=bjorn.helgaas@hp.com \
--cc=cw@f00f.org \
--cc=dsd@gentoo.org \
--cc=greg@kroah.com \
--cc=harmon@ksu.edu \
--cc=jeff@garzik.org \
--cc=len.brown@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sergio@sergiomb.no-ip.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome