[PATCH] linux-2.4.1-pre9/drivers/usb/serial/mct_u232.c usb_device_id table broken by new format

From: Adam J. Richter (adam@yggdrasil.com)
Date: Sat Jan 20 2001 - 06:04:30 EST

Next message: Nick Urbanik: "Re: rsync + ssh fail on raid; okay on 2.2.x"
Previous message: Eric Lammerts: "Re: Off-Topic: how do I trace a PID over double-forks?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

The format of usb_device_id tables was recently changed
(just before 2.4.0, I think) to include a match_flags field. A bit
set to one in that field indicates that a given member of the structure
contains a valid value that must match. A bit set to zero indicates
a wildcard (skip the comparison). Compiling a driver that uses the old
format results in that driver having a usb_device_id structure that
has an all zeroes match_flags, which means don't compare anything.
That is, it is a completely wildcard and will match every USB interface.

As of 2.4.1-pre9, there appears to be only USB driver that
was missed: drivers/usb/serial/mct_u232.c. This patch fixes the problem.

-- Adam J. Richter __ ______________ 4880 Stevens Creek Blvd, Suite 104 adam@yggdrasil.com \ / San Jose, California 95129-1034 +1 408 261-6630 | g g d r a s i l United States of America fax +1 408 261-6631 "Free Software For The Rest Of Us."

text/plain attachment: usb-mct.diff

- 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 message: Nick Urbanik: "Re: rsync + ssh fail on raid; okay on 2.2.x"
Previous message: Eric Lammerts: "Re: Off-Topic: how do I trace a PID over double-forks?"
Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Tue Jan 23 2001 - 21:00:22 EST