From: Brad Boyer <flar@allandria.com>
To: Matthias Urlichs <smurf@smurf.noris.de>
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>,
Linux/m68k <linux-m68k@lists.linux-m68k.org>,
Linux/m68k on Mac <linux-mac68k@mac.linux-m68k.org>,
Linux/PPC Development <linuxppc-dev@lists.linuxppc.org>
Subject: Re: [linux-mac68k] Re: drivers/macintosh/Kconfig (was: Re: Linux 2.6.3-rc1)
Date: Sun, 8 Feb 2004 14:19:49 -0800 [thread overview]
Message-ID: <20040208221948.GA14225@pants.nu> (raw)
In-Reply-To: <20040208220710.GA5933@kiste>
On Sun, Feb 08, 2004 at 11:07:10PM +0100, Matthias Urlichs wrote:
> This may be a stupid question, but I've got an iMate, and it already
> works rather well -- it checks whether the (single!) ADB device behind
> it is a keyboard or a mouse, and then translates that to standard PCish
> USB keycodes or mouse events, transparently.
Yes, it can convert a standard keyboard and mouse directly to a USB
keyboard and mouse, but if you want to treat it as a generic ADB
bus, you need a driver.
> Do you have documentation that says it can do more ..?
How about the official page?
http://www.griffintechnology.com/products/imate/
It specifically says "and other ADB peripherals" in the description.
The various documentation if you search around their site talks
about how you can just plug in a keyboard or mouse and it works,
but has a driver download for OSX and OS9 to allow using anything
with a real ADB driver to work.
I'm pretty sure keyboards and mice are the only devices currently
supported on ADB in Linux anyway, but it's a thought for the future.
Brad Boyer
flar@allandria.com
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2004-02-08 22:19 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.58.0402061823040.30672@home.osdl.org>
2004-02-08 14:25 ` drivers/macintosh/Kconfig (was: Re: Linux 2.6.3-rc1) Geert Uytterhoeven
2004-02-08 14:53 ` David D. Kilzer
2004-02-08 19:32 ` Geert Uytterhoeven
2004-02-08 20:57 ` Brad Boyer
2004-02-08 21:15 ` [linux-mac68k] " David D. Kilzer
2004-02-08 22:16 ` Geert Uytterhoeven
2004-02-08 23:00 ` David D. Kilzer
2004-02-08 21:29 ` Benjamin Herrenschmidt
2004-02-08 21:59 ` Brad Boyer
2004-02-08 22:22 ` Benjamin Herrenschmidt
2004-02-08 23:05 ` Brad Boyer
2004-02-08 22:07 ` [linux-mac68k] " Matthias Urlichs
2004-02-08 22:19 ` Brad Boyer [this message]
2004-02-08 22:25 ` Benjamin Herrenschmidt
2004-02-08 22:39 ` Matthias Urlichs
2004-02-08 21:26 ` Benjamin Herrenschmidt
2004-02-08 22:07 ` Geert Uytterhoeven
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=20040208221948.GA14225@pants.nu \
--to=flar@allandria.com \
--cc=benh@kernel.crashing.org \
--cc=geert@linux-m68k.org \
--cc=linux-m68k@lists.linux-m68k.org \
--cc=linux-mac68k@mac.linux-m68k.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=smurf@smurf.noris.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).