lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Wed, 12 Oct 2016 15:24:59 +0300 From: Luca Coelho <luca@...lho.fi> To: Chris Rorvick <chris@...vick.com>, Paul Bolle <pebolle@...cali.nl> Cc: Intel Linux Wireless <linuxwifi@...el.com>, Emmanuel Grumbach <emmanuel.grumbach@...el.com>, Johannes Berg <johannes.berg@...el.com>, Kalle Valo <kvalo@...eaurora.org>, Oren Givon <oren.givon@...el.com>, linux-wireless@...r.kernel.org, netdev@...r.kernel.org, linux-kernel@...r.kernel.org Subject: Re: [PATCH] iwlwifi: pcie: reduce "unsupported splx" to a warning On Tue, 2016-10-11 at 23:32 -0500, Chris Rorvick wrote: > On Tue, Oct 11, 2016 at 5:11 AM, Paul Bolle <pebolle@...cali.nl> wrote: > > For what it's worth, on my machine I have twenty (!) SPLX entries, all > > reading: > > Name (SPLX, Package (0x04) > > { > > Zero, > > Package (0x03) > > { > > 0x80000000, > > 0x80000000, > > 0x80000000 > > }, > > > > Package (0x03) > > { > > 0x80000000, > > 0x80000000, > > 0x80000000 > > }, > > > > Package (0x03) > > { > > 0x80000000, > > 0x80000000, > > 0x80000000 > > } > > }) > > > I actually see exactly the same on my Dell XPS 13 (9350) when I use > acpidump, etc. I typed the entry I included in the commit log by hand > based on what the driver gets back from the SPLC method (I added a > function to dump the returned object.) Okay... Actually this is a structure in the BIOS and the actual method we call is SPLC. The SPLC method may return one item from this table, or something entirely different, possible one of the three values depending on a configuration option or so. Can you to find and send me the actual SPLC method that we call, from your BIOS? -- Cheers, Luca.
Powered by blists - more mailing lists