This patch fixes the "Lines should not end with a '('"
problem reported by checkpatch
Signed-off-by: Aditya Shankar
---
drivers/staging/wilc1000/linux_mon.c | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wilc1000/linux_mon.c
b/drivers/staging/wi
This commit fixes below style problems in multiple lines
Fix checkpatch WARNING: line over 80 characters
Signed-off-by: Aditya Shankar
---
drivers/staging/wilc1000/linux_mon.c | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/drivers/staging/wilc1000/linux_m
Hi,
I am attempting to get AP mode working with an RTL8188CU device. I'm using the
rtl8192cu driver from backports-4.2.6-1 with hostapd 2.6, but this doesn't seem
to be working. I can provide details if needed, but for now I'd just like to
know if AP mode is supported using vanilla kernel driver
On Mon, Dec 11, 2017 at 10:55:18AM +0100, Arend van Spriel wrote:
> On 12/11/2017 9:11 AM, Chi-Hsien Lin wrote:
> > broken_sg_support, sd_head_align, and sd_sgentry_align are used in
> > brcmfmac code but not configurable in dts file. Add the parsing logic.
> > Now they can be configured like below
Ha! I didn't realize those were two separate drivers. Blacklisting
rtl8xxxu made it work consistently. The throughput is still about 1/2
what it is in Windows 10, but at least it works! Thanks.
On Mon, Dec 11, 2017 at 9:21 PM, Larry Finger wrote:
> On 12/11/2017 06:59 PM, James Hemsing wrote:
>>
Hi Amitkumar,
On Wed, 2017-12-06 at 12:43 +0530, Amitkumar Karwar wrote:
> On Tue, Dec 5, 2017 at 9:41 PM, Alexey Brodkin
> wrote:
> > Hi Amit,
> >
> > I'm seeing quite a strange behavior of RedPine module.
> > It connects perfectly fine to one of access points but fails
> > to connect to anothe
Hi Prameela,
On Fri, 2017-12-15 at 18:14 +0530, Prameela Rani Garnepudi wrote:
> Hi Alexey,
>
>
> On Friday 15 December 2017 04:50 PM, Alexey Brodkin wrote:
> > Hi Prameela,
> >
> > On Fri, 2017-12-15 at 11:13 +0530, Prameela Rani Garnepudi wrote:
> >> Hi Alexey,
> >>
> >> Please use the
On Fri, Dec 15, 2017 at 12:10:34PM +0100, Arend van Spriel wrote:
> # cat /sys/kernel/debug/brcmfmac/:03:00.0/revinfo
vendorid: 0x14e4
deviceid: 0x43ec
radiorev: 0.41.32.105
chipnum: 17238 (4356)
chiprev: 2
chippkg: 2
corerev: 48
boardid: 0x0777
boardvendor: 0x14e4
boardrev: P103
driverrev: 7.
Hi Prameela,
On Fri, 2017-12-15 at 11:13 +0530, Prameela Rani Garnepudi wrote:
> Hi Alexey,
>
> Please use the attached patch to improve TX throughput. We will be
> submitting this patch along with few others soon.
Could you please specify which branch this patch is based on?
I tried to apply
On 12/15/2017 11:32 AM, Stanislaw Gruszka wrote:
On Fri, Dec 15, 2017 at 10:58:10AM +0100, Arend van Spriel wrote:
On 12/14/2017 3:22 PM, Stanislaw Gruszka wrote:
On Thu, Dec 14, 2017 at 10:13:29AM +0100, Arend van Spriel wrote:
The cur_etheraddr is the first piece of info we try to get from t
On Fri, Dec 15, 2017 at 10:58:10AM +0100, Arend van Spriel wrote:
> On 12/14/2017 3:22 PM, Stanislaw Gruszka wrote:
> >On Thu, Dec 14, 2017 at 10:13:29AM +0100, Arend van Spriel wrote:
> >>The cur_etheraddr is the first piece of info we try to get from the
> >>firmware. Could you build the driver w
On 12/14/2017 3:22 PM, Stanislaw Gruszka wrote:
On Thu, Dec 14, 2017 at 10:13:29AM +0100, Arend van Spriel wrote:
The cur_etheraddr is the first piece of info we try to get from the
firmware. Could you build the driver with CONFIG_BRCMDBG and load
the module with 'debug=0x181416'.
dmesg attach
On 12/14/2017 7:16 PM, Sunil Dutt Undekari wrote:
Can't we have some kind of capability indication that the driver supports each
of these flags or not? Otherwise we get into a situation where you just have
to try the flag and hope it works, since it doesn't look like drivers are
required to e
On 12/15/2017 9:51 AM, Srinivas Dasari wrote:
don’t we actually need a flag in NL80211_CMD_CONNECT that indicates that userspace
is able to actually handle NL80211_CMD_EXTERNAL_AUTH. It is nice >that there is
feature for userspace to see if the driver supports it, but how is the driver able
to
>don’t we actually need a flag in NL80211_CMD_CONNECT that indicates that
>userspace is able to actually handle NL80211_CMD_EXTERNAL_AUTH. It is nice
>>that there is feature for userspace to see if the driver supports it, but how
>is the driver able to offload successfully if it doesn’t know tha
15 matches
Mail list logo
