[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <4AFB086B.1020201@natemccallum.com>
Date: Wed, 11 Nov 2009 13:54:35 -0500
From: Nathaniel McCallum <nathaniel@...emccallum.com>
To: linux-kernel@...r.kernel.org
Subject: Re: [PATCH][RFC] Devices that ignore USB spec generate invalid modaliases
On 11/11/2009 03:39 AM, Nathaniel McCallum wrote:
> On 11/11/2009 03:20 AM, Nathaniel McCallum wrote:
>> Drivers for devices which have bcdDevice conforming to BCD will have no
>> change in modalias output.
>
> One small clarification. Existing drivers which specify a non-zero lower
> bound and an upper bound past the next character will have their upper
> bound changed from 0x9 to 0xf (i.e.: d123[4-9] -> d123[4-9a-f]). I
> believe this is the only case where an existing (working) modalias will
> change.
I've solved the above problem in the latest patch
(file2alias_hex_or_bcd.patch) which automatically detects if a driver
entry is supporting a hex bcdDevice rather than a bcd one and adjusts
accordingly. Thus, for all normal devices, there is now no change at all.
In the process I discovered another bug. 'devlo++' and 'devhi--' are
used. However this number is most often in BCD format, so ++/-- won't
work. A second patch (file2alias_bcd_increment.patch) resolves this issue.
Again, questions/comments welcome.
Nathaniel McCallum
View attachment "file2alias_bcd_increment.patch" of type "text/plain" (1800 bytes)
View attachment "file2alias_hex_or_bcd.patch" of type "text/plain" (3251 bytes)
Powered by blists - more mailing lists