9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@terzarima.net>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] just checking ...
Date: Thu, 23 Mar 2006 21:29:05 +0000	[thread overview]
Message-ID: <4fca90b56c2fa4cc2cc8172121802d20@terzarima.net> (raw)
In-Reply-To: <942177f118a07e7cbb4d452ca3429bcd@proxima.alt.za>

[-- Attachment #1: Type: text/plain, Size: 137 bytes --]

perhaps your devusb.c and usbd are not up to date.
the latter now sets the vendor and device IDs, and the former
displays them if set

[-- Attachment #2: Type: message/rfc822, Size: 3236 bytes --]

From: lucio@proxima.alt.za
To: 9fans@cse.psu.edu
Subject: Re: [9fans] just checking ...
Date: Thu, 23 Mar 2006 20:55:19 +0200
Message-ID: <942177f118a07e7cbb4d452ca3429bcd@proxima.alt.za>

>     || /n/sources/contrib/zwansch/usbuart.tgz

In usbuart.c:

	char ident[]		= "Enabled 0x0000ff 0x067b 0x2303";

Is that for real?  I've never noticed anything beyond the first "Enabled" argument, and I only get:

	Enabled 0x0000ff
	 0 0x0000ff         57 bytes          5 blocks
	 1 0x0000ff          0 bytes          0 blocks
	 2 0x0000ff          0 bytes          0 blocks
	 3 0x0000ff          0 bytes          0 blocks

for my Ericsson USB connector, which NetBSD identifies as:

	Prolific Technolgy Inc. USB-Serial Controller. rev 1.10/3.00. addr 3

++L

  reply	other threads:[~2006-03-23 21:29 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-03-22 22:53 Ronald G Minnich
2006-03-22 23:47 ` erik quanstrom
2006-03-22 23:51   ` Ronald G Minnich
2006-03-23  0:01     ` Steve Simon
2006-03-23  0:02     ` erik quanstrom
2006-03-23  0:03     ` erik quanstrom
2006-03-23  0:01       ` Ronald G Minnich
2006-03-23  0:21         ` jmk
2006-03-23 15:13           ` Ronald G Minnich
2006-03-23  8:54     ` Gabriel Diaz
2006-03-23  9:57       ` Christoph Lohmann
2006-03-23 18:55         ` lucio
2006-03-23 21:29           ` Charles Forsyth [this message]
2006-03-24  5:35             ` lucio
2006-03-23 22:55           ` Christoph Lohmann
2006-03-24  5:24             ` lucio
2006-03-24  5:38             ` lucio
2006-03-24 10:51               ` Christoph Lohmann
2006-03-24 11:03                 ` Charles Forsyth
2006-03-24 11:07                   ` Charles Forsyth
2006-03-24 18:47                 ` lucio
2006-03-24 20:51                   ` Christoph Lohmann
2006-03-25 13:18                     ` lucio
2006-03-24 14:50             ` lucio
2006-03-24 17:41               ` Charles Forsyth
2006-03-24 18:35                 ` lucio
2006-03-24 18:59                   ` Charles Forsyth
2006-03-24 20:41               ` Christoph Lohmann
2006-03-25 13:17                 ` lucio
2006-03-25 13:33                   ` Russ Cox
2006-03-25 14:35                     ` lucio
2006-03-25 14:56                       ` Russ Cox
2006-03-25 17:07                   ` lucio
2006-03-25 22:01                     ` Christoph Lohmann
2006-03-26 19:45                       ` lucio
2006-03-23 15:14       ` Ronald G Minnich
2006-03-23 16:57         ` Charles Forsyth

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=4fca90b56c2fa4cc2cc8172121802d20@terzarima.net \
    --to=forsyth@terzarima.net \
    --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).