From: Benjamin Herrenschmidt <bh40@calva.net>
To: Paul Mackerras <paulus@cs.anu.edu.au>, linuxppc-dev@lists.linuxppc.org
Subject: [PATCH] ADB stuffs (req. for trackpad patch)
Date: Sat, 26 Dec 1998 19:04:05 +0100 [thread overview]
Message-ID: <19981226190405.026346@smtp.calvacom.fr> (raw)
[-- Attachment #1: Type: text/plain, Size: 723 bytes --]
Enclosed is a patch to drivers/macintosh/adb.c (and
includes/asm-ppc/adb.h since there's a new exported function).
The new function handles ADB handlerID negociation (try to change the
default handler ID of a device, returns if it fails). It updates the
kernel's internal table of handlerIDs too, just in case...
It's called by new hardware init code in the previously sent patch to
mac_keyb.c
Note also that I changed the adb register function so that it matches by
handlerID or original address. if you want to match by original address,
pass 0 to handlerID, if you want the opposite, pass 0 to original address.
--
E-Mail: <mailto:bh40@calva.net>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
[-- Attachment #2: adb.patch.gz --]
[-- Type: application/octet-stream, Size: 972 bytes --]
reply other threads:[~1998-12-26 18:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=19981226190405.026346@smtp.calvacom.fr \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@cs.anu.edu.au \
/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;
as well as URLs for NNTP newsgroup(s).