From: Jeff Garzik <jeff@garzik.org>
To: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
Cc: Chris Wedgwood <cw@f00f.org>, Andrew Morton <akpm@osdl.org>,
bjorn.helgaas@hp.com, linux-kernel@vger.kernel.org,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
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 11:13:53 -0400 [thread overview]
Message-ID: <44FD9431.2050403@garzik.org> (raw)
In-Reply-To: <1157468155.30252.17.camel@localhost.localdomain>
Sergio Monteiro Basto wrote:
> On Mon, 2006-09-04 at 11:33 -0700, Chris Wedgwood wrote:
>> On Mon, Sep 04, 2006 at 12:54:07PM +0100, Sergio Monteiro Basto wrote:
>>
>>> I don't know if this is a real question. Have we VIA products on PCI
>>> card, running on not VIA chip sets ?
>> Yes. Certainly for on-board devices too.
>
> OK , other argument.
> 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.
No thanks. As VIA SATA maintainer, I like being able to use my VIA SATA
PCI card.
Jeff
next prev parent reply other threads:[~2006-09-05 15:14 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 [this message]
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
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=44FD9431.2050403@garzik.org \
--to=jeff@garzik.org \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=bjorn.helgaas@hp.com \
--cc=cw@f00f.org \
--cc=dsd@gentoo.org \
--cc=greg@kroah.com \
--cc=harmon@ksu.edu \
--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