linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
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: Fri, 8 Oct 1999 15:06:17 +0200	[thread overview]
Message-ID: <19991008150617.016099@mailhost.mipsys.com> (raw)
In-Reply-To: <199910081233.OAA03575@simul.biophys.uni-duesseldorf.de>


On Fri, Oct 8, 1999, Michael Schmitz
<schmitz@opal.biophys.uni-duesseldorf.de> wrote:

>Thanks, I forgot that sleeping will power down all ADB devices. That still
>doesn't force a bus reset but a bus reset may not be what we want anyway. 

Yes, sleep powers down all ADB devices, and that's why the ADB code
contains a sleep notifier which will do a bus reset on wakeup. The adb
code will then re-do the probing and re-adressing and notify it's own
clients (mac_keyb.c drivers) via it's own notifier that the bus was reset
so they get a chance to re-initialize their various devices.
The /dev/adb code will also catch bus reset commands and do the same
thing. I still think that we should try to do something more complex than
a reset+reprobe.

>Can we add a SysRQ code for this? Speaking of which, what is the magic sysrq 
>key on a Lombard, or the shutdown key combo? I couldn't find that in the
>keyboard driver ...

>That's about what I've been discussing with some (including Paul and hpa)
>about two years ago. We could add adbkeyb (raw keyboard data) and adbmouse
>(the busmouse device) and possibly adbtablet for good measure and give up 
>that hijacked misc minor 10, finally. 
>
>I can help writing and testing this on a Powerbook, I just don't have a
>desktop Mac to connect multiple ADB devices to. 

My idea was to work on this this Sunday, but if you want to write it now,
feel free to do so ;) I can test it on various configurations at work.

-- 
           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/

  reply	other threads:[~1999-10-08 13:06 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-07 16:21 ADB probing Benjamin Herrenschmidt
1999-10-07 18:28 ` 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 [this message]
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=19991008150617.016099@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 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).