public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: Sergej Bauer <sergej.bauer@gmail.com>
Cc: Richard Weinberger <richard.weinberger@gmail.com>,
	Paul Bolle <pebolle@tiscali.nl>,
	linux-kernel@vger.kernel.org, gregkh@linuxfoundation.org
Subject: Re: [PATCH 1/1] Add mkopci driver
Date: Sat, 21 Mar 2015 16:41:42 +0100	[thread overview]
Message-ID: <201503211641.42508.arnd@arndb.de> (raw)
In-Reply-To: <201503211741.11580.sergej.bauer@gmail.com>

On Saturday 21 March 2015, Sergej Bauer wrote:
> Richard, thanks for your review.
> 
> But I still have several notes about driver:
> 
> > - You add new proc files, which is not really welcomed. Please consider sysfs.
> That will break a bunch of userspace applications, which use proc-files for several years (as long as from 2006
> year)
> 

> > BTW: Forgot to mention that this sounds like a job for UIO or VFIO.
> And again, you are right. But, again, there a number of applications wich use /proc/mkopci/core
> 
> But, of course, there may be decided that the kernel main line - this is not the place for such a driver. :)
> If the driver is suitable anyway, patch is at the end of this message

I don't think we should merge the driver with the proposed user interface. You can either
create a high-level abstraction for MIL-STD-1553, or use UIO or VFIO to provide a trivial
passthrough. In either case, both the ioctl interface and the procfs interface have no
future, and existing user space programs need to adapt.

There is nothing wrong with adding a driver for this hardware, but I'd rather see it done
properly than having an ad-hoc user space interface that was never reviewed publically
before it got used by applications.

	Arnd

  reply	other threads:[~2015-03-21 15:41 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-20 12:10 [PATCH 1/1] Add mkopci driver sergej.bauer
2015-03-20 12:43 ` Richard Weinberger
2015-03-20 12:44   ` Richard Weinberger
2015-03-21 12:11   ` Paul Bolle
2015-03-21 14:41   ` Sergej Bauer
2015-03-21 15:41     ` Arnd Bergmann [this message]
2015-03-21 17:24       ` Sergej Bauer
2015-03-21 17:32         ` Richard Weinberger
2015-03-21 18:29           ` Sergej Bauer
2015-03-26 22:47 ` Greg KH

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=201503211641.42508.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=gregkh@linuxfoundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pebolle@tiscali.nl \
    --cc=richard.weinberger@gmail.com \
    --cc=sergej.bauer@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