From: Michael Nazzareno Trimarchi <michael@amarulasolutions.com>
To: Daniel Wagner <wagi@monom.org>
Cc: connman@lists.linux.dev
Subject: Re: [RFC PATCH] tether: Add a way to define a tethering frequency
Date: Wed, 6 Oct 2021 23:55:17 +0200 [thread overview]
Message-ID: <CAOf5uwkPSxGygWi1EM+7BbqVJ_t_fK00exdcAyHO5nAFCOYJwA@mail.gmail.com> (raw)
In-Reply-To: <20211006124043.l7nlcqciqk5wc6ef@carbon.fritz.box>
Hi Daniel
On Wed, Oct 6, 2021 at 2:40 PM Daniel Wagner <wagi@monom.org> wrote:
>
> Hi Michael,
>
> On Mon, Oct 04, 2021 at 11:00:16PM +0200, Michael Trimarchi wrote:
> > Add an optional parameter to set the frequency of access point. Need to
> > be splitted in multiple patches. This is used as initial idea.
>
> Nice, this is what I had in mind.
>
> > TODO:
> > - split
>
> Yes please.
The best thing here is to add libnl in connman. This allows us to read
some wifi properties, like
the available frequencies. This can be added in device.c or where you
think is the best.
We can create even a temp function that just check if the frequency is
valid in the range of 5Ghz
or 2.4Ghz
Michael
>
> > - add freq constraints
> > - move to unsigned int
>
> Daniel
--
Michael Nazzareno Trimarchi
Co-Founder & Chief Executive Officer
M. +39 347 913 2170
michael@amarulasolutions.com
__________________________________
Amarula Solutions BV
Joop Geesinkweg 125, 1114 AB, Amsterdam, NL
T. +31 (0)85 111 9172
info@amarulasolutions.com
www.amarulasolutions.com
next prev parent reply other threads:[~2021-10-06 21:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-04 21:00 [RFC PATCH] tether: Add a way to define a tethering frequency Michael Trimarchi
2021-10-06 12:40 ` Daniel Wagner
2021-10-06 21:55 ` Michael Nazzareno Trimarchi [this message]
2021-10-07 15:04 ` Daniel Wagner
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAOf5uwkPSxGygWi1EM+7BbqVJ_t_fK00exdcAyHO5nAFCOYJwA@mail.gmail.com \
--to=michael@amarulasolutions.com \
--cc=connman@lists.linux.dev \
--cc=wagi@monom.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).