From: Stefan Jeglinski <jeglin@4pi.com>
To: Michael Schmitz <schmitz@opal.biophys.uni-duesseldorf.de>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: usb wheel mouse, XF4.0
Date: Tue, 28 Nov 2000 14:55:28 -0500 [thread overview]
Message-ID: <p0433010ab649bafec687@[206.6.156.5]> (raw)
In-Reply-To: <Pine.LNX.4.10.10011282036580.22745-100000@opal.biophys.uni-duesseld orf.de>
> > ... not that there isn't a simple trick, and not that I've exhausted
>> all my possibilities yet, but my level of exasperation is rather high
>> at the moment... so far I'm chalking it up mostly to usb still being
>> not really built into the stable kernel.
>
>Wrong: support for USB PCI cards not being built into the stable kernel.
>Support for recent Mac builtin USB controllers (OHCI) is just fine.
>Support for anything above the controller (protocols) apparently works
>fine with OHCI (PPC) and UHCI (Intel).
I take it you're saying that PCI USB cards are not being officially
supported, but they may work. Otherwise I don't get your comment. The
backport into 2.2.18 (which will be defined as stable when it is no
longer pre status) seems to include config options for many keyspan
devices, among others. Are these not PCI cards? I could clearly be
dead wrong here, I'm now surmising.
>What exactly is on the PCI USB card?
It's an Orangelink USB/Firewire card, 2 usbs, 2 firewire ports.
Otherwise I'm not sure what your question means. Do you ask for chip
brands/numbers, etc?
I -think- the card is seen fine, as per my recent dmesg posted on
linuxppc-user. AFAICT, I've done everything as I should with the
input layer. I can't absolutely prove the mouse works (Logitech
2-button + wheel), but I -think- it is there. The problem is that in
console, I get no mouse action (I can see and move a cursor around
the screen with the ADB mouse), and in X, it's as if only every
10000th mouse event is being registered (every once in a while, when
there is disk activity, the USB mouse will jump in the general
direction I've moved it, the ADB mouse continues to work fine).
As I implied in my e-mail but could have been clearer about, I'm not
at all certain that the issue really is with the usb or the mouse or
the usb card, etc. It's just that for me, on an old-world Mac, the
usb experience as a whole has a flaw somewhere that I've been unable
to figure out.
Stefan Jeglinski
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2000-11-28 19:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <Pine.LNX.4.10.10011282036580.22745-100000@opal.biophys.uni-duesseld orf.de>
2000-11-28 19:55 ` Stefan Jeglinski [this message]
2000-11-28 20:23 ` usb wheel mouse, XF4.0 Michael Schmitz
2000-11-29 8:33 ` Timothy A. Seufert
2000-11-29 9:02 ` Andreas Tobler
2000-11-29 14:07 ` Stefan Jeglinski
2000-11-29 17:08 ` Benjamin Herrenschmidt
2000-11-29 17:14 ` Benjamin Herrenschmidt
2000-12-01 7:09 ` Michel Lanners
2000-11-29 13:45 ` christopher.murtagh
[not found] <Pine.LNX.4.10.10011282036580.22745-100000@opal.biophys.uni-duesseldorf.de >
2000-11-29 8:15 ` Timothy A. Seufert
2000-11-29 9:30 ` Michael Schmitz
2000-11-29 13:10 ` Benjamin Herrenschmidt
[not found] <Pine.LNX.4.10.10011282109440.2086-100000@zirkon.biophys.uni-duessel dorf.de>
2000-11-28 22:32 ` Stefan Jeglinski
2000-11-28 23:15 ` Michael Schmitz
[not found] <F269nW0kKIBXEHt3V5g00007774@hotmail.com>
2000-11-28 19:31 ` Stefan Jeglinski
2000-11-28 19:39 ` 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='p0433010ab649bafec687@[206.6.156.5]' \
--to=jeglin@4pi.com \
--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).