All of lore.kernel.org
 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 10:11:17 +0200	[thread overview]
Message-ID: <20180523081117.GA7247@kroah.com> (raw)
In-Reply-To: <17499481527058909@web27g.yandex.ru>

On Wed, May 23, 2018 at 10:01:49AM +0300, Ozgur Kara wrote:
> 
> 
> 23.05.2018, 09:48, "Greg KH" <greg@kroah.com>:
> > On Wed, May 23, 2018 at 09:26:31AM +0300, Ozgur Kara wrote:
> >> ?I think seen the drivers/staging section in the kernel source.
> >
> > Yes, starting out with drivers/staging/*/TODO is always a good idea.
> >
> >> ?for example, some new generation embedded modules and electronic devices don't work on Linux.
> >
> > Really? Like what?
> 
> For example kernel's no have drivers for some sensors, I also couldn't identify the PCI card for automation and no driver in the kernel.
> 
> CP-168U RS232 PCI Card

Odss are, this "just works" if it is a normal serial port card.  If not,
it should be trivial to get working.

> Wireless Nozzle Reader MTI125
> NXP MPU6050
> MPU6050
> 
> I hope I'm not wrong :)

We have loads of iio drivers in the kernel, try digging based on the PCI
id values.  For example, look at drivers/iio/imu/inv_mpu6050/ :)

But yes, sensors are a great way to get involved in driver writing, they
are usually pretty simple and all they need are to be hooked up to the
iio interface.  A data sheet is usually needed to determine the units
and values the sensors provide, but those should not be hard to come by.

good luck!

greg k-h

  reply	other threads:[~2018-05-23  8:11 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
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 [this message]
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=20180523081117.GA7247@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.