From: Benjamin Herrenschmidt <bh40@calva.net>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: ADB probing
Date: Thu, 7 Oct 1999 18:21:56 +0200 [thread overview]
Message-ID: <19991007182156.030455@mailhost.mipsys.com> (raw)
On Thu, Oct 7, 1999, Michael Schmitz
<schmitz@opal.biophys.uni-duesseldorf.de> wrote:
>I'd rather not poll the ADB bus if it can be avoided. How does MacOS detect
>a new mouse device? But you could always force a bus reset and rescan via
>/dev/adb.
Be careful that the bus reset will cause an automatic re-probing and
re-init of the bus and devices by the drivers in mac_keyb.c. (This way,
we could make a userland tool that sends the bus reset and have a real
hot-swap ADB, just reset the bus after the hot swap). This feature is
mainly used by the sleep code for now.
--
Perso. e-mail: <mailto:bh40@calva.net>
Work e-mail: <mailto:benh@mipsys.com>
BenH. Web : <http://calvaweb.calvacom.fr/bh40/>
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~1999-10-07 16:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-10-07 16:21 Benjamin Herrenschmidt [this message]
1999-10-07 18:28 ` ADB probing Michael Schmitz
1999-10-07 19:38 ` David A. Gatwood
1999-10-08 9:44 ` Michael Schmitz
1999-10-08 23:07 ` Brad Midgley
1999-10-11 12:28 ` Michael Schmitz
1999-10-14 22:25 ` multihead (Re: ADB probing) Brad Midgley
1999-10-08 10:08 ` ADB probing Benjamin Herrenschmidt
1999-10-08 12:33 ` Michael Schmitz
1999-10-08 13:06 ` Benjamin Herrenschmidt
1999-10-11 9:46 ` Michael Schmitz
-- strict thread matches above, loose matches on Subject: below --
1999-10-06 23:47 Tom Rini
1999-10-07 9:27 ` Michael Schmitz
1999-10-07 11:22 ` Timothy Wall
1999-10-07 12:16 ` Michael Schmitz
1999-10-07 16:15 ` Benjamin Herrenschmidt
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=19991007182156.030455@mailhost.mipsys.com \
--to=bh40@calva.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=schmitz@opal.biophys.uni-duesseldorf.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.