From: Deepak R Varma <drv@mailo.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Dan Carpenter <error27@gmail.com>,
Neil Armstrong <neil.armstrong@linaro.org>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kevin Hilman <khilman@baylibre.com>,
Jerome Brunet <jbrunet@baylibre.com>,
Martin Blumenstingl <martin.blumenstingl@googlemail.com>,
linux-media@vger.kernel.org, linux-amlogic@lists.infradead.org,
linux-staging@lists.linux.dev,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: patches for staging:media drivers
Date: Fri, 11 Nov 2022 22:41:03 +0530 [thread overview]
Message-ID: <Y26CJ9L52AmPBQYC@qemulion> (raw)
In-Reply-To: <Y2uv56k515cKTXU4@lunn.ch>
On Wed, Nov 09, 2022 at 02:49:27PM +0100, Andrew Lunn wrote:
> On Wed, Nov 09, 2022 at 12:10:37PM +0530, Deepak R Varma wrote:
> > On Tue, Nov 08, 2022 at 09:27:32PM +0100, Andrew Lunn wrote:
>
> Staging drivers for network tend to be USB dongles for WiFi. Some of
> those drivers need throwing away and starting again, others need less
> work. If you are interested in that, i would suggest asking on
> linux-wireless@vger.kernel.org.
>
> Another option might be pi433? The problem with that is, i don't know
> how it fits into the rest of the network stack? Could it maybe fit
> under ieee802154? Or is it just unique and needs to do its own thing?
Hello Andrew,
I looked at the pi433 driver and it appears to be a good starting point. I have
started studying more about the hardware, the RF technology etc. There is a TODO
file with reasonable challenges.
Thank you for the recommendation.
Have a nice weekend!
./drv
>
> Andrew
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2022-11-11 17:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-06 10:52 patches for staging:media drivers Deepak R Varma
2022-11-07 17:29 ` Neil Armstrong
2022-11-07 18:57 ` Deepak R Varma
2022-11-08 8:10 ` Dan Carpenter
2022-11-08 9:35 ` Hans Verkuil
2022-11-08 9:46 ` Dan Carpenter
2022-11-08 20:27 ` Andrew Lunn
2022-11-09 6:40 ` Deepak R Varma
2022-11-09 13:49 ` Andrew Lunn
2022-11-11 17:11 ` Deepak R Varma [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=Y26CJ9L52AmPBQYC@qemulion \
--to=drv@mailo.com \
--cc=andrew@lunn.ch \
--cc=error27@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=jbrunet@baylibre.com \
--cc=khilman@baylibre.com \
--cc=linux-amlogic@lists.infradead.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-staging@lists.linux.dev \
--cc=martin.blumenstingl@googlemail.com \
--cc=mchehab@kernel.org \
--cc=neil.armstrong@linaro.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).