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:
> > On Tue, Nov 08, 2022 at 11:10:21AM +0300, Dan Carpenter wrote:
> >
> > I cannot say anything about the media subsystem, but for networking
> > patches, i will be much more willing to help somebody going from
> > Outreach to being a full kernel developers if they decide to take on
> > something more than just some Coccinelle changes. If it looks like you
> > have the hardware and want to make it better, have a vision where the
> > driver should go, then you are likely to get more help from me. So if
> > media drivers are what you interested in, go buy some hardware which
> > uses one of the drivers in staging, look at the TODO file, and submit
> > bigger patches than just -1 to -ENOMEM.
>
> Hello Andrew,
> Thank you so much for your kind advice and willingness to help a newbie
> become a valued kernel developer. I am committed to acquire necessary
> knowledge and skills to contribute more than current cleanup and minor
> correction patches. I am sure that the upcoming Coccinelle based project
> work [if I am shortlisted] will be much more complex and meaningful.
>
> I will explore the staging directory to identify a hardware I can afford.
> I would welcome suggestion on a driver that is not much expensive and
> complex to start with. Anything for the networking subsystem???
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@xxxxxxxxxxxxxxx.
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?
Andrew
