Am 2008-02-05 14:27 + schrieb Daniel Drake:
> it is whitespace-corrupted and hence will not apply. You should also submit
ARGH! May be copy with vim/xterm caused this. Is this better?
Anything else should have created a clean patch *mumblegrumble*
> it directly to the usb-storage
Konstantin Kletschke wrote:
Am 2008-02-05 14:26 +0100 schrieb Xavier Bestel:
+UNUSUAL_DEV( 0x04b0, 0x0411, 0x0100, 0x0110,
Maybe you should leave them both here.
I suppose the device is checked against a range between
bcdDeviceMin -> bcdDeviceMax to take care of the possibility new
Am 2008-02-05 14:26 +0100 schrieb Xavier Bestel:
> > +UNUSUAL_DEV( 0x04b0, 0x0411, 0x0100, 0x0110,
> Maybe you should leave them both here.
I suppose the device is checked against a range between
bcdDeviceMin -> bcdDeviceMax to take care of the possibility new
revisions does not need the quirk
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:
>
> ---
Nikon did update their FW for the Nikon D80 and usb-storage got
unusable:
scsi 10:0:0:0: Direct-Access NIKOND80 1.10 PQ: 0 ANSI: 2
sd 10:0:0:0: [sdb] 3970049 512-byte hardware sectors (2033 MB)
sd 10:0:0:0: [sdb] Write Protect is off
sd 10:0:0:0: [sdb] Mode Sense: 0f 00 00
Nikon did update their FW for the Nikon D80 and usb-storage got
unusable:
scsi 10:0:0:0: Direct-Access NIKOND80 1.10 PQ: 0 ANSI: 2
sd 10:0:0:0: [sdb] 3970049 512-byte hardware sectors (2033 MB)
sd 10:0:0:0: [sdb] Write Protect is off
sd 10:0:0:0: [sdb] Mode Sense: 0f 00 00
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:
---
Am 2008-02-05 14:26 +0100 schrieb Xavier Bestel:
+UNUSUAL_DEV( 0x04b0, 0x0411, 0x0100, 0x0110,
Maybe you should leave them both here.
I suppose the device is checked against a range between
bcdDeviceMin - bcdDeviceMax to take care of the possibility new
revisions does not need the quirk
Konstantin Kletschke wrote:
Am 2008-02-05 14:26 +0100 schrieb Xavier Bestel:
+UNUSUAL_DEV( 0x04b0, 0x0411, 0x0100, 0x0110,
Maybe you should leave them both here.
I suppose the device is checked against a range between
bcdDeviceMin - bcdDeviceMax to take care of the possibility new
Am 2008-02-05 14:27 + schrieb Daniel Drake:
it is whitespace-corrupted and hence will not apply. You should also submit
ARGH! May be copypaste with vim/xterm caused this. Is this better?
Anything else should have created a clean patch *mumblegrumble*
it directly to the usb-storage
10 matches
Mail list logo
