From: Michal Marek <mmarek@suse.cz>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Alex Williamson <alex.williamson@redhat.com>,
Takashi Iwai <tiwai@suse.de>, Bjorn Helgaas <bhelgaas@google.com>,
Oliver Neukum <oneukum@suse.de>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] pciehp: Add pciehp_surprise module option
Date: Fri, 22 Mar 2013 17:35:36 +0100 [thread overview]
Message-ID: <514C8858.3050702@suse.cz> (raw)
In-Reply-To: <20130322161644.GA28760@srcf.ucam.org>
On 22.3.2013 17:16, Matthew Garrett wrote:
> On Fri, Mar 22, 2013 at 05:15:04PM +0100, Michal Marek wrote:
>
>> Alex, Matthew, would it work for you to have this debug / band-aid
>> option _and_ have a list of either machines' dmi strings that have this
>> problem, or devices' PCI IDs (*), and enable the surprise event handling
>> for such machines / devices automatically? The option would be still
>> useful for debugging, to be able to easily find out if given machine has
>> this problem and needs to be added to the quirk list.
>
> That's be preferable, but if there's anything we've learned about dmi
> strings it's that they usually mean we're doing something wrong. Does
> this work with Windows without any quirking? Is there a machine-specific
> driver for the PCIe chipset?
I don't know. Oliver and Takashi have the machines, but I'm not sure if
they have a working Windows image for them.
Michal
next prev parent reply other threads:[~2013-03-22 16:35 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-20 14:02 [PATCH] pciehp: Add pciehp_surprise module option Takashi Iwai
2013-03-20 16:33 ` Randy Dunlap
2013-03-20 16:39 ` Takashi Iwai
2013-03-20 17:52 ` Matthew Garrett
2013-03-20 19:11 ` Takashi Iwai
2013-03-20 19:12 ` Matthew Garrett
2013-03-20 19:23 ` Takashi Iwai
2013-03-20 19:26 ` Matthew Garrett
2013-03-20 18:09 ` Alex Williamson
2013-03-20 19:08 ` Takashi Iwai
2013-03-22 16:15 ` Michal Marek
2013-03-22 16:16 ` Matthew Garrett
2013-03-22 16:35 ` Michal Marek [this message]
2013-03-22 16:20 ` Alex Williamson
2013-03-27 16:11 ` Oliver Neukum
2013-03-27 16:19 ` Michal Marek
2013-03-20 18:41 ` Martin Mokrejs
2013-03-20 18:56 ` Martin Mokrejs
2013-03-20 19:20 ` Takashi Iwai
2013-06-07 0:04 ` Martin Mokrejs
2013-03-25 16:58 ` Bjorn Helgaas
2013-04-10 16:34 ` Takashi Iwai
2013-04-10 17:19 ` Bjorn Helgaas
2013-04-11 13:40 ` Takashi Iwai
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=514C8858.3050702@suse.cz \
--to=mmarek@suse.cz \
--cc=alex.williamson@redhat.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mjg59@srcf.ucam.org \
--cc=oneukum@suse.de \
--cc=tiwai@suse.de \
/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.