mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sergio Monteiro Basto <sergio@sergiomb.no-ip.org>
To: Adrian Bunk <bunk@stusta.de>
Cc: Linus Torvalds <torvalds@osdl.org>, Chris Wedgwood <cw@f00f.org>,
	Daniel Drake <dsd@gentoo.org>, Daniel Ritz <daniel.ritz@gmx.ch>,
	Jean Delvare <khali@linux-fr.org>,
	Bjorn Helgaas <bjorn.helgaas@hp.com>,
	Brice Goglin <brice@myri.com>,
	"John W. Linville" <linville@tuxdriver.com>,
	Bauke Jan Douma <bjdouma@xs4all.nl>,
	Tomasz Koprowski <tomek@koprowski.org>,
	gregkh@suse.de, linux-kernel@vger.kernel.org,
	linux-pci@atrey.karlin.mff.cuni.cz, Alan Cox <alan@redhat.com>
Subject: Re: RFC: PCI quirks update for 2.6.16
Date: Tue, 19 Dec 2006 06:08:41 +0000	[thread overview]
Message-ID: <1166508521.3800.40.camel@monteirov> (raw)
In-Reply-To: <20061210234733.GH10351@stusta.de>

[-- Attachment #1: Type: text/plain, Size: 1342 bytes --]

On Mon, 2006-12-11 at 00:47 +0100, Adrian Bunk wrote:
> So we have the following situation:
> - 2.6.16    - 2.6.16.16 : problems for Chris
>                           (and possibly many other people)
> - 2.6.16.17 - 2.6.16.35 : problems for many other people
>                           (I remember 4-5 bug reports in the kernel
>                            Bugzilla alone)
> 
> The fix in 2.6.19 was considered suboptimal, and Alan's patch for
> fixing 
> this whole issue more properly is currently not even in your tree.  

Right,
Those 4-5 bug reports should test Alan's patch.
All the problem is detected the correct devices that should be quirked.
In 2.6.16, all ( PCI_VENDOR_ID_VIA, PCI_ANY_ID), in 2.6.16.17 just some.
Still questionable if this quirks is for on-board VIA when interrupts
are in PIC mode, or for all interrupts modes (historically before the
patch to be for IO-APIC and PIC mode, was just for PIC mode, but in that
time IO-APIC wasn't common on PC) .
So with Alan's patch the question is:if a device need to be quirked and
don't. 
Those 4-5 reports will answer the question, they needs VIA quirks and we
want know is the patch do the right job. 
My laptop that need the quirks and I can test it is not available right
now and I am too busy to test on it, sorry.

Thanks,
-- 
Sérgio M.B.

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 2166 bytes --]

  parent reply	other threads:[~2006-12-19  6:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 13:24 Adrian Bunk
2006-12-07 13:53 ` Sergey Vlasov
2006-12-07 17:27   ` Bauke Jan Douma
2006-12-07 18:32     ` Sergey Vlasov
2006-12-08 15:34       ` Adrian Bunk
2006-12-07 14:38 ` Daniel Drake
2006-12-07 14:57   ` Adrian Bunk
2006-12-07 16:37     ` Alan Cox
2006-12-10  4:09   ` Sergio Monteiro Basto
2006-12-10 16:00     ` Adrian Bunk
2006-12-10 16:22       ` Daniel Drake
2006-12-10 22:33         ` Chris Wedgwood
2006-12-10 22:39           ` Linus Torvalds
2006-12-10 22:49             ` Chris Wedgwood
2006-12-11  1:17               ` Linus Torvalds
2006-12-10 23:47             ` Adrian Bunk
2006-12-11  1:23               ` Linus Torvalds
2006-12-11 12:52                 ` Adrian Bunk
2006-12-19  6:08               ` Sergio Monteiro Basto [this message]
2006-12-11  1:42       ` Sergio Monteiro Basto
2006-12-11 12:41         ` Adrian Bunk
2006-12-11 12:48           ` Sergio Monteiro Basto
2006-12-11 13:01             ` Adrian Bunk
2006-12-07 19:54 ` Jean Delvare
2006-12-07 20:45   ` Tomek Koprowski
2006-12-08 15:42     ` Adrian Bunk
2006-12-08 16:11 ` RFC: PCI quirks update for 2.6.16 (v2) Adrian Bunk
2006-12-08 21:02 ` RFC: PCI quirks update for 2.6.16 Brice Goglin

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=1166508521.3800.40.camel@monteirov \
    --to=sergio@sergiomb.no-ip.org \
    --cc=alan@redhat.com \
    --cc=bjdouma@xs4all.nl \
    --cc=bjorn.helgaas@hp.com \
    --cc=brice@myri.com \
    --cc=bunk@stusta.de \
    --cc=cw@f00f.org \
    --cc=daniel.ritz@gmx.ch \
    --cc=dsd@gentoo.org \
    --cc=gregkh@suse.de \
    --cc=khali@linux-fr.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@atrey.karlin.mff.cuni.cz \
    --cc=linville@tuxdriver.com \
    --cc=tomek@koprowski.org \
    --cc=torvalds@osdl.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

all inboxes | Powered by JetHome®