linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <bh40@calva.net>
To: Tom Rini <trini@kernel.crashing.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: ADB probing
Date: Thu, 7 Oct 1999 18:15:41 +0200	[thread overview]
Message-ID: <19991007181541.031811@mailhost.mipsys.com> (raw)
In-Reply-To: <Pine.LNX.4.10.9910061626290.10804-100000@opus.bloom.county>


On Wed, Oct 6, 1999, Tom Rini <trini@kernel.crashing.org> wrote:

>I've run into a wierd problem with ADB stuff, and I wonder if anyone has
>an idea on how to work/fix this.  What I'm trying to do right now is fix
>up kudzu so it can probe for things on the ADB bus.  Right now it does
>what all the other old config tools did, and pokes at /dev/adbmouse.  The
>problem is right now this works if there's any adb device present (one of
>the machines I checked only has an adb kbd, tho adbmouse suport is
>compiled in).  Also, is there any way to see if the machine has an adb
>keyboard installed?  Thanks..

Look at my trackpad tool source code, you'll find an example of probing
the devices. That's not an ideal way since part of the "device type"
information is the original address of the device before relocation, and
you can't ask the device about this. You should be able to handle most
cases with just the handlerID, but I'll look into adding a couple of
ioctls to /dev/adb so you can also get the original address. (I'll do
this next week end, ping me if I forget, I'm doing too many things at the
same time those last few weeks).

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

  parent reply	other threads:[~1999-10-07 16:15 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-10-06 23:47 ADB probing 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 [this message]
  -- strict thread matches above, loose matches on Subject: below --
1999-10-07 16:21 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-08 10:08   ` Benjamin Herrenschmidt
1999-10-08 12:33     ` Michael Schmitz
1999-10-08 13:06       ` Benjamin Herrenschmidt
1999-10-11  9:46         ` Michael Schmitz

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=19991007181541.031811@mailhost.mipsys.com \
    --to=bh40@calva.net \
    --cc=linuxppc-dev@lists.linuxppc.org \
    --cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).