If it isn't a bug fix and it isn't in patchwork right now, I don't
want to see it.
This time around inappropriate submissions will be silently marked
as "deferred" in patchwork and not even looked at by me.
Thanks.
On 04-09-17 21:33, Steve deRosier wrote:
On Fri, Sep 1, 2017 at 1:02 PM, Arend van Spriel
wrote:
Also note that the wifi chip (the term "radio" does not quite cover it) has
not really lost power. It is quite common that it is not powered through the
SDIO bus.
On Fri, Sep 1, 2017 at 1:02 PM, Arend van Spriel
wrote:
> Also note that the wifi chip (the term "radio" does not quite cover it) has
> not really lost power. It is quite common that it is not powered through the
> SDIO bus. With the power-sequence support in the MMC
There are some HP laptops that contain only a single antenna, which would
not be a problem except these boxes have a mistake in their EFUSE coding.
The ant_sel module option has been provided to correct for this problem;
however, the current antenna selection code has bugs. The first of these
two
In commit bcd37f4a0831 ("rtlwifi: btcoex: 23b 2ant: let bt transmit when
hw initialisation done"), there is an additional error when the module
parameter ant_sel is used to select the auxilary antenna. The error is
that the antenna selection is not checked when writing the antenna
selection
i compared the sources and they are identical to the latest wireless-next
Am 04.09.2017 um 17:00 schrieb Tom Psyborg:
Hi
Have you tried
https://mirror2.openwrt.org/sources/compat-wireless-2017-08-25.tar.xz
to see if it contains same issues?
On 4 September 2017 at 16:08, Sebastian
On 04-09-17 16:42, Antony Antony wrote:
Hi Arend,
On Fri, Sep 01, 2017 at 11:30:59PM +0200, Arend van Spriel wrote:
Hi Rob,
Actually the Broadcom wifi chips themselves are discoverable. So once the
driver has access to the register space of the device it can determine the
actual chip, its
On 4 September 2017 at 23:01, Kalle Valo wrote:
>
> I'll queue this for 4.14. And add a stable tag so that I goes to 4.13
> stable releases:
>
> Cc: # v4.13
>
> --
> Kalle Valo
Thanks.
Hi Arend,
On Fri, Sep 01, 2017 at 11:30:59PM +0200, Arend van Spriel wrote:
> > > Hi Rob,
> > >
> > > Actually the Broadcom wifi chips themselves are discoverable. So once the
> > > driver has access to the register space of the device it can determine the
> > > actual chip, its revision, and
I tested yesterday the current wireless-next tree with backports and
openwrt and also dd-wrt and ath10k
after a few minutes the load was up to 50.0 . after downgrading just
mac80211 to the january version but still using latest ath10k
with some small mods to fit to the api, everything was
Johannes Berg writes:
> On Mon, 2017-08-21 at 15:32 +0200, Toke Høiland-Jørgensen wrote:
>>
>> > + struct ieee80211_vif *vif;
>> > struct ieee80211_key_conf *hw_key;
>> > u32 flags;
>> > - /* 4
On Wed, 2017-08-23 at 17:00 +0200, Håvard Rabbe wrote:
> Hi
>
> Im trying to get wds working. I haven’t found much documentation on
> this topic. This is what i have found: https://wireless.wiki.kernel.o
> rg/en/users/documentation/iw#setting_up_a_wds_peer
>
> I have configured two machines with
On Fri, 2017-09-01 at 13:07 -0700, Thomas Pedersen wrote:
> On Thu, Aug 31, 2017 at 11:30 PM, Greg Maitz
> wrote:
> > Hi guys,
> >
> > I'm seeing a problem when I work on the wireless mesh between two
> > linux devices. The root node has 3.18 kernel while the next hop
> >
Ian W MORRISON writes:
> On 2 September 2017 at 06:04, Arend van Spriel
> wrote:
>> On 31-08-17 00:51, Ian W MORRISON wrote:
>>>
>>> The firmware feature check introduced for multi-scheduled scan is also
>>> failing for bcm4345 devices
(adding netdev and lkml)
Stanislaw Gruszka writes:
> On Fri, Sep 01, 2017 at 05:31:57PM +0300, Kalle Valo wrote:
>> Stanislaw Gruszka writes:
>>
>> > On Thu, Aug 31, 2017 at 10:33:28AM -0500, Larry Finger wrote:
>> >> Should the patch to
Larry Finger writes:
> On 09/01/2017 09:31 AM, Kalle Valo wrote:
>> Stanislaw Gruszka writes:
>>
>>> On Thu, Aug 31, 2017 at 10:33:28AM -0500, Larry Finger wrote:
Should the patch to wireless-drivers be annotated with a Stable reference
On Mon, 2017-09-04 at 13:43 +0200, Jiri Kosina wrote:
> On Thu, 24 Aug 2017, Luca Coelho wrote:
>
> > > looks like a correct fix to me, so feel free to add
> > >
> > > Acked-by: Jiri Kosina
> > >
> > > I'll be able to provide my Tested-by: eventually only in ~10 days.
> >
>
On Thu, 24 Aug 2017, Luca Coelho wrote:
> > looks like a correct fix to me, so feel free to add
> >
> > Acked-by: Jiri Kosina
> >
> > I'll be able to provide my Tested-by: eventually only in ~10 days.
>
>
> Kalle already picked it up in wireless-drivers and this should
On Tue, Aug 29, 2017 at 02:23:41PM +0800, Wright Feng wrote:
> From: Chung-Hsien Hsu
>
> The firmware for brcmfmac devices includes information regarding
> regulatory constraints. For certain devices this information is kept
> separately in a binary form that needs to be
For the whole patch set:
Reviewed-by: Sergey Matyukevich
On Mon, 2017-08-21 at 15:32 +0200, Toke Høiland-Jørgensen wrote:
>
> > + struct ieee80211_vif *vif;
> > struct ieee80211_key_conf *hw_key;
> > u32 flags;
> > - /* 4 bytes free */
> > + codel_time_t
Hi Carl,
On Sun, 2017-09-03 at 12:15 -0700, Carl Myers wrote:
> Greetings all,
>
> Apologies if any of this is wrong, this is my first attempt to report a bug in
> the linux kernel =)
>
> I got here by running the get_maintainer script on the iwlwifi directory of a
> linux kernel checkout.
>
>
Firmware returns proprietary error code when getting error in
fil_cmd_data_set or fil_cmd_data_get. The vendor tools or
utilities which uses libnl may stuck in some commands when wl is down.
For example, issue "scan" command after issuing "down" command, the
"scan" command will be the blocking
23 matches
Mail list logo