All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan <alan@lxorguk.ukuu.org.uk>
To: Greg KH <greg@kroah.com>
Cc: linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: Userspace I/O driver core
Date: Thu, 14 Dec 2006 10:52:35 +0000	[thread overview]
Message-ID: <20061214105235.46c080ae@localhost.localdomain> (raw)
In-Reply-To: <20061214010608.GA13229@kroah.com>

> But in order to get this core into the kernel tree, we need to have some
> "real" drivers written that use it.  So, for anyone that wants to see
> this go into the tree, now is the time to step forward and post your
> patches for hardware that this kind of driver interface is needed.

Might be kind of hairy given uio_read() doesn't even return from the
kernel. This code simply isn't fit for purpose, philosophical debate
aside.

Alan

  parent reply	other threads:[~2006-12-14 10:44 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-14  1:06 Userspace I/O driver core Greg KH
2006-12-14  5:48 ` Ben Nizette
2006-12-14  9:44 ` Avi Kivity
2006-12-14 10:19   ` Arjan van de Ven
2006-12-14 10:46     ` Avi Kivity
2006-12-14 10:54       ` Arjan van de Ven
2006-12-14 10:56         ` Avi Kivity
2006-12-14 17:54           ` Greg KH
2006-12-16 14:48     ` Dr. David Alan Gilbert
2006-12-14 10:25   ` Hans-Jürgen Koch
2006-12-14 10:48     ` Avi Kivity
2006-12-14 12:39       ` Jan Engelhardt
2006-12-14 13:38         ` Avi Kivity
2006-12-14 17:48           ` Jan Engelhardt
2006-12-14 18:00       ` Greg KH
2006-12-14 10:52 ` Alan [this message]
2006-12-14 11:22   ` Thomas Gleixner
2006-12-14 11:39     ` Alan
2006-12-14 11:37       ` Hans-Jürgen Koch
2006-12-14 12:45         ` Alan
2006-12-14 12:37 ` Jan Engelhardt
2006-12-14 16:10 ` linux-os (Dick Johnson)
2006-12-14 21:55   ` Ben Nizette

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=20061214105235.46c080ae@localhost.localdomain \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=greg@kroah.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tglx@linutronix.de \
    /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.