From: Jon Smirl <jonsmirl@gmail.com>
To: John Richard Moser <nigelenki@comcast.net>
Cc: linux-kernel@vger.kernel.org
Subject: Re: binary drivers and development
Date: Fri, 11 Mar 2005 11:10:10 -0500 [thread overview]
Message-ID: <9e47339105031108102e0e4e60@mail.gmail.com> (raw)
In-Reply-To: <423082BF.6060007@comcast.net>
On Thu, 10 Mar 2005 12:24:15 -0500, John Richard Moser
<nigelenki@comcast.net> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> I've done more thought, here's a small list of advantages on using
> binary drivers, specifically considering UDI. You can consider a
> different implementation for binary drivers as well, with most of the
> same advantages.
Think about the impact the evolution of devfs and sysfs have on the
driver model. They are still evolving. Or the 32 to 64 bit impact on
ioctl's.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-03-11 16:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-10 16:28 binary drivers and development John Richard Moser
2005-03-10 16:48 ` Greg KH
2005-03-10 17:19 ` John Richard Moser
2005-03-10 17:24 ` Greg KH
2005-03-10 17:02 ` Ralf Baechle
2005-03-10 17:25 ` John Richard Moser
2005-03-10 17:24 ` John Richard Moser
2005-03-10 20:03 ` Diego Calleja
2005-03-10 20:14 ` John Richard Moser
2005-03-10 21:21 ` Lennart Sorensen
2005-03-10 21:42 ` John Richard Moser
2005-03-10 22:31 ` Lee Revell
2005-03-10 21:59 ` Peter Chubb
2005-03-10 22:32 ` John Richard Moser
2005-03-12 15:53 ` Felipe Alfaro Solana
2005-03-13 5:01 ` John Richard Moser
2005-03-13 7:17 ` Mike Galbraith
2005-03-10 22:45 ` Rik van Riel
2005-03-11 10:39 ` Ben Dooks
2005-03-11 16:39 ` Benedikt Spranger
2005-03-11 16:10 ` Jon Smirl [this message]
2005-03-11 9:33 ` [TROLL] " Xavier Bestel
-- strict thread matches above, loose matches on Subject: below --
2005-03-11 4:57 Albert Cahalan
2005-03-19 11:29 ` Eric W. Biederman
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=9e47339105031108102e0e4e60@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nigelenki@comcast.net \
/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.