On Wed, Oct 12, 2016 at 1:05 PM, Paul Bolle <pebo...@tiscali.nl> wrote:
> On Wed, 2016-10-12 at 12:50 -0500, Chris Rorvick wrote:
>> This may already be apparent, but Dell sells two versions of the 9350:
>> one with the Broadcom adapter and one with the AC 8260.
>
> Off
On Tue, Oct 11, 2016 at 9:09 AM, Chris Rorvick <ch...@rorvick.com> wrote:
> I didn't receive your email so I'll try to respond via Paul's.
>>> If this is really bothering you, I guess I could apply this patch for
>>> now. But as I said, this is not solving the actual
Hi Luca,
I didn't receive your email so I'll try to respond via Paul's.
On Tue, Oct 11, 2016 at 5:11 AM, Paul Bolle wrote:
>> This is not coming from the NIC itself, but from the platform's ACPI
>> tables. Can you tell us which platform you are using?
Interesting. I'm
On Tue, Oct 11, 2016 at 5:11 AM, Paul Bolle wrote:
> For what it's worth, on my machine I have twenty (!) SPLX entries, all
> reading:
> Name (SPLX, Package (0x04)
> {
> Zero,
> Package (0x03)
> {
> 0x8000,
>
Hi Luca,
> On Thu, 2016-10-13 at 13:21 +0300, Luca Coelho wrote:
> Could you please give this a spin? I have tested it with some handmade
> ACPI tables in QEMU and it seems to work fine now.
Tested-by: Chris Rorvick <ch...@rorvick.com>
I think the debug output looks as expe
eing fully functional after initialization, the
above condition is reported as an error. Knock the message down to a
warning and provide better context for understanding its consequence.
Signed-off-by: Chris Rorvick <ch...@rorvick.com>
---
drivers/net/wireless/intel/iwlwifi/pcie/drv.c | 2 +-
1
Hi Luca,
FYI, It seems that Google does not like your email as I'm not
receiving any of your messages in gmail. Some responses below:
On Wed, 2016-10-12 at 15:24 +0300, Luca Coelho wrote:
> Hi Chris,
> On Tue, 2016-10-11 at 09:09 -0500, Chris Rorvick wrote:
> > On Tue, Oct 11, 201