LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Jeff Garzik <jgarzik@mandrakesoft.com>
To: "Eric W. Biederman" <ebiederman@uswest.net>
Cc: Pavel Machek <pavel@Elf.ucw.cz>,
	Jeremy Elson <jelson@circlemud.org>,
	linux-kernel@vger.kernel.org
Subject: linmodems (was Re: [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices)
Date: Sun, 7 Oct 2001 21:37:22 -0500 (CDT)	[thread overview]
Message-ID: <Pine.LNX.3.96.1011007213223.2882B-100000@mandrakesoft.mandrakesoft.com> (raw)
In-Reply-To: <m1n132x4qg.fsf@frodo.biederman.org>

On 7 Oct 2001, Eric W. Biederman wrote:
> Pavel Machek <pavel@Elf.ucw.cz> writes:
> > 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...

> I don't see how linmodem drivers apply.  At least not at the low-level
> because you actually have to driver the hardware, respond to interrupts
> etc.  On some of this I can see a driver split like there is for the video
> card drivers, so the long running portitions don't have to be in the kernel.

My best guess for a Linux winmodem solution for Linux is three pieces:
The existing Lucent (and other) hardware work (by Pavel/Richard/Jamie/others?)
Rogier Wolff's user space serial driver code, and
A work called "modem" by a now-deceased scientist at SGI(IIRC).  Alan
pointed me to the last piece.  'modem' handles up to 14.4k speed, and
supports some error correcting protocols we all remember from the BBS
days.

Just need someone to glue those pieces together... and you have a
winmodem driver with the proper portions in userspace, and the proper
portions in kernel space.

	Jeff





  reply	other threads:[~2001-10-08  2:37 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-09-29  1:18 [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices 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           ` Jeff Garzik [this message]
2001-10-08 12:19             ` linmodems (was Re: [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices) 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

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=Pine.LNX.3.96.1011007213223.2882B-100000@mandrakesoft.mandrakesoft.com \
    --to=jgarzik@mandrakesoft.com \
    --cc=ebiederman@uswest.net \
    --cc=jelson@circlemud.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@Elf.ucw.cz \
    --subject='linmodems (was Re: [ANNOUNCE] FUSD v1.00: Framework for User-Space Devices)' \
    /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

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