kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: greg@kroah.com (Greg KH)
To: kernelnewbies@lists.kernelnewbies.org
Subject: searching for a missing driver
Date: Wed, 23 May 2018 08:05:21 +0200	[thread overview]
Message-ID: <20180523060521.GA15885@kroah.com> (raw)
In-Reply-To: <20180523022551.GA2481@hle-laptop.local>

On Tue, May 22, 2018 at 10:25:51PM -0400, Hugo Lefeuvre wrote:
> Hi,
> 
> I've been reading documentation about linux drivers development for
> quite a while now, but never did anything really useful of it. Lack of
> time, but most importantly lack of projects to apply this knowledge.
> Now I've got some spare time ahead of me, and it seems to be the
> right moment to start a kernel driver project.
> 
> ... but I don't know exactly what kind of device driver I want to
> write, and what kind of device I want to work on.

It's best to find a device you care about, that does not work on Linux,
to do something like this, as you are going to be working on it for a
while.

But the problem is, as you are finding out, that almost everything
already "just works" in Linux.  Turns out Linux supports more hardware
than any other operating system, sorry :)

Try digging around in shops that sell "odd hardware", that might be the
best way to find something like this.

good luck!

greg k-h

  reply	other threads:[~2018-05-23  6:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-23  2:25 searching for a missing driver Hugo Lefeuvre
2018-05-23  6:05 ` Greg KH [this message]
2018-05-23  6:26   ` Ozgur Kara
2018-05-23  6:48     ` Greg KH
2018-05-23  7:01       ` Ozgur Kara
2018-05-23  8:11         ` Greg KH
2018-05-24  2:26           ` Hugo Lefeuvre

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=20180523060521.GA15885@kroah.com \
    --to=greg@kroah.com \
    --cc=kernelnewbies@lists.kernelnewbies.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).