From: "S.Çağlar Onur" <caglar@pardus.org.tr>
To: "Ni@m" <niam.niam@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] for NIKON D50 as UMS
Date: Tue, 3 Jul 2007 23:10:32 +0300 [thread overview]
Message-ID: <200707032310.33106.caglar@pardus.org.tr> (raw)
In-Reply-To: <a9e22dff0707031303i30c08439t3cc48fb1b95f29b8@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3317 bytes --]
Hi;
03 Tem 2007 Sal tarihinde, Ni@m şunları yazmıştı:
> This short patch allows NIKON D50 to be mounted as UMS on 2.6.22-rc7,
> some previous kernels...
>
>
> --- linux-2.6.22-rc7/drivers/usb/storage/unusual_devs.h 2007-07-03
> 22:54:23.000000000 +0300
> +++ linux-2.6.22-rc7-niam/drivers/usb/storage/unusual_devs.h
> 2007-07-03 22:35:39.000000000 +0300
> @@ -313,6 +313,13 @@
> US_SC_DEVICE, US_PR_DEVICE,NULL,
> US_FL_NOT_LOCKABLE ),
>
> +/* Reported by Niam <niam.niam@gmail.com> */
> +UNUSUAL_DEV( 0x04b0, 0x0409, 0x0100, 0x0100,
> + "NIKON",
> + "NIKON DSC D50",
> + US_SC_DEVICE, US_PR_DEVICE, NULL,
> + US_FL_FIX_CAPACITY),
> +
> /* Reported by Andreas Bockhold <andreas@bockionline.de> */
> UNUSUAL_DEV( 0x04b0, 0x0405, 0x0100, 0x0100,
> "NIKON",
Hmm i have NIKON D50 also and it works here without a problem with Linus's
current git.
...
caglar@zangetsu ~ $ mount
/dev/sda3 on / type ext3 (rw,noatime,user_xattr)
proc on /proc type proc (rw,noexec,nosuid)
sysfs on /sys type sysfs (rw)
usbfs on /proc/bus/usb type usbfs (rw)
tmpfs on /dev/shm type tmpfs (rw,noexec,nosuid,nodev)
securityfs on /sys/kernel/security type securityfs (rw)
/dev/sdc1 on /media/sdc1 type vfat
(rw,nosuid,nodev,noatime,uhelper=hal,flush,uid=1000,utf8,shortname=mixed)
caglar@zangetsu ~ $ uname -a
Linux zangetsu 2.6.22-rc7-CFS-v18 #32 SMP Tue Jul 3 09:29:55 EEST 2007 i686
Intel(R) Core(TM)2 CPU T5600 @ 1.83GHz GNU/Linux
[ 43.040002] ipw3945: Detected geography ABG (13 802.11bg channels, 23
802.11a channels)
[ 46.140489] APIC error on CPU1: 00(40)
[ 46.140492] APIC error on CPU0: 00(40)
[ 134.156403] NET: Registered protocol family 17
[ 153.610600] FAT: utf8 is not a recommended IO charset for FAT filesystems,
filesystem will be case sensitive!
[ 5376.491701] usb 5-1: new high speed USB device using ehci_hcd and address 6
[ 5376.607589] usb 5-1: configuration #1 chosen from 1 choice
[ 5376.607970] scsi7 : SCSI emulation for USB Mass Storage devices
[ 5376.608453] usb-storage: device found at 6
[ 5376.608472] usb-storage: waiting for device to settle before scanning
[ 5381.601547] scsi 7:0:0:0: Direct-Access NIKON D50 1.00
PQ: 0 ANSI: 2
[ 5381.602885] sd 7:0:0:0: [sdc] 2012161 512-byte hardware sectors (1030 MB)
[ 5381.603383] sd 7:0:0:0: [sdc] Write Protect is off
[ 5381.603390] sd 7:0:0:0: [sdc] Mode Sense: 0f 00 00 00
[ 5381.603394] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 5381.605133] sd 7:0:0:0: [sdc] 2012161 512-byte hardware sectors (1030 MB)
[ 5381.605617] sd 7:0:0:0: [sdc] Write Protect is off
[ 5381.605624] sd 7:0:0:0: [sdc] Mode Sense: 0f 00 00 00
[ 5381.605628] sd 7:0:0:0: [sdc] Assuming drive cache: write through
[ 5381.605633] sdc: sdc1
[ 5381.610048] sd 7:0:0:0: [sdc] Attached SCSI removable disk
[ 5381.610951] usb-storage: device scan complete
[ 5385.190375] FAT: utf8 is not a recommended IO charset for FAT filesystems,
filesystem will be case sensitive!
...
Cheers
--
S.Çağlar Onur <caglar@pardus.org.tr>
http://cekirdek.pardus.org.tr/~caglar/
Linux is like living in a teepee. No Windows, no Gates and an Apache in house!
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-03 20:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 20:03 [PATCH] for NIKON D50 as UMS Ni@m
2007-07-03 20:10 ` S.Çağlar Onur [this message]
2007-07-03 20:16 ` Randy Dunlap
2007-07-03 20:54 ` Oliver Neukum
2007-07-03 21:02 ` S.Çağlar Onur
2007-07-03 21:12 ` [linux-usb-devel] " Alan Stern
[not found] ` <a9e22dff0707031341o199032ejb6fe4b4ecde4af61@mail.gmail.com>
2007-07-03 21:45 ` Ni@m
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=200707032310.33106.caglar@pardus.org.tr \
--to=caglar@pardus.org.tr \
--cc=linux-kernel@vger.kernel.org \
--cc=niam.niam@gmail.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.