Andy Shevchenko writes:
> There are a lot of examples in the kernel where PCI_VDEVICE() is used and
> still
> looks not so convenient due to additional driver_data field attached.
>
> Introduce PCI_DEVICE_DATA() macro to fully describe device ID entry in
> shortest
> possible form. For example,
When mac80211 receives a packet, we interate over the list of
active interfaces to find the station(which transmitted the packet).
Currently, station search is not allowed on AP/VLAN interface; since
stations can also get mapped to AP/VLAN interfaces, they are worth
considering for station search.
Hi,
Are there any plans to officially support "Killer/Wireless-AC 9260
wireless cards" in Linux 4.19?
For now this card works using this patch [1] in Manjaro, and also
works for Archlinux distro [2].
Thanks,
Alejandro
[1] "Subject: [PATCH] iwlwifi: add killer cards for 9000 series"
https://gitlab
Hi
Doing some throughput tests I've noticed there are many CCK errors which
mainly occur while receiving data. OFDM errors counted are far less in
numbers than CCK ones, also appearing more often while receiving data. When
transmitting data, the amount of these errors is almost insignificant.
deb
On Sun, 2018-07-29 at 15:49 +0300, Andy Shevchenko wrote:
> On Fri, 2018-07-27 at 16:10 -0500, Bjorn Helgaas wrote:
> Do you think variant with ##vend##dev is better? I will update it for
> v4
> if needed.
Okay, I have sent v4 with your comment addressed.
--
Andy Shevchenko
Intel Finland Oy
some people claim it is hardware limit
On 27 July 2018 at 15:35, Ben Greear wrote:
> Hello,
>
> Has anyone tried making ath9k able to support 16 vAP interfaces on a single
> radio? I seem to recall that there were limitations regarding beacon
> timers and such, and that is why the current limit
There are a lot of examples in the kernel where PCI_VDEVICE() is used and still
looks not so convenient due to additional driver_data field attached.
Introduce PCI_DEVICE_DATA() macro to fully describe device ID entry in shortest
possible form. For example,
before:
{ PCI_VDEVICE(INTEL, PCI
On Fri, 2018-07-27 at 16:10 -0500, Bjorn Helgaas wrote:
> On Fri, Jul 27, 2018 at 11:49:44PM +0300, Andy Shevchenko wrote:
> > There are a lot of examples in the kernel where PCI_VDEVICE() is
> > used and still
> > looks not so convenient due to additional driver_data field
> > attached.
> >
> > I
Make ieee80211_send_layer2_update() a common function so other drivers
can re-use it.
Add support in wil6210 to send L2UF on behalf of newly associated
station by calling the common function.
Change-Id: Ic2daa1b8392122931103eb5a963e14f8270818bb
Signed-off-by: Dedy Lansky
---
drivers/net/wireless
