Using 4.4-rc4 and today's wireless-testing (master-2015-12-10), and
the latest firmware on linux-firmware, my wireless driver runs into a
non-functional loop rambling about "L1 Enabled - LTR Enabled loop".
Reverting back to an older kernel works. I could bisect *if this issue
is not known*, but it
On Fri, Dec 11, 2015 at 10:59 AM, Luis R. Rodriguez
wrote:
> I could bisect *if this issue
> is not known*, but it may take a while...
So this is interesting..
The opensuse 4.2.4 kernel worked, but I tried my own vanilla 4.2.4
kernel and that didn't work. This lead me to believe this
On Sun, Aug 30, 2015 at 11:11 AM, Linus Torvalds
wrote:
> On Sun, Aug 30, 2015 at 1:25 AM, Arend van Spriel wrote:
>> On 08/29/2015 12:38 PM, Ming Lei wrote:
>>
>> Does this mean a built-in driver can not get firmware from initramfs or
>> built in the kernel early. Seems a bit too aggressive.
>
>
The subject should probably be: ima: add support to load policy from path
Cc'ing Roberts who originally wanted SELinux file policy signing capabilities.
Also Greg, who is reviewing the sysdata file changes I had proposed which would
provide a generic file loading facility for modules, and later a
On Thu, Dec 17, 2015 at 11:33 AM, Luis R. Rodriguez wrote:
> Please no, instead of adding yet-another kernel file-loading facility which is
> likely error prone we should consolidate *all kernel file-loading facilities*
> into a *common generic shared one*. So please work to make th
On Mon, Jun 27, 2016 at 01:38:43AM +0200, Martin Blumenstingl wrote:
> On Sat, Jun 25, 2016 at 9:26 PM, Christian Lamparter
> wrote:
> > I've added lede-dev and Luis since this is relevant for them.
> > Maybe between the sysloadfw.sh and owl-loader, there's another
> > solution we overlooked so fa
On Fri, Jul 22, 2016 at 10:38:24AM +0200, Arend Van Spriel wrote:
> + Luis
>
> On 21-7-2016 13:51, Stanislaw Gruszka wrote:
> > (cc: firmware and brcmfmac maintainers)
> >
> > On Thu, Jul 21, 2016 at 06:23:11AM -0400, Prarit Bhargava wrote:
> >>
> >>
> >> On 07/21/2016 04:05 AM, Stanislaw Gruszka
On Fri, Jul 22, 2016 at 12:26:00PM +0200, Stanislaw Gruszka wrote:
> On Fri, Jul 22, 2016 at 10:38:24AM +0200, Arend Van Spriel wrote:
> > + Luis
> >
> > On 21-7-2016 13:51, Stanislaw Gruszka wrote:
> > > (cc: firmware and brcmfmac maintainers)
> > >
> > > On Thu, Jul 21, 2016 at 06:23:11AM -0400
On Fri, Jul 22, 2016 at 08:51:36AM -0400, Prarit Bhargava wrote:
> On 07/22/2016 08:21 AM, Arend Van Spriel wrote:
> >> Another option to solve to problem would be stop requesting not
> >> available publicly firmware. However, I assume some drivers would
> >> like to preserve that option.
> >
> >
On Thu, Jul 28, 2016 at 09:23:35PM +0200, Arend van Spriel wrote:
> On 23-07-16 00:05, Luis R. Rodriguez wrote:
> > The firmware API is a mess and I've been trying to correct that
> > with a more flexible API.
<-- snip -->
> > Extensions to the fw API are IMHO be
On Sat, Jul 30, 2016 at 02:42:41PM +0200, Arend van Spriel wrote:
> + Luis (again) ;-)
>
> On 29-07-16 08:13, Daniel Wagner wrote:
> > On 07/28/2016 09:01 PM, Bjorn Andersson wrote:
> >> On Thu 28 Jul 11:33 PDT 2016, Dmitry Torokhov wrote:
> >>
> >>> On Thu, Jul 28, 2016 at 09:55:11AM +0200, Danie
On Mon, Aug 01, 2016 at 02:26:04PM +0200, Daniel Wagner wrote:
> On 07/31/2016 09:23 AM, Dmitry Torokhov wrote:
> >On July 30, 2016 9:58:17 AM PDT, "Luis R. Rodriguez"
> >wrote:
> >>On Sat, Jul 30, 2016 at 02:42:41PM +0200, Arend van Spriel wrote:
> >
On Sun, Jul 31, 2016 at 12:23:09AM -0700, Dmitry Torokhov wrote:
> On July 30, 2016 9:58:17 AM PDT, "Luis R. Rodriguez"
> wrote:
> >On Sat, Jul 30, 2016 at 02:42:41PM +0200, Arend van Spriel wrote:
> >> + Luis (again) ;-)
> >>
> >> On 29-07-16 08
On Mon, Aug 01, 2016 at 10:19:51AM -0700, Bjorn Andersson wrote:
> On Sat 30 Jul 09:58 PDT 2016, Luis R. Rodriguez wrote:
>
> > On Sat, Jul 30, 2016 at 02:42:41PM +0200, Arend van Spriel wrote:
> > > + Luis (again) ;-)
> > >
> > > On 29-07-16 08:13, Daniel
On Tue, Aug 02, 2016 at 07:49:19AM +0200, Daniel Wagner wrote:
> >The sysdata API's main goal rather is to provide a flexible API first,
> >compartamentalizing the usermode helper was secondary. But now it seems
> >I may just also add devm support too to help simplify code further.
>
> I missed th
On Tue, Aug 02, 2016 at 08:53:55AM +0200, Daniel Wagner wrote:
> On 08/02/2016 08:34 AM, Luis R. Rodriguez wrote:
> >On Tue, Aug 02, 2016 at 07:49:19AM +0200, Daniel Wagner wrote:
> >>>The sysdata API's main goal rather is to provide a flexible API first,
> >&g
On Tue, Aug 02, 2016 at 11:10:22AM +, Valo, Kalle wrote:
> "Luis R. Rodriguez" writes:
>
> > I was considering this as a future extension to the firmware API
> > through the new extensible firmware API, the sysdata API.
>
> I think Linus mentioned thi
On Wed, Aug 03, 2016 at 01:33:31PM +0200, Arend van Spriel wrote:
> On 02-08-16 16:16, Luis R. Rodriguez wrote:
> > On Tue, Aug 02, 2016 at 11:10:22AM +, Valo, Kalle wrote:
> >> "Luis R. Rodriguez" writes:
> >>
> >>> I was consideri
On Wed, Aug 03, 2016 at 01:43:31PM +0200, Arend van Spriel wrote:
> On 03-08-16 09:42, Dmitry Torokhov wrote:
> > On Tue, Aug 2, 2016 at 12:41 AM, Luis R. Rodriguez
> > wrote:
> >> On Tue, Aug 02, 2016 at 08:53:55AM +0200, Daniel Wagner wrote:
> >>> On 08
On Wed, Aug 03, 2016 at 12:42:14AM -0700, Dmitry Torokhov wrote:
> On Tue, Aug 2, 2016 at 12:41 AM, Luis R. Rodriguez wrote:
> > On Tue, Aug 02, 2016 at 08:53:55AM +0200, Daniel Wagner wrote:
> >> On 08/02/2016 08:34 AM, Luis R. Rodriguez wrote:
> >> >On Tue, Au
On Wed, Aug 03, 2016 at 08:57:09AM +0200, Daniel Wagner wrote:
> On 08/02/2016 09:41 AM, Luis R. Rodriguez wrote:
> >On Tue, Aug 02, 2016 at 08:53:55AM +0200, Daniel Wagner wrote:
> >>On 08/02/2016 08:34 AM, Luis R. Rodriguez wrote:
> >>>On Tue, Aug 02, 2016 at 0
On Wed, Aug 03, 2016 at 03:04:39PM +, Valo, Kalle wrote:
> "Luis R. Rodriguez" writes:
>
> > On Wed, Aug 03, 2016 at 01:33:31PM +0200, Arend van Spriel wrote:
> >> On 02-08-16 16:16, Luis R. Rodriguez wrote:
> >> > On Tue, Aug 02, 2016 at 11:10:22A
On Wed, Aug 03, 2016 at 09:18:21AM -0700, Dmitry Torokhov wrote:
> On Wed, Aug 03, 2016 at 05:55:40PM +0200, Luis R. Rodriguez wrote:
> >
> > I accept all help and would be glad to make enhancements instead of
> > the old API through new API. The biggest thing here first
On Wed, Aug 03, 2016 at 05:55:40PM +0200, Luis R. Rodriguez wrote:
> On Wed, Aug 03, 2016 at 08:57:09AM +0200, Daniel Wagner wrote:
> > On 08/02/2016 09:41 AM, Luis R. Rodriguez wrote:
> > >On Tue, Aug 02, 2016 at 08:53:55AM +0200, Daniel Wagner wrote:
> > >>
On Wed, Aug 03, 2016 at 10:39:55AM -0700, Bjorn Andersson wrote:
> On Tue 02 Aug 00:41 PDT 2016, Luis R. Rodriguez wrote:
>
> > On Tue, Aug 02, 2016 at 08:53:55AM +0200, Daniel Wagner wrote:
> > > On 08/02/2016 08:34 AM, Luis R. Rodriguez wrote:
> > > >On Tue,
On Wed, Aug 10, 2016 at 09:04:38PM +0200, Arend Van Spriel wrote:
> On 10-8-2016 20:32, Luis R. Rodriguez wrote:
> > On Fri, Jun 17, 2016 at 08:35:03PM +0200, Luis R. Rodriguez wrote:
> >> On Thu, Jun 16, 2016 at 05:09:30PM -1000, Linus Torvalds wrote:
> >>> On Thu, J
On Wed, Aug 10, 2016 at 08:17:08PM +0100, Mark Brown wrote:
> On Wed, Aug 10, 2016 at 09:04:38PM +0200, Arend Van Spriel wrote:
>
> > So why would drivers want the devm solution anyway. Once firmware is
> > loaded in the device it can be freed or do you expect device drivers to
> > keep the firmwa
On Fri, Jun 17, 2016 at 08:35:03PM +0200, Luis R. Rodriguez wrote:
> On Thu, Jun 16, 2016 at 05:09:30PM -1000, Linus Torvalds wrote:
> > On Thu, Jun 16, 2016 at 3:36 PM, Luis R. Rodriguez
> > wrote:
> > >
> > > Reason this could not wait is folks seem to want
On Thu, Aug 18, 2016 at 03:12:04PM +0200, Daniel Wagner wrote:
> This series ignores all complete_all() usages in the firmware loading
> path. They will be hopefully address by Luis' sysdata patches [0].
> That leaves a couple of complete_all() calls.
I had not considered this as a gain, but glad
On Wed, Aug 26, 2015 at 03:33:04PM +0100, David Howells wrote:
> Luis R. Rodriguez wrote:
>
> > But note, we also have kexec_file_load() syscall and an arch specific
> > signature verification feature, arch_kexec_kernel_verify_sig().
> > Sad trombone, no LSM hook an
On Wed, Aug 26, 2015 at 10:35:19PM -0400, Paul Moore wrote:
> On Wed, Aug 26, 2015 at 7:26 PM, Luis R. Rodriguez wrote:
> > On Wed, Aug 26, 2015 at 03:33:04PM +0100, David Howells wrote:
> > Now let's review the SELinux stuff before we jump back into firmware /
> > syst
On Thu, Aug 27, 2015 at 11:38:58AM +0100, David Howells wrote:
> Luis R. Rodriguez wrote:
>
> > "PKCS#7: Add an optional authenticated attribute to hold firmware name"
> > https://git.kernel.org/cgit/linux/kernel/git/dhowells/linux-fs.g
On Thu, Aug 27, 2015 at 10:57:23AM -, David Woodhouse wrote:
> > Luis R. Rodriguez wrote:
> >
> >> "PKCS#7: Add an optional authenticated attribute to hold firmware name"
> >> https://git.kernel.org/cgit/linux/kernel/git/dhowell
On Fri, Aug 28, 2015 at 11:20:10AM +, Roberts, William C wrote:
> > -Original Message-
> > From: Paul Moore [mailto:p...@paul-moore.com]
> >
> > While I question the usefulness of a SELinux policy signature in the
> > general case,
> > there are some situations where it might make sen
On Fri, Aug 28, 2015 at 06:26:05PM -0400, Paul Moore wrote:
> On Fri, Aug 28, 2015 at 7:20 AM, Roberts, William C
> wrote:
> > Even triggered updates make sense, since you can at least have some form of
> > trust
> > of where that binary policy came from.
>
> It isn't always that simple, see my
On Thu, Aug 27, 2015 at 07:54:33PM -0400, Mimi Zohar wrote:
> On Thu, 2015-08-27 at 23:29 +0200, Luis R. Rodriguez wrote:
> > On Thu, Aug 27, 2015 at 10:57:23AM -, David Woodhouse wrote:
> > > > Luis R. Rodriguez wrote:
> > > >
> > > >> "PK
On Mon, Aug 31, 2015 at 10:18:55AM -0400, Mimi Zohar wrote:
> On Sat, 2015-08-29 at 04:16 +0200, Luis R. Rodriguez wrote:
> > On Thu, Aug 27, 2015 at 07:54:33PM -0400, Mimi Zohar wrote:
> > > On Thu, 2015-08-27 at 23:29 +0200, Luis R. Rodriguez wrote:
> > > > On T
On Mon, Aug 31, 2015 at 12:45:36PM -0400, Mimi Zohar wrote:
> On Mon, 2015-08-31 at 17:05 +0100, David Woodhouse wrote:
> > On Mon, 2015-08-31 at 10:18 -0400, Mimi Zohar wrote:
> > > I'm not real happy about it, but since we can't break the existing ABI
> > > of loading data into the kernel via a b
On Tue, Sep 01, 2015 at 01:20:37PM -0700, Kees Cook wrote:
> On Thu, Aug 27, 2015 at 2:29 PM, Luis R. Rodriguez wrote:
> > On Thu, Aug 27, 2015 at 10:57:23AM -, David Woodhouse wrote:
> > Right so now that firmware usermode helper is behind us (systemd ripped it)
> > we
On Tue, Sep 01, 2015 at 11:35:05PM -0400, Mimi Zohar wrote:
> > OK great, I think that instead of passing the actual routine name we should
> > instead pass an enum type for to the LSM, that'd be easier to parse and we'd
> > then have each case well documented. Each LSM then could add its own
> > d
On Wed, Sep 02, 2015 at 01:54:43PM -0700, Kees Cook wrote:
> On Wed, Sep 2, 2015 at 11:46 AM, Luis R. Rodriguez wrote:
> > On Tue, Sep 01, 2015 at 11:35:05PM -0400, Mimi Zohar wrote:
> >> > OK great, I think that instead of passing the actual routine name we
> >> &
On Wed, Sep 02, 2015 at 07:54:13PM -0400, Mimi Zohar wrote:
> On Wed, 2015-09-02 at 01:43 +0200, Luis R. Rodriguez wrote:
> > On Mon, Aug 31, 2015 at 10:18:55AM -0400, Mimi Zohar wrote:
> > > On Sat, 2015-08-29 at 04:16 +0200, Luis R. Rodriguez wrote:
> > > > On T
On Wed, Sep 02, 2015 at 08:05:36PM -0400, Mimi Zohar wrote:
> On Wed, 2015-09-02 at 20:46 +0200, Luis R. Rodriguez wrote:
> > On Tue, Sep 01, 2015 at 11:35:05PM -0400, Mimi Zohar wrote:
> > > > OK great, I think that instead of passing the actual routine name we
> >
On Thu, Sep 03, 2015 at 02:14:18PM -0700, Kees Cook wrote:
> [removed bounced email addresses]
>
> On Wed, Sep 2, 2015 at 2:37 PM, Luis R. Rodriguez wrote:
> > On Wed, Sep 02, 2015 at 01:54:43PM -0700, Kees Cook wrote:
> >> On Wed, Sep 2, 2015 at 11:46 AM, Luis R. Rodrigu
g for country/rules
crda: db2rd, parse/print CAC time
John W. Linville (1):
crda: Add DESTDIR support in install-libreg* rules in Makefile
Krishna Chaitanya (1):
crda: Fix the linking order to avoid compilation error
Luis R. Rodriguez (1):
crda: document contribution process
On Mon, Feb 02, 2015 at 09:59:25AM -0500, Ilan Peer wrote:
> As the operating environment of a device can change, add
> API for user space to indicate a change of indoor settings.
> In addition modify the handling of the indoor processing as
> follows:
>
> 1. Directly update the indoor setting wit
Change this by scheduling a timeout every time CRDA is called. In
> addition, in restore_regulatory_settings() all pending requests are
> restored (and not only the user ones).
>
> Signed-off-by: Ilan Peer
Reviewed-by: Luis R. Rodriguez
Luis
--
To unsubscribe from this list: send
On Sun, Feb 08, 2015 at 09:10:01AM +, Peer, Ilan wrote:
> Hi Luis,
>
> > -Original Message-
> > From: Luis R. Rodriguez [mailto:mcg...@suse.com]
> > Sent: Saturday, February 07, 2015 01:58
> > To: Peer, Ilan
> > Cc: linux-wireless@vger.kernel.org; A
Wider community:
anyone aware of any *need* in the kernel to know whether one is indoor or
not on a device running Linux other than wifi? Clearly it should be something
that might be of interest to at least other RF devices, so that is at least
one possibilty to consider already, but what else?
O
On Thu, Feb 19, 2015 at 5:03 PM, wrote:
> On Fri, 20 Feb 2015 01:53:44 +0100, "Luis R. Rodriguez" said:
>> Wider community:
>>
>> anyone aware of any *need* in the kernel to know whether one is indoor or
>> not on a device running Linux other than wifi? C
On Fri, Feb 20, 2015 at 7:02 AM, Jonathan Bither wrote:
> On 02/19/2015 08:03 PM, valdis.kletni...@vt.edu wrote:
>>
>> On Fri, 20 Feb 2015 01:53:44 +0100, "Luis R. Rodriguez" said:
>>>
>>> Wider community:
>>>
>>> anyone aware of any
On Sat, Feb 21, 2015 at 10:57:10PM -0500, Ilan Peer wrote:
> Previously, the indoor setting configuration assumed that as
> long as a station interface is connected, the indoor environment
> setting does not change. However, this assumption is problematic
> as:
>
> - It is possible that a station
On Wed, Feb 25, 2015 at 02:30:40PM +, Peer, Ilan wrote:
> Hi Luis,
>
> > -Original Message-
> > From: Luis R. Rodriguez [mailto:mcg...@suse.com]
> > Sent: Tuesday, February 24, 2015 02:03
> > To: Peer, Ilan; Jouni Malinen
> > Cc: linux-wir
On Wed, Feb 25, 2015 at 04:47:02AM -0500, Ilan Peer wrote:
> Directly update the indoor setting without wrapping it as
> a regulatory request, to simplify the processing.
>
> Signed-off-by: Ilan Peer
Acked-by: Luis R. Rodriguez
Luis
--
To unsubscribe from this list: s
On Wed, Feb 25, 2015 at 04:47:03AM -0500, Ilan Peer wrote:
> case NL80211_USER_REG_HINT_INDOOR:
> - return regulatory_hint_indoor_user();
> + is_indoor = !!info->attrs[NL80211_ATTR_REG_INDOOR];
> + if (info->attrs[NL80211_ATTR_SOCKET_OWNER])
> +
On Wed, Feb 25, 2015 at 04:47:04AM -0500, Ilan Peer wrote:
> Timeout was scheduled only in case CRDA was called due to user hints,
> but was not scheduled for other cases. This can result in regulatory
> hint processing getting stuck in case that there is no CRDA configured.
>
> Change this by sch
On Thu, Feb 26, 2015 at 04:54:06AM -0500, Ilan Peer wrote:
> Previously, the indoor setting configuration assumed that as
> long as a station interface is connected, the indoor environment
> setting does not change. However, this assumption is problematic
> as:
>
> - It is possible that a station
On Sun, Mar 01, 2015 at 01:02:28AM -0500, Ilan Peer wrote:
> diff --git a/net/wireless/reg.c b/net/wireless/reg.c
> index c24c8bf..f88d512 100644
> --- a/net/wireless/reg.c
> +++ b/net/wireless/reg.c
> @@ -128,9 +128,12 @@ static int reg_num_devs_support_basehint;
> * State variable indicating if
On Wed, Mar 04, 2015 at 10:37:35AM +, Peer, Ilan wrote:
>
> > -Original Message-
> > From: Luis R. Rodriguez [mailto:mcg...@suse.com]
> > Sent: Monday, March 02, 2015 23:23
> > To: Peer, Ilan
> > Cc: linux-wireless@vger.kernel.org; ArikX Nemts
On Wed, Mar 04, 2015 at 12:32:06AM -0500, Ilan Peer wrote:
> -int regulatory_hint_indoor_user(void)
> +int regulatory_hint_indoor(bool is_indoor, u32 portid)
> {
> + spin_lock(®_indoor_lock);
> +
> + /* It is possible that more than one user space process is trying to
> + * configure
Change this by scheduling a timeout every time CRDA is called. In
> addition, in restore_regulatory_settings() all pending requests are
> restored (and not only the user ones).
>
> Signed-off-by: Ilan Peer
Acked-by: Luis R. Rodriguez
For all of these.
Luis
--
To unsubscribe fr
On Thu, Apr 9, 2015 at 5:57 PM, Luis R. Rodriguez
wrote:
> Hey folks,
>
> next week I'd like to address replacing the need for CRDA [0] as a
> udev helper with in-kernel functionality There's a few motivations
> for this but a good one is that the kernel already has no
On Mon, Dec 12, 2016 at 10:53:38AM +0100, Rafał Miłecki wrote:
> On 12 December 2016 at 10:26, Arend Van Spriel
> wrote:
> > On 12-12-2016 9:32, Rafał Miłecki wrote:
> >> On 12 December 2016 at 09:12, Johannes Berg
> >> wrote:
> >>> On Sat, 2016-12-10 at 16:54 +0100, Rafał Miłecki wrote:
>
On Sat, Dec 10, 2016 at 04:54:41PM +0100, Rafał Miłecki wrote:
> So it would be nice to have version of request_firmware_nowait with
> FW_OPT_NO_WARN. If requesting firmware NVRAM fails *and* getting
> platform NVRAM fails, then I could to print error on my own.
> Does it make sense? Can you see a
On Thu, Dec 15, 2016 at 2:12 PM, Arend Van Spriel
wrote:
> On 15-12-2016 16:33, Pali Rohár wrote:
>> On Thu Dec 15 09:18:44 2016 Kalle Valo wrote:
>>> (Adding Luis because he has been working on request_firmware() lately)
>>>
>>> Pali Rohár writes:
>>>
>> So no, there is no argument against.
On Mon, Feb 29, 2016 at 1:32 PM, Till Kamppeter
wrote:
> Hi,
>
> we are accepted as mentoring organization again!
>
> So please advertise our participation to find students and add more
> project ideas to the ideas page:
>
> https://www.linuxfoundation.org/collaborate/workgroups/gsoc/google-summer
I just hit "want to mentor" for the backports one by Cristina-Gabriela Moraru.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Thu, Sep 04, 2014 at 12:23:40PM +0200, Johannes Berg wrote:
> On Thu, 2014-09-04 at 13:17 +0300, Jouni Malinen wrote:
> > On Thu, Sep 04, 2014 at 10:03:51AM +0200, Johannes Berg wrote:
> > > On Wed, 2014-09-03 at 16:15 +0300, Jouni Malinen wrote:
> > > > Source:
> > > > http://www.ntrc.org.lc/op
On Tue, Sep 02, 2014 at 02:00:00PM +0200, Helmut Schaa wrote:
> Hi Luis,
>
> On Tue, Apr 22, 2014 at 5:39 AM, Luis R. Rodriguez
> wrote:
> > From: "Luis R. Rodriguez"
> >
> > This allows processing of the last regulatory request when
> > we
bit late on mine as well.
> On Tue, Jun 10 2014, Luis R. Rodriguez wrote:
> > On Mon, Jun 9, 2014 at 7:21 AM, Rostislav Lisovy wrote:
> >> Dear Luis;
> >> Thank you for the introduction in the wireless-regdb mailing-list.
> >>
> >> On Wed, 2014-06-04
On Mon, Sep 08, 2014 at 11:59:39AM +0200, Helmut Schaa wrote:
> Hi,
>
> On Fri, Sep 5, 2014 at 11:43 PM, Luis R. Rodriguez wrote:
> > Yeah this seems to be a corner case of the fact that we deal with
> > locking for the last request only through RCU and we only annotate
>
On Fri, Sep 12, 2014 at 6:00 PM, Geyslan Gregório Bem wrote:
> Hi John and Sujith,
>
> Peter and Luis are CC.
>
> I'm having issues with my ath9k as you can see below. My card is constantly
> connecting and disconnecting from my SSID before it could get some IP
> (DHCP).
>
> I saw that you have pa
a regulatory-rule.
>
> Also allow propagating the GO_CONCURRENT modifier from a reg-rule to a
> channel.
>
> Signed-off-by: Arik Nemtsov
Reviewed-by: Luis R. Rodriguez
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a mess
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov wrote:
> +static bool reg_wdev_chan_valid(struct wiphy *wiphy, struct wireless_dev
> *wdev)
> +{
> + struct ieee80211_channel *ch;
> + struct cfg80211_chan_def chandef;
> + struct cfg80211_registered_device *rdev = wiphy_to_rdev(wip
Nemtsov
Reviewed-by: Luis R. Rodriguez
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov wrote:
> cfg80211: allow wiphy specific regdomain management
This guy never made it to my inbox.
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordom
On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov wrote:
> + * @NL80211_ATTR_WIPHY_SELF_MANAGED_REG: flag attribute indicating the
> + * regulatory information came from the driver and not from the global
> + * cfg80211 regulatory domain information.
Awesome, can you also add another entry f
On Wed, Nov 5, 2014 at 1:12 AM, Arik Nemtsov wrote:
> On Wed, Nov 5, 2014 at 5:23 AM, Luis R. Rodriguez
> wrote:
>> On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov wrote:
>>> + * @NL80211_ATTR_WIPHY_SELF_MANAGED_REG: flag attribute indicating the
>>> + * regula
On Wed, Nov 5, 2014 at 1:18 AM, Arik Nemtsov wrote:
> On Wed, Nov 5, 2014 at 5:16 AM, Luis R. Rodriguez
> wrote:
>> On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov wrote:
>>> +static bool reg_wdev_chan_valid(struct wiphy *wiphy, struct wireless_dev
>>> *w
On Wed, Nov 5, 2014 at 12:41 AM, Arik Nemtsov wrote:
> On Wed, Nov 5, 2014 at 5:21 AM, Luis R. Rodriguez
> wrote:
>> On Wed, Oct 22, 2014 at 11:37 PM, Arik Nemtsov wrote:
>>> cfg80211: allow wiphy specific regdomain management
>>
>> This guy never made it to
On Thu, Nov 13, 2014 at 05:55:13PM +0200, Arik Nemtsov wrote:
> >
> >> 2. And then if userspace sends a wiphy idx to the NL80211_CMD_GET_REG,
> >> we'll return wiphy->regd for that case as well?
> >
> > That's right, for now we'd be able to send the regd when either
> > NL80211_ATTR_WIPHY_SELF_MANA
Johannes, Jouni, please review the comment about WLAN_REASON_DEAUTH_LEAVING
below.
On Thu, Nov 13, 2014 at 06:13:36PM +0200, Arik Nemtsov wrote:
> When the regulatory settings change, some channels might become invalid.
> Disconnect interfaces acting on these channels, after giving userspace
> cod
t required (things which
are good to be explicit about) Vs possible fixes, these last are
good fixes. Also put them as part of your first set of patches
and add my Acked-by so Johannes can already merge them. If you want
them merged faster just send them separately now.
Acked-by: Luis R. Rodriguez
On Thu, Nov 13, 2014 at 06:13:38PM +0200, Arik Nemtsov wrote:
> From: Jonathan Doron
>
> Add a new regulatory flag that allows a driver to manage regdomain
> changes/updates for its own wiphy.
> In this case the regdomain is local to the driver, and it does not use
> the shared cfg80211 regdomain
On Thu, Nov 13, 2014 at 06:13:39PM +0200, Arik Nemtsov wrote:
> From: Jonathan Doron
>
> Allow usermode to query wiphy-specific regd info, for drivers that use
> wiphy-specific regulatory management.
>
> Use the existing API for sending regdomain info to usermode, but return
> the wiphy-specific
Full kernel integration is now merged as part of Linux
backports-20141114. I've written a bit about it [0] [1], what we need
now are users and developer to give this a good spin as we wind down
for the v3.19 release, which will be the first release that will
support kernel integration down to any k
On Sun, Nov 16, 2014 at 01:06:00PM +0200, Arik Nemtsov wrote:
> On Fri, Nov 14, 2014 at 1:11 AM, Luis R. Rodriguez wrote:
> >> index a4d2792..656a1b1 100644
> >> --- a/net/wireless/core.c
> >> +++ b/net/wireless/core.c
> >> @@ -541,6 +541,13 @@
On Sun, Nov 16, 2014 at 01:00:16PM +0200, Arik Nemtsov wrote:
> On Fri, Nov 14, 2014 at 12:45 AM, Luis R. Rodriguez wrote:
> >> + * @REGULATORY_ENFORCE_CHANNELS: the regulatory core will make sure all
> >> + * interfaces on this wiphy reside on allowed chann
On Thu, Nov 20, 2014 at 04:17:00PM +0100, Johannes Berg wrote:
> On Thu, 2014-11-13 at 18:13 +0200, Arik Nemtsov wrote:
> > When the regulatory settings change, some channels might become invalid.
> > Disconnect interfaces acting on these channels, after giving userspace
> > code a grace period to
On Thu, Nov 20, 2014 at 06:47:24PM +0200, Arik Nemtsov wrote:
> On Thu, Nov 20, 2014 at 5:22 PM, Johannes Berg
> wrote:
> > On Sun, 2014-11-16 at 13:06 +0200, Arik Nemtsov wrote:
> >
> >> We intend to add a patch to wpa_s to always add the wiphy_idx to
> >> NL80211_CMD_GET_REG. With the current ap
On Thu, Nov 20, 2014 at 09:38:53PM +0100, Johannes Berg wrote:
> On Thu, 2014-11-20 at 21:35 +0100, Luis R. Rodriguez wrote:
>
> > It really should only kick you off of channels you are not allowed to use,
> > I welcome this change and think it is important as a standard f
On Fri, Nov 21, 2014 at 11:33:43AM +0200, Arik Nemtsov wrote:
> On Thu, Nov 20, 2014 at 10:54 PM, Luis R. Rodriguez wrote:
> >>
> >> Then it gets the global one, and it knows it via a wiphy attribute:
> >>
> >> (wiphy->regula
On Sun, Nov 23, 2014 at 05:02:19PM +0200, Arik Nemtsov wrote:
> When the regulatory settings change, some channels might become invalid.
> Disconnect interfaces acting on these channels, after giving userspace
> code a grace period to leave them.
>
> This mode is currently opt-in, and not all inte
gned-off-by: Jonathan Doron
> Signed-off-by: Arik Nemtsov
Reviewed-by: Luis R. Rodriguez
Luis
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
On Sun, Nov 23, 2014 at 05:02:21PM +0200, Arik Nemtsov wrote:
> From: Jonathan Doron
>
> Allow usermode to query wiphy-specific regd info, for drivers that use
> wiphy-specific regulatory management.
>
> Use the existing API for sending regdomain info to usermode, but return
> the wiphy-specific
On Wed, Nov 26, 2014 at 05:06:37PM +0200, Arik Nemtsov wrote:
> On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez wrote:
> > On Sun, Nov 23, 2014 at 05:02:19PM +0200, Arik Nemtsov wrote:
> >> When the regulatory settings change, some channels might become invalid.
> >
On Wed, Nov 26, 2014 at 10:39 AM, Arik Nemtsov wrote:
> On Wed, Nov 26, 2014 at 5:28 PM, Luis R. Rodriguez wrote:
>> On Wed, Nov 26, 2014 at 05:06:37PM +0200, Arik Nemtsov wrote:
>>> On Tue, Nov 25, 2014 at 9:38 PM, Luis R. Rodriguez wrote:
>>> > On Sun, Nov 23,
On Wed, Nov 26, 2014 at 11:16 AM, Arik Nemtsov wrote:
> On Wed, Nov 26, 2014 at 5:58 PM, Luis R. Rodriguez wrote:
>> On Wed, Nov 26, 2014 at 10:39 AM, Arik Nemtsov wrote:
>>> On Wed, Nov 26, 2014 at 5:28 PM, Luis R. Rodriguez wrote:
>>>> On Wed, Nov 26, 2014 at
On Wed, Nov 26, 2014 at 11:43 AM, Arik Nemtsov wrote:
> On Tue, Nov 25, 2014 at 10:28 PM, Luis R. Rodriguez wrote:
>> On Sun, Nov 23, 2014 at 05:02:21PM +0200, Arik Nemtsov wrote:
>>> From: Jonathan Doron
>>>
>>> Allow usermode to query wiphy-specific regd
On Wed, Nov 26, 2014 at 11:49 AM, Arik Nemtsov wrote:
> On Wed, Nov 26, 2014 at 6:47 PM, Luis R. Rodriguez wrote:
>> On Wed, Nov 26, 2014 at 11:43 AM, Arik Nemtsov wrote:
>>> On Tue, Nov 25, 2014 at 10:28 PM, Luis R. Rodriguez wrote:
>>>> On Sun, Nov 23, 2014 at
1 - 100 of 320 matches
Mail list logo
