From: Oliver Neukum <oliver@neukum.org>
To: "Pekka Enberg" <penberg@cs.helsinki.fi>
Cc: "Wilco Beekhuizen" <wilcobeekhuizen@gmail.com>,
"Greg KH" <greg@kroah.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Missing usb_find_device symbol from usb.c
Date: Thu, 24 Jan 2008 13:58:50 +0100 [thread overview]
Message-ID: <200801241358.51496.oliver@neukum.org> (raw)
In-Reply-To: <84144f020801240434s3ce63e58m8ffb74d70c0aef32@mail.gmail.com>
Am Donnerstag, 24. Januar 2008 13:34:00 schrieb Pekka Enberg:
> Hi Oliver,
>
> On Jan 24, 2008 2:24 PM, Oliver Neukum <oliver@neukum.org> wrote:
> > > Sure but the filesystems in fs/ are general purpose and they can be
> > > mounted on top of any block device (except for the in-memory ones like
> >
> > nfs, cifs, jffs, ...
>
> But none of them mess around with *hardware*. Sure, you can split it
> in two: driver and filesystem but yet again, the latter is not general
> purpose at all. I think this is somewhat similar to spufs which is
> really hardware specific and thus not eligible for fs/.
So we put it into drivers/usb/misc
Does that change the code?
> On Jan 24, 2008 2:24 PM, Oliver Neukum <oliver@neukum.org> wrote:
> > > sysfs). Furthermore, the problem with iriverfs is that it assumes that
> > > there can be only one device plugged to the host. What we want is
> > > something like
> > >
> > > $ mount -t iriverfs /dev/iriver0 /mnt/media
> > >
> > > Which can be accomplished with an USB driver in driver/usb/ that
> > > registers the special iriverfs.
> >
> > And what happens if you do
> > mount -t vfat /dev/iriver0 /mnt/media ?
>
> If /dev/iriver0 is registered as a block device, we read the
> superblock but don't find a vfat filesystem and the mount fails as
> expected. As for
>
> mount -t iriverfs /dev/sd1 /mnt/media
>
> we need to make sure file_system_type->get_sb() does something like
> what drivers/mtd/mtdsuper.c::get_sb_mtd() does to make sure we only
> let it mount if the block device is indeed an iriver player.
How do you make a block device on top of this device? It has no notion
of reading/writing arbitrary blocks. It operates on files.
Regards
Oliver
next prev parent reply other threads:[~2008-01-24 12:56 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-22 19:18 [PATCH] Missing usb_find_device symbol from usb.c Wilco Beekhuizen
2008-01-22 22:08 ` Adrian Bunk
2008-01-24 1:37 ` Greg KH
2008-01-24 10:05 ` Wilco Beekhuizen
2008-01-24 11:19 ` Pekka Enberg
2008-01-24 11:49 ` Oliver Neukum
2008-01-24 11:52 ` Pekka Enberg
2008-01-24 12:24 ` Oliver Neukum
2008-01-24 12:34 ` Pekka Enberg
2008-01-24 12:58 ` Oliver Neukum [this message]
2008-01-24 13:14 ` Pekka Enberg
2008-01-24 16:44 ` Greg KH
2008-01-24 17:06 ` Pekka Enberg
2008-01-24 17:20 ` Greg KH
2008-01-24 17:42 ` Pekka Enberg
2008-01-24 18:03 ` Greg KH
2008-01-24 19:25 ` Pekka J Enberg
2008-01-24 19:57 ` Oliver Neukum
2008-01-24 20:10 ` Pekka Enberg
2008-01-24 20:00 ` Oliver Neukum
2008-01-24 20:26 ` Pekka Enberg
2008-01-24 20:28 ` Greg KH
2008-01-25 8:58 ` Oliver Neukum
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=200801241358.51496.oliver@neukum.org \
--to=oliver@neukum.org \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=penberg@cs.helsinki.fi \
--cc=wilcobeekhuizen@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).