From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: patch for working around 2.2. UBS brokenness.
Date: Fri, 30 Mar 2001 17:21:35 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98597325122720@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98597140917162@msgid-missing>
Fix is in CVS now -- thanks for the patch!
----- Original Message -----
From: "Ben Woodard" <ben@valinux.com>
To: <linux-hotplug-devel@lists.sourceforge.net>
Sent: Friday, March 30, 2001 8:38 AM
Subject: patch for working around 2.2. UBS brokenness.
> Here is a simple patch for /etc/hotplug/usb.agent that works around
> the way that USB on 2.2.1[89] identify the revision.
>
> =================================> RCS file: RCS/usb.agent,v
> retrieving revision 1.1
> diff -u -r1.1 usb.agent
> --- usb.agent 2001/03/29 16:36:54 1.1
> +++ usb.agent 2001/03/30 16:02:02
> @@ -109,6 +109,11 @@
> exit 1
> fi
>
> + # work around 2.2 brokenness
> + # munges the usb_bcdDevice such that it is a integer rather
> + # than a float: e.g. 1.0 become 0100
> + PRODUCT=`echo $PRODUCT | sed -e "s+\.\([0-9]\)$+.\10+" -e "s/\.$/00/" \
> + -e "s+/\([0-9]\)\.\([0-9][0-9]\)+/0\1\2+"`
> set `echo $PRODUCT | $AWK -F/ '{print "0x" $1, "0x" $2, "0x" $3 }'` ''
> usb_idVendor=$1
> usb_idProduct=$2
>
> _______________________________________________
> Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
> Linux-hotplug-devel@lists.sourceforge.net
> http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
prev parent reply other threads:[~2001-03-30 17:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-30 16:38 patch for working around 2.2. UBS brokenness Ben Woodard
2001-03-30 17:21 ` David Brownell [this message]
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=marc-linux-hotplug-98597325122720@msgid-missing \
--to=david-b@pacbell.net \
--cc=linux-hotplug@vger.kernel.org \
/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).