From: Arnaldo Carvalho de Melo <acme@conectiva.com.br>
To: Alastair Foster <alasta@mail.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Camera as a USB mass storage / SCSI device
Date: Sun, 31 Dec 2000 16:46:34 -0200 [thread overview]
Message-ID: <20001231164634.F818@conectiva.com.br> (raw)
In-Reply-To: <379744379.978294325610.JavaMail.root@web582-mc>
In-Reply-To: <379744379.978294325610.JavaMail.root@web582-mc>; from alasta@mail.com on Sun, Dec 31, 2000 at 03:25:25PM -0500
Em Sun, Dec 31, 2000 at 03:25:25PM -0500, Alastair Foster escreveu:
> USB support appears to be coming along nicely. I have just aquired an Agfa
> ePhoto digital camera. I have heard several success stories of people who
> have compiled kernels with SCSI and USB mass storage support and been able
> to emulate their camera's flash memory as a SCSI disk on bootup. Accessing
> the camera was then simply a matter of mounting the SCSI device.
>
> Unfortunately, my camera does not get recognised on bootup. This is hardly
> surprising, given that the kernel has no way of determining the camera as a
> USB mass storage device. However, I'm curious as to how others have managed
> to get away with this by doing nothing more than compiling their kernel with
> the above options. Is there some sort of database which tells the kernel to
> associate a particular USB product ID and vendor with a particular driver?
> If so, is there any way to edit this database?
/usr/src/linux/drivers/usb/storage/usb.c, look for:
/* This is the list of devices we recognize, along with their flag data */
/* The vendor name should be kept at eight characters or less, and
* the product name should be kept at 16 characters or less. If a device
* has the US_FL_DUMMY_INQUIRY flag, then the vendor and product names
* normally generated by a device thorugh the INQUIRY response will be
* taken from this list, and this is the reason for the above size
* restriction. However, if the flag is not present, then you
* are free to use as many characters as you like.
*/
static struct us_unusual_dev us_unusual_dev_list[] = {
{ 0x03ee, 0x0000, 0x0000, 0x0245,
"Mitsumi",
"CD-R/RW Drive",
US_SC_8020, US_PR_CBI, NULL, 0},
<SNIP>
- Arnaldo
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-31 21:06 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-31 20:25 Alastair Foster
2000-12-31 18:46 ` Arnaldo Carvalho de Melo [this message]
2000-12-31 21:41 ` Matthew Dharm
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=20001231164634.F818@conectiva.com.br \
--to=acme@conectiva.com.br \
--cc=alasta@mail.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®