LKML Archive on
help / color / mirror / Atom feed
From: Jeremy Elson <>
To: Pavel Machek <>
Cc: Jeremy Elson <>,
Subject: Re: [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices
Date: Tue, 9 Oct 2001 20:55:48 -0700 (PDT)	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

On Fri, 5 Oct 2001, Pavel Machek wrote:
> Yep. And linmodem driver does signal processing, so it is big and
> ugly. And up till now, it had to be in kernel. With your patches, such
> drivers could be userspace (where they belong!). Of course, it would be 
> very good if your interface did not change...

FUSD's user-kernel interface won't change spuriously, but it sometimes
will need to change as features are added.  Some such changes are
already in the works.

The fact that FUSD provides a semi-stable binary interface for servicing
device-file callbacks isn't really FUSD's design goal as much as it is an
accidental side effect.  Making a stable binary interface for kernel
device drivers is the objective of, say, UDI (I think).  The purpose of
FUSD is just to be able to proxy the callbacks to userspace.


      parent reply	other threads:[~2001-10-10  3:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-29  1:18 Jeremy Elson
2001-10-01 15:36 ` Jeremy Elson
2001-10-02 18:48   ` Pavel Machek
2001-10-02 22:37     ` Jeremy Elson
2001-10-02 22:44       ` Mike Fedyk
2001-10-05 18:51       ` Pavel Machek
2001-10-08  2:09         ` Eric W. Biederman
2001-10-08  2:37           ` linmodems (was Re: [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices) Jeff Garzik
2001-10-08 12:19             ` Pavel Machek
2001-10-08 19:34             ` Tim Jansen
2001-10-08 12:20           ` [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices Pavel Machek
2001-10-13 21:57             ` Eric W. Biederman
2001-10-14  6:12               ` Pavel Machek
2001-10-15 12:34                 ` Jamie Lokier
2001-10-15 12:38                 ` Jamie Lokier
2001-10-10  3:55         ` Jeremy Elson [this message]

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \
    --subject='Re: [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).