From: David Brownell <david-b@pacbell.net>
To: linux-hotplug@vger.kernel.org
Subject: Re: hotplug-2001_01_23 and kernel 2.4.1
Date: Thu, 01 Feb 2001 01:06:11 +0000 [thread overview]
Message-ID: <marc-linux-hotplug-98099146120175@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98098107731236@msgid-missing>
[-- Attachment #1: Type: text/plain, Size: 1953 bytes --]
Try this patch. If it works, it should go to Linus.
It's not so much that things got switched, as that there are
two mechanisms for specifying device/interface type and they
don't strictly overlap (according to my brief investigation).
Some printers use one mechanism (interface typing), others
use another (device typing).
- Dave
----- Original Message -----
From: Greg KH <greg@kroah.com>
To: Gordon Lack <gmlack@freenet.co.uk>
Cc: <linux-hotplug-devel@lists.sourceforge.net>; <linux-usb-devel@lists.sourceforge.net>
Sent: Wednesday, January 31, 2001 2:41 PM
Subject: Re: hotplug-2001_01_23 and kernel 2.4.1
> I think there was a patch to the printer driver to fix this, but I don't
> remember, does anyone on linux-usb-devel or linux-hotplug see this same
> thing (I don't have a USB printer handy at the moment.)
>
> greg k-h
>
> On Wed, Jan 31, 2001 at 10:07:22PM +0000, Gordon Lack wrote:
> > I've just combined these 2.
> >
> > Bascially Ok, but one problem...
> >
> > I have an Epson Stylus 740 printer on USB. The kernel calls out to
> > hotplug with a TYPE os 7/1/2 for this (and hence no INTERFACE value).
> >
> > So, the scripts set the 3 interface values to 1000 (out of range).
> >
> > This doesn't match any of the 3 printer entries in
> > /lib/modules/2.4.1/modules.usbconf. *Those* entries have Interface
> > settings of 7/1/1, 7/1/2 and 7/1/3, but no Device settings.
> >
> > So it looks to me as though something has swaped the meaning of the
> > Interface and Device settings between whatever produces the
> > modules.usbconf files (if this is modutils then I've just upgrade to
> > 2.4.2) and what your hotplug scripts expect.
> >
> > If I swap the two pairs of 3 fields arround in the "while read ..."
> > line of the usb.agent script then all is Ok.
> >
> >
> > I hope this makes sense and is useful....
> >
> > Thanks....
> > Gordon Lack
>
> --
> greg@(kroah|wirex).com
>
[-- Attachment #2: printer-pre3.patch --]
[-- Type: application/octet-stream, Size: 622 bytes --]
--- 2.4.0-test12/drivers/usb/printer.c Tue Dec 12 10:20:37 2000
+++ linux/drivers/usb/printer.c Tue Dec 19 15:10:57 2000
@@ -613,6 +613,9 @@
};
static struct usb_device_id usblp_ids [] = {
+ { bDeviceClass: 7, bDeviceSubClass: 1, bDeviceProtocol: 1},
+ { bDeviceClass: 7, bDeviceSubClass: 1, bDeviceProtocol: 2},
+ { bDeviceClass: 7, bDeviceSubClass: 1, bDeviceProtocol: 3},
{ bInterfaceClass: 7, bInterfaceSubClass: 1, bInterfaceProtocol: 1},
{ bInterfaceClass: 7, bInterfaceSubClass: 1, bInterfaceProtocol: 2},
{ bInterfaceClass: 7, bInterfaceSubClass: 1, bInterfaceProtocol: 3},
next prev parent reply other threads:[~2001-02-01 1:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-31 22:41 hotplug-2001_01_23 and kernel 2.4.1 Greg KH
2001-02-01 1:06 ` David Brownell [this message]
2001-02-01 1:54 ` David Brownell
2001-02-02 0:49 ` Gordon Lack
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-98099146120175@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).