linux-kernel - Re: [Patch 1/1] Nikon D80 usb-storage quirk needs modified, new FW

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <1202218008.23816.9.camel@skunk.anacadf.mentorg.com>
Date:	Tue, 05 Feb 2008 14:26:48 +0100
From:	Xavier Bestel <xavier.bestel@...e.fr>
To:	Konstantin Kletschke <lists@...gbr.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: [Patch 1/1] Nikon D80 usb-storage quirk needs modified, new FW

On Tue, 2008-02-05 at 13:43 +0100, Konstantin Kletschke wrote:
> Nikon did update their FW for the Nikon D80 and usb-storage got
> unusable:
[...]
> I relized the unusal_devs.h needs to be adapted to 
> reflect new FW Version, then it works fine again:
> 
> --- linux-2.6.23/drivers/usb/storage/unusual_devs.h_orig        2008-02-05 13:33:55.010623616 +0100
> +++ linux-2.6.23/drivers/usb/storage/unusual_devs.h     2008-02-05 13:32:22.926623601 +0100
> @@ -342,7 +342,7 @@
>                 US_FL_FIX_CAPACITY),
> 
>  /* Reported by Emil Larsson <emil@...p.net> */
> -UNUSUAL_DEV(  0x04b0, 0x0411, 0x0100, 0x0101,
> +UNUSUAL_DEV(  0x04b0, 0x0411, 0x0100, 0x0110,
>                 "NIKON",
>                 "NIKON DSC D80",
>                 US_SC_DEVICE, US_PR_DEVICE, NULL,
> 
> 
> What I wonder is, why are there other examples only reflecting the
> newest Firmware, are older ones also catched?

Maybe you should leave them both here.

	Xav


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/