From: Alex deVries <alex@linuxcare.com>
To: "Brian S. Julin" <bri@mojo.calyx.net>
Cc: parisc-linux@lists.parisc-linux.org, Helge Deller <deller@gmx.de>,
maswan@acc.umu.se
Subject: Re: [parisc-linux] TODO-list entry of "HIL keyboard driver needs updating"
Date: Mon, 05 Mar 2001 11:51:22 -0500 [thread overview]
Message-ID: <3AA3C40A.C3D320FC@linuxcare.com> (raw)
In-Reply-To: Pine.BSO.4.33.0103050014290.32438-100000@mojo.calyx.net
"Brian S. Julin" wrote:
>
> Hmmm... Brian might refer to me, but I do not know who Alex is.
> The only other person who showed interest in the driver was
> Helge Deller. We do NOT have access to the HIL specs, and
> the driver I would like to write will need more detail than that
> gleaned from the BSD/linux/mklinux source code. But, if the
> below refers to another two people who DO have access to the
> docs, then it would be nice if they would tell me what needs
> to be done to get me access to them.
I'm Alex.
The reason that I think I have HIL specs is because it's mentioned in
the WAX documentation I have under NDA. I can't send out copies of it,
but I can give information necessary for writing code.
- Alex
--
Alex deVries, Principal Solutions Architect, The Puffins at Linuxcare
613.562.2759 tel
alex@linuxcare.com, http://www.linuxcare.com/
Linuxcare, Putting open source to work.
next prev parent reply other threads:[~2001-03-05 16:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <00121503462102.00304@P100>
2001-03-05 5:20 ` [parisc-linux] TODO-list entry of "HIL keyboard driver needs updating" Brian S. Julin
2001-03-05 7:07 ` Grant Grundler
2001-03-05 16:51 ` Alex deVries [this message]
2001-03-05 17:26 ` Brian S. Julin
2001-03-06 21:56 ` [parisc-linux] TODO-list entry of "HIL keyboard driver needs u pdating" 5116
2001-03-07 9:00 ` [parisc-linux] TODO-list entry of "HIL keyboard driver needs updating" Alex deVries
2001-03-09 19:52 ` 5116
2001-03-05 18:27 Mike Hibler
-- strict thread matches above, loose matches on Subject: below --
2001-03-05 4:47 Mattias Wadenstein
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=3AA3C40A.C3D320FC@linuxcare.com \
--to=alex@linuxcare.com \
--cc=bri@mojo.calyx.net \
--cc=deller@gmx.de \
--cc=maswan@acc.umu.se \
--cc=parisc-linux@lists.parisc-linux.org \
/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