From: Greg KH <greg@kroah.com>
To: Nathaniel McCallum <nathaniel@natemccallum.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Devices that ignore USB spec generate invalid modaliases
Date: Thu, 12 Nov 2009 15:42:55 -0800 [thread overview]
Message-ID: <20091112234255.GA23889@kroah.com> (raw)
In-Reply-To: <4AFA73C7.4070002@natemccallum.com>
On Wed, Nov 11, 2009 at 03:20:23AM -0500, Nathaniel McCallum wrote:
> Please CC me as I'm not subscribed to LKML.
>
> The current code to generate usb modaliases from usb_device_id assumes
> that the device's bcdDevice descriptor will actually be in BCD format.
> While this should be a sane assumption, some devices don't follow spec
> and just use plain old hex. This causes drivers for these devices to
> generate invalid modalias lines which will never actually match for the
> hardware.
>
> The following patch adds hex support for bcdDevice in file2alias.c.
> Drivers for devices which have bcdDevice conforming to BCD will have no
> change in modalias output. Drivers for devices which don't conform
> (primarily usb-storage and ibmcam in my initial survey) should now
> generate valid modaliases.
>
> EXAMPLE OUTPUT (ibmcam; space added to highlight change)
> Old: usb:v0545p800D d030[10-9] dc*dsc*dp*ic*isc*ip*
> New: usb:v0545p800D d030a dc*dsc*dp*ic*isc*ip*
Huh? The old one had '[]' in it?
What does the bcdDevice for this really look like in the device itself?
If it is messed up in the descriptor, then how can we know to fix it up
here?
And you might want to cc: linux-usb@vger.kernel.org with this as well,
as that's where the USB developers are.
thanks,
greg k-h
next prev parent reply other threads:[~2009-11-12 23:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-11 8:20 [PATCH] Devices that ignore USB spec generate invalid modaliases Nathaniel McCallum
2009-11-11 8:39 ` Nathaniel McCallum
2009-11-11 18:54 ` [PATCH][RFC] " Nathaniel McCallum
2009-11-12 23:42 ` Greg KH [this message]
2009-11-13 1:09 ` [PATCH] " Nathaniel McCallum
2009-11-13 14:51 ` Nathaniel McCallum
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=20091112234255.GA23889@kroah.com \
--to=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nathaniel@natemccallum.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox