public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Miles Lane <miles@megapathdsl.net>
To: Erik Mouw <J.A.K.Mouw@ITS.TUDelft.NL>
Cc: Linus Torvalds <torvalds@transmeta.com>,
	Kernel Mailing List <linux-kernel@vger.kernel.org>,
	jerdfelt@valinux.com, usb@in.tum.de
Subject: Re: test12-pre6
Date: Wed, 06 Dec 2000 16:05:00 -0800	[thread overview]
Message-ID: <3A2ED42C.9050304@megapathdsl.net> (raw)
In-Reply-To: <20001206200803.C847@arthur.ubicom.tudelft.nl> <Pine.LNX.4.10.10012061131320.1873-100000@penguin.transmeta.com> <20001206210928.G847@arthur.ubicom.tudelft.nl>

Erik Mouw wrote:

> On Wed, Dec 06, 2000 at 11:38:30AM -0800, Linus Torvalds wrote:
> 
>> But I see something obviously wrong there: you have busmaster disabled.
>> 
>> Looking into the UHCI controller code, I notice that neither UHCI driver
>> actually does the (required)
>> 
>> 	pci_set_master(dev);
>> 
>> Please add that to just after a successful "pci_enable_device(dev)", and I
>> just bet your USB will start working.


I tested this change applied to usb-ohci.
I did not fix the problem where eth0 spits
out a ton of error messages:

eth0: Host error, FIFO diagnostic register 0000.
eth0: using default media MII
eth0: Host error, FIFO diagnostic register 0000.
eth0: using default media MII
eth0: Too much work in interrupt, status e003.
eth0: Host error, FIFO diagnostic register 0000.
eth0: using default media MII

This error occurs when I am trasfering data over my
DSL connection while moving my USB mouse.

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

  parent reply	other threads:[~2000-12-07  0:37 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-06  7:25 test12-pre6 Linus Torvalds
2000-12-06  7:50 ` test12-pre6 Alexander Viro
2000-12-06  7:54 ` [PATCH] test12-pre6 Alexander Viro
2000-12-06  8:03 ` Alexander Viro
2000-12-06  8:06 ` Alexander Viro
2000-12-06  8:26   ` Tigran Aivazian
2000-12-06  8:38     ` Tigran Aivazian
2000-12-06  8:56       ` Tigran Aivazian
2000-12-06  9:07         ` Alexander Viro
2000-12-06  9:29           ` Tigran Aivazian
2000-12-06  8:11 ` Alexander Viro
2000-12-06 11:47 ` test12-pre6 Wakko Warner
2000-12-06 12:04   ` test12-pre6 Andrew Morton
2000-12-07  1:43     ` test12-pre6 Wakko Warner
2000-12-06 13:06 ` test12-pre6 Tobias Ringstrom
2000-12-06 13:29   ` test12-pre6 Miles Lane
2000-12-06 18:08 ` test12-pre6 Erik Mouw
2000-12-06 18:38   ` test12-pre6 Linus Torvalds
2000-12-06 19:08     ` test12-pre6 Erik Mouw
2000-12-06 19:38       ` test12-pre6 Linus Torvalds
2000-12-06 20:09         ` test12-pre6 Erik Mouw
2000-12-06 21:06           ` test12-pre6 Jeff Garzik
2000-12-06 22:57             ` test12-pre6 Miles Lane
2000-12-06 23:10               ` test12-pre6 Johannes Erdfelt
2000-12-06 23:13               ` test12-pre6 Jeff Garzik
2000-12-06 23:17                 ` test12-pre6 Miles Lane
2000-12-07  0:05           ` Miles Lane [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-12-07  1:30 test12-pre6 Dunlap, Randy

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=3A2ED42C.9050304@megapathdsl.net \
    --to=miles@megapathdsl.net \
    --cc=J.A.K.Mouw@ITS.TUDelft.NL \
    --cc=jerdfelt@valinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@transmeta.com \
    --cc=usb@in.tum.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