From: Sape Mullender <sape@plan9.bell-labs.com>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] usbd problem
Date: Wed, 13 Feb 2008 11:18:18 -0500 [thread overview]
Message-ID: <f6ae74a18df8ba7d0e1f5528dc422d42@plan9.bell-labs.com> (raw)
In-Reply-To: <a94f90e6ed09ffa5af667c417e0e00ae@quanstro.net>
>> Are you killing the old usbd before starting a new one?
>
> yes.
>
>> And is this uhci or ohci?
>
> ohci. oddly, my uhci ich9r machine doesn't recognize
> either of my extensive collection of two usb devices.
You may be running the usbd with faulty dump.c. If your
devices show up in /dev/usb0/1/status with just one
line and 0x000000 for Class/Subclass/Proto, then you're
almost certainly running the old dump.c.
In dump.c, five lines before the bottom of the file,
change len = b[0] - 1 into len = b[0]
A new version should already have been posted.
Sape
next prev parent reply other threads:[~2008-02-13 16:18 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-12 1:36 erik quanstrom
2008-02-12 8:20 ` Richard Miller
2008-02-12 13:59 ` Sape Mullender
2008-02-12 14:13 ` erik quanstrom
2008-02-12 14:35 ` Sape Mullender
2008-02-12 14:42 ` Fco. J. Ballesteros
2008-02-13 0:50 ` erik quanstrom
2008-02-13 14:32 ` Richard Miller
2008-02-13 14:45 ` erik quanstrom
2008-02-13 14:52 ` Richard Miller
2008-02-13 15:04 ` erik quanstrom
2008-02-13 16:18 ` Sape Mullender [this message]
2008-02-13 16:37 ` erik quanstrom
2008-02-13 17:09 ` Sape Mullender
2008-02-12 8:21 Richard Miller
2008-02-12 13:21 ` erik quanstrom
2008-02-12 21:24 ` Richard Miller
2008-02-12 21:28 ` geoff
2008-02-12 21:33 ` Richard Miller
2008-02-12 21:37 ` erik quanstrom
2008-02-12 22:18 ` Richard Miller
2008-02-12 23:05 ` geoff
2008-02-13 6:31 ` arisawa
2008-02-13 8:25 ` Richard Miller
2008-02-13 8:54 ` arisawa
2008-02-13 10:58 ` Richard Miller
2008-02-13 14:13 ` Richard Miller
2008-02-13 18:49 ` geoff
2008-02-13 15:54 ` Richard Miller
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=f6ae74a18df8ba7d0e1f5528dc422d42@plan9.bell-labs.com \
--to=sape@plan9.bell-labs.com \
--cc=9fans@cse.psu.edu \
/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).