From: "Ian E. Morgan" <penguin.wrangler@gmail.com>
To: "Greg KH" <greg@kroah.com>
Cc: "Linux Kernel Mailing List" <linux-kernel@vger.kernel.org>
Subject: Re: sysfs: duplicate filename (usb unusual dev?)
Date: Thu, 15 May 2008 09:53:08 -0400 [thread overview]
Message-ID: <2a6e8c0d0805150653j394ec325jf45dd000c86bea8d@mail.gmail.com> (raw)
In-Reply-To: <20080515050925.GA8133@kroah.com>
On Thu, May 15, 2008 at 1:09 AM, Greg KH <greg@kroah.com> wrote:
> On Mon, May 12, 2008 at 11:10:11AM -0400, Ian E. Morgan wrote:
>> My wife got a silly little keychain digital photo frame for a gift.
>> I'm trying to make it work, but no such luck:
>>
>> (This is on vanilla 2.6.25)
>
> These warning messages should be safely ignored (it's odd that I can't
> duplicate this, perhaps it's a CONFIG_SYSFS_DEPRECATED thing...)
>
>> So I don't get the reason for duplicate sysfs nodes, and the scsi
>> device for mass storage never shows up (no /dev/sdb is registered,
>> etc)
>
> Are you sure sd_mod is loaded?
>
> thanks,
>
> greg k-h
>
Yeah, turns out the device really is a piece of CR*P like I figured. I
had to add this to get it to work:
UNUSUAL_DEV( 0x1908, 0x1315, 0x0000, 0x0000,
"BUILDWIN",
"Photo Frame",
US_SC_DEVICE, US_PR_DEVICE, NULL,
US_FL_GO_SLOW ),
after which the device showed up as a removable media device with an
iso9660 fs! Sheesh! And this fs of course just contained some utter
garbage software for Windows to upload pictures onto the device using
a proprietary HID interface. Can you say "what were they thinking?!"
Having given up at this point, I plugged it into a windows box, and
the thing basically gave windows a conniption fit. Yeah, I think I'll
be throwing it out now. What do you expect for a $9.95 trinket from
China? Sorry for wasting everyone's time.
--
Ian Morgan
prev parent reply other threads:[~2008-05-15 13:53 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-12 15:10 Ian E. Morgan
2008-05-15 5:09 ` Greg KH
2008-05-15 13:53 ` Ian E. Morgan [this message]
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=2a6e8c0d0805150653j394ec325jf45dd000c86bea8d@mail.gmail.com \
--to=penguin.wrangler@gmail.com \
--cc=greg@kroah.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®