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] [day] [month] [year] [list]
Date:	Tue, 3 Jul 2007 17:12:34 -0400 (EDT)
From:	Alan Stern <stern@...land.harvard.edu>
To:	S.Çağlar Onur <caglar@...dus.org.tr>
cc:	Oliver Neukum <oliver@...kum.org>, "Ni@m" <niam.niam@...il.com>,
	<linux-usb-devel@...ts.sourceforge.net>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [linux-usb-devel] [PATCH] for NIKON D50 as UMS

On Wed, 4 Jul 2007, [utf-8] S.Çağlar Onur wrote:

> Hi,
> 
> 03 Tem 2007 Sal tarihinde, Oliver Neukum şunları yazmıştı: 
> > Am Dienstag, 3. Juli 2007 schrieb S.Çağlar Onur:
> > > Hmm i have NIKON D50 also and it works here without a problem with
> > > Linus's current git.
> >
> > Please provide the full lsusb -v for your devices, both of you.
> > You might have different versions of the device.
> 
> Here it is;
> 
> 
> Bus 005 Device 007: ID 04b0:0409 Nikon Corp. 
> Device Descriptor:
>   bLength                18
>   bDescriptorType         1
>   bcdUSB               2.00
>   bDeviceClass            0 (Defined at Interface level)
>   bDeviceSubClass         0 
>   bDeviceProtocol         0 
>   bMaxPacketSize0        64
>   idVendor           0x04b0 Nikon Corp.
>   idProduct          0x0409 
>   bcdDevice            1.00

The descriptors are the same.  But that doesn't mean anything.  It's 
possible that one device has a problem and the other doesn't because 
one computer tries to read the last sector and the other computer 
doesn't.  Or perhaps the two cameras have different capacities.

Alan Stern

-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ