From: Oliver Neukum <oneukum@suse.de>
To: Sarah Sharp <sarah.a.sharp@linux.intel.com>
Cc: Denis Turischev <denis.turischev@compulab.co.il>,
linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
Takashi Iwai <tiwai@suse.de>,
dashing.meng@gmail.com, Niklas Schnelle <niklas@komani.de>,
Giorgos <ganastasiouGR@gmail.com>,
art1@vhex.net
Subject: Re: [PATCH v1] xhci: Switch Intel Lynx Point ports to EHCI on shutdown
Date: Fri, 03 Jan 2014 19:14:29 +0100 [thread overview]
Message-ID: <1388772869.5769.1.camel@linux-fkkt.site> (raw)
In-Reply-To: <20140103000334.GE9621@xanatos>
On Thu, 2014-01-02 at 16:03 -0800, Sarah Sharp wrote:
> That means your system worked fine in 3.13-rc3 (when the quirk was
> applied broadly), but won't work for 3.13-rc6 (when the quirk was
> narrowed to HP machines). So we need the quirk to apply to your
> systems
> as well.
>
> ISTR that the other folks on Cc (Meng, Niklas, Giorgos, and Art) all
> had
> systems that broke when commit
> 638298dc66ea36623dbc2757a24fc2c4ab41b016
> was introduced. For those systems, what vendor was the system, and
> what
> BIOS was it running?
>
> Takashi, did the HP systems that needed the quirk have a Phoenix BIOS?
>
> Denis, do all of Compulab's Haswell systems reboot on shutdown? Are
> they all running a Phoenix BIOS? Can you send me the output of `sudo
> lspci -vvv -s` for the xHCI host?
>
> Basically, I'm trying to find a common variable to key off. I suspect
> BIOS vendor is probably the right thing, instead of system vendor.
The BIOS vendor on HP systems is "Hewlett-Packard"
I guess the hope for a single common denominator is futile.
It'll have to be a list.
Regards
Oliver
next prev parent reply other threads:[~2014-01-03 18:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-19 16:29 Denis Turischev
2013-12-19 16:38 ` Greg KH
2013-12-19 17:07 ` [PATCH v1] " Denis Turischev
2013-12-19 18:21 ` Sarah Sharp
2013-12-20 10:41 ` Denis Turischev
2013-12-20 23:45 ` Sarah Sharp
2013-12-21 16:45 ` Holger Freyther
2013-12-22 7:47 ` Denis Turischev
2014-01-03 0:03 ` Sarah Sharp
2014-01-03 3:40 ` littlebat
2014-01-03 18:14 ` Oliver Neukum [this message]
2014-01-03 19:34 ` art1
2014-01-06 12:34 ` Denis Turischev
2014-01-07 10:03 ` Takashi Iwai
2014-01-07 23:11 ` Sarah Sharp
2014-01-08 12:57 ` Denis Turischev
2014-02-04 11:10 ` [PATCH] " Denis Turischev
2014-02-18 7:42 ` [RESEND] " Denis Turischev
2014-02-18 18:54 ` Sarah Sharp
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=1388772869.5769.1.camel@linux-fkkt.site \
--to=oneukum@suse.de \
--cc=art1@vhex.net \
--cc=dashing.meng@gmail.com \
--cc=denis.turischev@compulab.co.il \
--cc=ganastasiouGR@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=niklas@komani.de \
--cc=sarah.a.sharp@linux.intel.com \
--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 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®