public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: iSteve <isteve@rulez.cz>
To: Sergey Vlasov <vsu@altlinux.ru>,
	linux-kernel@vger.kernel.org,
	linux-usb-devel@lists.sourceforge.net
Subject: Re: broken modules.alias entries for some USB devices
Date: Thu, 21 Sep 2006 21:03:46 +0200	[thread overview]
Message-ID: <20060921210346.1a59666b@silver> (raw)
In-Reply-To: <20060921223035.c5fda02d.vsu@altlinux.ru>

On Thu, 21 Sep 2006 22:30:35 +0400
Sergey Vlasov <vsu@altlinux.ru> wrote:
> The problem is that the bcdDevice field is supposed to be BCD - i.e.,
> its hex representation should contain only decimal digits 0..9.
> Therefore a proper USB device cannot have bcdDevice == 0x030a.
> Apparently some ibmcam devices violate this and use the bcdDevice field
> as if it was binary.
> 
> The code in scripts/mod/file2alias.c assumes that the bcdDevice_lo and
> bcdDevice_hi field contain proper BCD data.  Seems that, thanks to buggy
> hardware, this assumption is incorrect, and the code needs to support
> any hex numbers there.

So the 'correct' alias for this device should be eg.:
usb:v0545p800Dd030Adc*dsc*dp*ic*isc*ip*
right?

Given this new info... what if _lo is 0x030a and _hi is 0x030f? How would the
alias look like? Or worse, what if _lo is 0x030a and _hi is 0x040a?

Would these be correct?
usb:v0545p800Dd030[A-F]dc*dsc*dp*ic*isc*ip*
usb:v0545p800Dd0[30A-40A]dc*dsc*dp*ic*isc*ip*

Thanks in advance.
-- 
 -- iSteve

      reply	other threads:[~2006-09-21 19:04 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-20 16:53 modules.isapnpmap vs modules.alias iSteve
2006-09-20 17:22 ` Randy.Dunlap
2006-09-21 14:54   ` modules.isapnpmap vs modules.alias (now: modules.usbmap vs alias) iSteve
2006-09-21 18:30     ` broken modules.alias entries for some USB devices Sergey Vlasov
2006-09-21 19:03       ` iSteve [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=20060921210346.1a59666b@silver \
    --to=isteve@rulez.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --cc=vsu@altlinux.ru \
    /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