From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
To: Daniele Palmas <dnlplm@gmail.com>
Cc: David Miller <davem@davemloft.net>,
kuba@kernel.org, bjorn.andersson@linaro.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
kvalo@codeaurora.org
Subject: Re: [PATCH v2 0/2] Migrate QRTR Nameservice to Kernel
Date: Fri, 6 Mar 2020 22:47:42 +0530 [thread overview]
Message-ID: <20200306171742.GA14558@Mani-XPS-13-9360> (raw)
In-Reply-To: <CAGRyCJGMxMO-8b3QniJP0XVgTT4zxSd=pm_O=4T5N3f3H3aM2w@mail.gmail.com>
Hi,
On Fri, Mar 06, 2020 at 05:18:01PM +0100, Daniele Palmas wrote:
> Hello Mani,
>
> Il giorno gio 20 feb 2020 alle ore 16:15 Manivannan Sadhasivam
> <manivannan.sadhasivam@linaro.org> ha scritto:
> >
> > Hello,
> >
> > This patchset migrates the Qualcomm IPC Router (QRTR) Nameservice from userspace
> > to kernel under net/qrtr.
> >
>
> I saw those and the MHI driver related patches, thanks for doing them.
>
> Are you going to submit also the controller and device (uci, netdev)
> drivers for SDX55 modem?
>
This is certainly on the TODO list but there is no fixed timeline. Current
patchset focuses QCA6390 only, which does not need these drivers. So maybe
sometime later, we can expect these drivers to get upstreamed.
Thanks,
Mani
> Thanks,
> Daniele
>
> > The userspace implementation of it can be found here:
> > https://github.com/andersson/qrtr/blob/master/src/ns.c
> >
> > This change is required for enabling the WiFi functionality of some Qualcomm
> > WLAN devices using ATH11K without any dependency on a userspace daemon. Since
> > the QRTR NS is not usually packed in most of the distros, users need to clone,
> > build and install it to get the WiFi working. It will become a hassle when the
> > user doesn't have any other source of network connectivity.
> >
> > The original userspace code is published under BSD3 license. For migrating it
> > to Linux kernel, I have adapted Dual BSD/GPL license.
> >
> > This patchset has been verified on Dragonboard410c and Intel NUC with QCA6390
> > WLAN device.
> >
> > Thanks,
> > Mani
> >
> > Changes in v2:
> >
> > * Sorted the local variables in reverse XMAS tree order
> >
> > Manivannan Sadhasivam (2):
> > net: qrtr: Migrate nameservice to kernel from userspace
> > net: qrtr: Fix the local node ID as 1
> >
> > net/qrtr/Makefile | 2 +-
> > net/qrtr/ns.c | 751 ++++++++++++++++++++++++++++++++++++++++++++++
> > net/qrtr/qrtr.c | 51 +---
> > net/qrtr/qrtr.h | 4 +
> > 4 files changed, 767 insertions(+), 41 deletions(-)
> > create mode 100644 net/qrtr/ns.c
> >
> > --
> > 2.17.1
> >
prev parent reply other threads:[~2020-03-06 17:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-20 15:13 [PATCH v2 0/2] Migrate QRTR Nameservice to Kernel Manivannan Sadhasivam
2020-02-20 15:13 ` [PATCH v2 1/2] net: qrtr: Migrate nameservice to kernel from userspace Manivannan Sadhasivam
2020-02-20 15:13 ` [PATCH v2 2/2] net: qrtr: Fix the local node ID as 1 Manivannan Sadhasivam
2020-02-21 20:05 ` [PATCH v2 0/2] Migrate QRTR Nameservice to Kernel David Miller
2020-03-06 16:18 ` Daniele Palmas
2020-03-06 17:17 ` Manivannan Sadhasivam [this message]
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=20200306171742.GA14558@Mani-XPS-13-9360 \
--to=manivannan.sadhasivam@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=davem@davemloft.net \
--cc=dnlplm@gmail.com \
--cc=kuba@kernel.org \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.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