From: "Hans J. Koch" <hjk@hansjkoch.de>
To: Eli Billauer <eli.billauer@gmail.com>
Cc: linux-kernel@vger.kernel.org, arnd@arndb.de,
gregkh@linuxfoundation.org, hjk@hansjkoch.de
Subject: Re: [PATCH v4 1/2] New driver: Xillybus generic interface for FPGA (programmable logic)
Date: Mon, 20 May 2013 23:16:31 +0200 [thread overview]
Message-ID: <20130520211631.GA18956@local> (raw)
In-Reply-To: <1368802420-26723-1-git-send-email-eli.billauer@gmail.com>
On Fri, May 17, 2013 at 05:53:39PM +0300, Eli Billauer wrote:
> This is the documentation for the Xillybus driver. It's intended for kernel
> maintainers, since actual users will most likely rely on other documentation.
>
> It has turned out somewhat tricky to put Xillybus in one of the existing
> categories of device drivers. I placed it under drivers/uio, mainly because it
> shares the spirit of a generic driver allowing userspace programs to talk
> directly with hardware. Unlike the classic UIO devices, Xillybus' char files
> shouldn't be memory mapped, but rather used in the regular manner as streams
> of data.
In that case it simply isn't a UIO device.
>
> This driver was previously posted under drivers/misc/. The misc device
> framework turned out to be inadequate, as the driver may create more than 100
> device files in some cases.
And that is a problem? If yes, try something else like sysfs. From your
description, this is a drivers/misc device for me.
Thanks,
Hans
next prev parent reply other threads:[~2013-05-20 21:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-17 14:53 [PATCH v4 1/2] New driver: Xillybus generic interface for FPGA (programmable logic) Eli Billauer
2013-05-17 14:53 ` [PATCH v4 2/2] " Eli Billauer
2013-05-20 18:39 ` [PATCH v4 1/2] " Greg KH
2013-05-20 21:16 ` Hans J. Koch [this message]
2013-05-21 10:46 ` Eli Billauer
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=20130520211631.GA18956@local \
--to=hjk@hansjkoch.de \
--cc=arnd@arndb.de \
--cc=eli.billauer@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.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