From: Greg KH <greg@wirex.com>
To: Eric Sandeen <sandeen@sgi.com>
Cc: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] updates for KLSI usb->ethernet
Date: Wed, 7 Feb 2001 00:51:26 -0800 [thread overview]
Message-ID: <20010207005126.A32480@wirex.com> (raw)
In-Reply-To: <3A80ED7C.F3A92D5@sgi.com>
In-Reply-To: <3A80ED7C.F3A92D5@sgi.com>; from sandeen@sgi.com on Wed, Feb 07, 2001 at 12:38:52AM -0600
On Wed, Feb 07, 2001 at 12:38:52AM -0600, Eric Sandeen wrote:
> Any thoughts on what would be more correct,
>
> a) device descriptor silently changes
> b) device magically disconnects/reconnects on its own
>
> Both seem a bit odd, but take your pick. :)
b) is more like other devices. They use 1 descriptor id for the "I have
no firmware" state, then after firmware is downloaded, they disconnect,
and reconnect with a new id which means they have the firmware loaded.
Lots of usb-serial devices do this, and so does just about any
Anchor/Cypress EZ-USB chip based design.
Silently changing descriptor ids while connected is just asking for
trouble :)
You also might want to post this to linux-usb-devel as that's where the
authors of this driver are known to hang out.
greg k-h
--
greg@(kroah|wirex).com
http://immunix.org/~greg
-
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/
next prev parent reply other threads:[~2001-02-07 8:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 6:38 [PATCH] updates for KLSI usb->ethernet Eric Sandeen
2001-02-07 8:51 ` Greg KH [this message]
2001-02-08 20:22 ` [NEW][PATCH] updates for KLSI Eric Sandeen
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=20010207005126.A32480@wirex.com \
--to=greg@wirex.com \
--cc=linux-kernel@vger.kernel.org \
--cc=sandeen@sgi.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.