From: Greg KH <greg@kroah.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Dirk Eibach <eibach@gdsys.de>,
akpm@linux-foundation.org, linux-kernel@vger.kernel.org,
apw@shadowen.org, linux-usb@vger.kernel.org
Subject: Re: [PATCH] usb: add sysfs configuration interface for CP2101
Date: Mon, 3 Mar 2008 08:28:28 -0800 [thread overview]
Message-ID: <20080303162827.GB11592@kroah.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0803031006510.3456-100000@iolanthe.rowland.org>
On Mon, Mar 03, 2008 at 10:07:41AM -0500, Alan Stern wrote:
> On Mon, 3 Mar 2008, Dirk Eibach wrote:
>
> > From: Dirk Eibach <eibach@gdsys.de>
> >
> > The usb configuration data for the Silabs CP2101 usb to uart bridge
> > controller can be customized:
> > - Vendor ID
> > - Product ID
> > - Power Descriptor
> > - Release Number
> > - Serial Number
> > - Product Description String
> >
> > Silabs provides a windows-only tool to do that.
> > Since we use linux-only machines in our production-environment, we have no
> > proper way to customize the chips for our purpose.
> > So I added sysfs configuration support to the linux driver.
>
> Surely this sort of thing is better done in userspace, with libusb.
I agree, any reason why you have not tried that? Adding files like
"vendor_id" to an interface directory in sysfs could cause a lot of
people to get very confused, very quickly :)
thanks,
greg k-h
next prev parent reply other threads:[~2008-03-03 16:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-29 9:02 Dirk Eibach
2008-02-29 9:40 ` Dirk Eibach
2008-02-29 10:02 ` Andrew Morton
2008-02-29 12:31 ` Dirk Eibach
2008-02-29 20:35 ` Andrew Morton
2008-03-03 9:27 ` Dirk Eibach
2008-03-03 15:07 ` Alan Stern
2008-03-03 16:28 ` Greg KH [this message]
2008-03-04 7:03 ` Dirk Eibach
2008-03-04 17:52 ` Alan Stern
2008-03-04 19:51 ` Greg KH
2008-04-09 12:16 ` Andy Whitcroft
2008-03-01 0:33 ` Greg KH
2008-02-29 14:44 ` Andy Whitcroft
2008-02-29 20:46 ` Andrew Morton
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=20080303162827.GB11592@kroah.com \
--to=greg@kroah.com \
--cc=akpm@linux-foundation.org \
--cc=apw@shadowen.org \
--cc=eibach@gdsys.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=stern@rowland.harvard.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
all inboxes | Powered by JetHome®