On 28 December 2016 at 22:35, Felix Fietkau wrote:
> On 2016-12-28 16:59, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> This new file should be used for properties handled at higher level and
>> so usable with all drivers.
>>
>> Signed-off-by: Rafał Miłecki
>> ---
>> .../devicetree/bindings
From: Ping-Ke Shih
The addresses of Wlan NIC registers are natural alignment, but some
drivers have bugs. These are evident on platforms that need natural
alignment to access registers. This change contains the following:
1. Function _rtl8821ae_dbi_read() is used to read one byte from DBI,
On 28 December 2016 at 22:07, Arend van Spriel
wrote:
> On 28-12-16 16:59, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> They allow specifying hardware limitations of supported channels. This
>> may be useful for specifying single band devices or devices that support
>> only some part of the
On 2016-12-28 16:59, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This new file should be used for properties handled at higher level and
> so usable with all drivers.
>
> Signed-off-by: Rafał Miłecki
> ---
> .../devicetree/bindings/net/wireless/ieee80211.txt | 16
>
>
On 28 December 2016 at 22:28, Rafał Miłecki wrote:
> On 28 December 2016 at 22:07, Arend van Spriel
> wrote:
>> On 28-12-16 16:59, Rafał Miłecki wrote:
>>> From: Rafał Miłecki
>>>
>>> They allow specifying hardware limitations of supported channels. This
>>> may be useful for specifying single b
On 28-12-16 16:59, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> They allow specifying hardware limitations of supported channels. This
> may be useful for specifying single band devices or devices that support
> only some part of the whole band.
> E.g. some tri-band routers have separated radio
On 28 December 2016 at 21:39, Martin Blumenstingl
wrote:
> On Wed, Dec 28, 2016 at 9:32 PM, Rafał Miłecki wrote:
>> On 28 December 2016 at 21:05, Arend van Spriel
>> wrote:
>>> On 28-12-16 16:59, Rafał Miłecki wrote:
From: Rafał Miłecki
This new file should be used for properties
On Wed, Dec 28, 2016 at 9:32 PM, Rafał Miłecki wrote:
> On 28 December 2016 at 21:05, Arend van Spriel
> wrote:
>> On 28-12-16 16:59, Rafał Miłecki wrote:
>>> From: Rafał Miłecki
>>>
>>> This new file should be used for properties handled at higher level and
>>> so usable with all drivers.
>>>
>
On 28 December 2016 at 21:05, Arend van Spriel
wrote:
> On 28-12-16 16:59, Rafał Miłecki wrote:
>> From: Rafał Miłecki
>>
>> This new file should be used for properties handled at higher level and
>> so usable with all drivers.
>>
>> Signed-off-by: Rafał Miłecki
>> ---
>> .../devicetree/binding
On 28-12-16 16:59, Rafał Miłecki wrote:
> From: Rafał Miłecki
>
> This new file should be used for properties handled at higher level and
> so usable with all drivers.
>
> Signed-off-by: Rafał Miłecki
> ---
> .../devicetree/bindings/net/wireless/ieee80211.txt | 16
>
>
Change order of free_irq and dev unregistration.
It fixes situation when device already unregistered and
an interrupt happens and nobody can handle it.
Signed-off-by: Andrey Rusalin
---
drivers/nfc/pn533/i2c.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/nfc/pn
Make sure cmd is set before a frame is passed to the transport layer for
sending. In addition pn533_send_async_complete checks if cmd is set before
accessing its members.
Signed-off-by: Michael Thalmeier
Rework a little bit changes in pn532_send_async_complete.
Signed-off-by: Andrey Rusalin
--
Each of these patches fix some oops that I met during
tests of the driver with itead pn532 nfc module.
First and third patches related to order of initialization driver,
where interrupt handler was registered before work queues
were ready to handle it.
Also iqr was freed already after work queue
Sometimes during probing and registration of pn533_i2c
NULL pointer dereference happens.
Reproduced in cycle of inserting and removing pn533_i2c
and pn533 modules.
Backtrace:
[<8004205c>] (__queue_work) from [<80042324>] (queue_work_on+0x50/0x5c)
r10:acdc7c80 r9:8006b330 r8:ac0dfb40 r7:ac50c600 r6
I have been fighting this laptop (MacBookPro11,5) for a year now with
linux (mainly on Thunderbolt and power issues), but this is one of the
last ones that remains.
The system contains a BCM 43602 (rebranded by Apple of course):
04:00.0 Network controller [0280]: Broadcom Limited BCM43602 802.11a
From: Rafał Miłecki
They allow specifying hardware limitations of supported channels. This
may be useful for specifying single band devices or devices that support
only some part of the whole band.
E.g. some tri-band routers have separated radios for lower and higher
part of 5 GHz band.
Signed-o
From: Rafał Miłecki
This new file should be used for properties handled at higher level and
so usable with all drivers.
Signed-off-by: Rafał Miłecki
---
.../devicetree/bindings/net/wireless/ieee80211.txt | 16
1 file changed, 16 insertions(+)
create mode 100644 Document
On 28 December 2016 at 14:28, Rafał Miłecki wrote:
> On 28 December 2016 at 11:43, Martin Blumenstingl
> wrote:
>> should we describe the center freq in Hz or MHz (cfg80211's
>> ieee80211_channel uses the latter)?
>
> Is there any case that may require HZ accuracy? I was thinking about using
> M
On 28 December 2016 at 11:43, Martin Blumenstingl
wrote:
> On Wed, Dec 28, 2016 at 11:08 AM, Rafał Miłecki wrote:
>> On 3 October 2016 at 15:29, Kalle Valo wrote:
>>> Arnd Bergmann writes:
>>>
On Friday 30 September 2016, Felix Fietkau wrote:
> >> >> >> + device_type =
Luca Coelho writes:
> On Wed, 2016-12-28 at 11:59 +0800, Peter Xu wrote:
>> On Tue, Dec 27, 2016 at 09:46:55PM +0200, Kalle Valo wrote:
>> > Peter Xu writes:
>> >
>> > > Looks like latest Linux master (4.10-rc1, 7ce7d89f) cannot work well
>> > > with my wireless card, which is:
>> > >
>> > >
On Wed, Dec 28, 2016 at 11:08 AM, Rafał Miłecki wrote:
> On 3 October 2016 at 15:29, Kalle Valo wrote:
>> Arnd Bergmann writes:
>>
>>> On Friday 30 September 2016, Felix Fietkau wrote:
>> >> >> + device_type = "pci";
>> >> >> + mediatek,mtd-eeprom = <&fa
On 3 October 2016 at 15:29, Kalle Valo wrote:
> Arnd Bergmann writes:
>
>> On Friday 30 September 2016, Felix Fietkau wrote:
>>> >> >> >> + device_type = "pci";
>>> >> >> >> + mediatek,mtd-eeprom = <&factory 0x8000>;
>>> >> >> >> + mediatek,2ghz = <
On Wed, 2016-12-28 at 10:17 +0200, Emmanuel Grumbach wrote:
> On Wed, Dec 28, 2016 at 10:10 AM, Peter Xu wrote:
> > On Wed, Dec 28, 2016 at 09:27:15AM +0200, Luca Coelho wrote:
> >
> > [...]
> >
> > > > > > Is this a known issue? Please let me know if anyone wants more info
> > > > > > or
> >
On Wed, Dec 28, 2016 at 10:10 AM, Peter Xu wrote:
> On Wed, Dec 28, 2016 at 09:27:15AM +0200, Luca Coelho wrote:
>
> [...]
>
>> > > > Is this a known issue? Please let me know if anyone wants more info or
>> > > > logs, since this error triggers easily (everytime I boot).
>> > >
>> > > The error m
On Wed, Dec 28, 2016 at 09:27:15AM +0200, Luca Coelho wrote:
[...]
> > > > Is this a known issue? Please let me know if anyone wants more info or
> > > > logs, since this error triggers easily (everytime I boot).
> > >
> > > The error message isn't really telling much to the user (hint hint) but
25 matches
Mail list logo
