From: Jeff Garzik <jgarzik@pobox.com>
To: Alan Cox <alan@lxorguk.ukuu.org.uk>
Cc: linux-kernel@vger.rutgers.edu
Subject: Re: Universal Driver Interface spec available
Date: Wed, 01 Sep 1999 17:50:07 -0400 [thread overview]
Message-ID: <37CD9F8F.F3881475@pobox.com> (raw)
In-Reply-To: E11MI2e-0003fR-00@the-village.bc.nu
Alan Cox wrote:
> Not sure why anyone thinks this is Linux relevant 8) - other than it will help
> to make our drivers even faster than the competition if they adopt it.
> Have a read, but keep a bucket handy
In response to you and David: I agree :) But if vendors take this
seriously, I have a feeling a UDI interface will eventually appear.
Lack of UDI support may be an encouragement or a discouragement,
depending on the complexity of the device driver.
On a related subject, I think Linux could use a much more coherent --
and documented -- device driver interface. Writing portable Linux
device drivers requires very in-depth knowledge of the Linux 'arch'
code; I find myself checking the Alpha or Sparc arch code a lot to make
sure that the I/O routines and such that I call work as expected.
Regards,
Jeff
--
Americans' greatest fear is that America will turn out to have been a
phenomenon, not a civilization.
-- Shirley Hazzard, "Transit of Venus"
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~1999-09-01 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-09-01 20:54 Universal Driver Interface spec available Jeff Garzik
1999-09-01 21:30 ` David S. Miller
1999-09-01 21:35 ` Alan Cox
1999-09-01 21:50 ` Jeff Garzik [this message]
1999-09-02 1:00 ` David Olofson
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=37CD9F8F.F3881475@pobox.com \
--to=jgarzik@pobox.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=linux-kernel@vger.rutgers.edu \
/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