All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: walt <wa1ter@myrealbox.com>
Cc: "Randy.Dunlap" <rddunlap@osdl.org>,
	lkml <linux-kernel@vger.kernel.org>,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: [2.6.x]  USB Zip drive kills ps2 mouse.
Date: Fri, 5 Mar 2004 20:49:16 +0000	[thread overview]
Message-ID: <20040305204916.GC7254@mail.shareable.org> (raw)
In-Reply-To: <40452AB3.2060400@myrealbox.com>

> I've narrowed it down to the uhci_hcd module -- all the rest can
> be compiled in or as modules, doesn't matter.
> 
> Just in case I was vague:  the Zip drive works great regardless --
> it's only the ps2 mouse which is affected by this weird problem.
> No cursor movement at all if the Zip is plugged in during boot.

I don't know if it's related, but whenever I load the uhci_hcd module
on my laptop, or whenever I plug in a USB device while that module is
loaded (sorry, I forget which and can't test it now) - the floppy disk
motor and light are turned on for a couple of seconds!

Now, why would a USB event trigger the floppy disk motor?  It doesn't
happen with 2.4, and it doesn't happen on my desktop machine which is
OHCI+EHCI.

Perhaps the uhci_hcd driver is trampling on some ISA I/O port that it
shouldn't be, which is causing both my floppy motor oddity and your
mouse problem?

-- Jamie

  reply	other threads:[~2004-03-05 20:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20040301122450.69a1f36e.rddunlap@osdl.org>
2004-03-02  5:58 ` [2.6.x] USB Zip drive kills ps2 mouse Randy.Dunlap
2004-03-03  0:45   ` walt
2004-03-05 20:49     ` Jamie Lokier [this message]
2004-03-05 21:13       ` [linux-usb-devel] " Alan Stern
     [not found] <20040302164756.6e41a3c6.rddunlap@osdl.org>
2004-03-03  6:30 ` Randy.Dunlap
2004-02-29 16:47 walt

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=20040305204916.GC7254@mail.shareable.org \
    --to=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=rddunlap@osdl.org \
    --cc=wa1ter@myrealbox.com \
    /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.