(Adding AceLan)
Daniel Drake writes:
> On Wed, Nov 15, 2017 at 7:38 AM, Daniel Drake wrote:
>> On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo wrote:
Can't be fixed in firmware, but it would be good to have confirmation
of the hardware behavivour, and maybe some other solution is possibl
On Mon, Jan 8, 2018 at 2:24 PM, Kalle Valo wrote:
> (Adding AceLan)
>
> Daniel Drake writes:
>
>> On Wed, Nov 15, 2017 at 7:38 AM, Daniel Drake wrote:
>>> On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo wrote:
> Can't be fixed in firmware, but it would be good to have confirmation
> of the
On Mon, Jan 8, 2018 at 6:24 AM, Kalle Valo wrote:
> (Adding AceLan)
>
> Daniel Drake writes:
>
>> On Wed, Nov 15, 2017 at 7:38 AM, Daniel Drake wrote:
>>> On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo wrote:
> Can't be fixed in firmware, but it would be good to have confirmation
> of the
Hi Kalle,
I'm happy to see Russel's patch can be merged,
and I'm willing to rebase and merge those quirks into one commit and
submit it again.
Although the solution is not perfect, but it's nice to have.
Thanks.
Best regards,
AceLan Kao.
2018-01-09 7:07 GMT+08:00 Daniel Drake :
> On Mon, Jan 8,
Russell Hu wrote:
> On new Intel platforms like ApolloLake, legacy interrupt mechanism
> (INTx) is not supported, so WLAN modules are not working because
> interrupts are missing, therefore this patch is to add MSI support to
> ath9k. With module paremeter "use_msi=1", ath9k driver would try to
On new Intel platforms like ApolloLake, legacy interrupt mechanism
(INTx) is not supported, so WLAN modules are not working because
interrupts are missing, therefore this patch is to add MSI support to
ath9k. With module paremeter "use_msi=1", ath9k driver would try to
use MSI instead of INTx.
Si
Hi Russell,
> On new Intel platforms like ApolloLake, legacy interrupt mechanism
> (INTx) is not supported
Could you please share the background on what you are claiming here.
I have multiple ApolloLake laptops here with many legacy interrupts
being used in /proc/interrupts.
I do see this ath9k
Daniel Drake writes:
>> On new Intel platforms like ApolloLake, legacy interrupt mechanism
>> (INTx) is not supported
>
> Could you please share the background on what you are claiming here.
> I have multiple ApolloLake laptops here with many legacy interrupts
> being used in /proc/interrupts.
>
On Mon, Nov 13, 2017 at 4:48 PM, Kalle Valo wrote:
> Enabling MSI by default is just too invasive, ath9k is used in so many
> different enviroments that risk of regressions is high. MSI needs a lot
> of testing before we can even consider enabling it by default.
And it seems like we already found
Daniel Drake writes:
> On Mon, Nov 13, 2017 at 4:48 PM, Kalle Valo wrote:
>> Enabling MSI by default is just too invasive, ath9k is used in so many
>> different enviroments that risk of regressions is high. MSI needs a lot
>> of testing before we can even consider enabling it by default.
>
> And
On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo wrote:
>> Can't be fixed in firmware, but it would be good to have confirmation
>> of the hardware behavivour, and maybe some other solution is possible?
>> Are you following this up within Qualcomm?
>
> No time to do that right now, sorry.
I got severa
On Wed, Nov 15, 2017 at 7:38 AM, Daniel Drake wrote:
> On Tue, Nov 14, 2017 at 8:15 PM, Kalle Valo wrote:
>>> Can't be fixed in firmware, but it would be good to have confirmation
>>> of the hardware behavivour, and maybe some other solution is possible?
>>> Are you following this up within Qualc
12 matches
Mail list logo
