From: Greg KH <greg@kroah.com>
To: Philipp Hortmann <philipp.g.hortmann@gmail.com>
Cc: kernelnewbies@kernelnewbies.org
Subject: Re: Where to find the information how to write a state of the art USB driver?
Date: Thu, 13 Jan 2022 20:07:00 +0100 [thread overview]
Message-ID: <YeB4VHzMHVjNrwEG@kroah.com> (raw)
In-Reply-To: <YeB28CQZ/6A0fziJ@kroah.com>
On Thu, Jan 13, 2022 at 08:01:04PM +0100, Greg KH wrote:
> On Thu, Jan 13, 2022 at 07:54:19PM +0100, Philipp Hortmann wrote:
> > On 1/13/22 4:33 PM, Greg KH wrote:
> > > On Thu, Jan 13, 2022 at 07:39:38AM +0100, Philipp Hortmann wrote:
> > > > On 1/12/22 10:54 AM, Greg KH wrote:
> > > > > That driver tried to be an example for an unknown device, doing multiple
> > > > > different things that no single driver/device would probably ever need.
> > > > > Also it can almost always just be replaced with a simple userspace
> > > > > program using libusb, as I bet your driver could be replaced with as
> > > > > well, right?
> > > > Yes it can be replaced by a userspace program but even this is not required.
> > > It is an issue if you are trying to write a new driver. We do not take
> > > new drivers into the kernel tree if they can be in the kernel instead.
> > >
> >
> > Sorry I did not clearly express what I plan to do. I plan to do maintenance
> > and bug fixes on the kernel.
>
> That's wonderful, try starting out in drivers/staging/*/TODO for lots of
> things that need work.
And, there are USB drivers in there as well, if that is what you are
interested in working on.
_______________________________________________
Kernelnewbies mailing list
Kernelnewbies@kernelnewbies.org
https://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
next prev parent reply other threads:[~2022-01-13 19:08 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-10 21:31 Where to find the information how to write a state of the art USB driver? Philipp Hortmann
2022-01-11 8:51 ` Greg KH
2022-01-11 20:09 ` Philipp Hortmann
2022-01-12 9:54 ` Greg KH
2022-01-13 6:39 ` Philipp Hortmann
2022-01-13 15:33 ` Greg KH
2022-01-13 15:37 ` Greg KH
2022-01-13 18:54 ` Philipp Hortmann
2022-01-13 19:01 ` Greg KH
2022-01-13 19:07 ` Greg KH [this message]
2022-01-16 13:45 ` Pavel Skripkin
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=YeB4VHzMHVjNrwEG@kroah.com \
--to=greg@kroah.com \
--cc=kernelnewbies@kernelnewbies.org \
--cc=philipp.g.hortmann@gmail.com \
/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).