Re: [Ifp-driver-common] Is iFP a block device?

[Dan K. <da...@at...>]

On Mon, 2004-11-01 at 12:36 -0500, Geoff Oakham wrote:

> A couple of points of clarification: libifp is a general-purpose
> hardware-abstraction library that works both as a shared library and as
> a kernel module: iriverfs allready uses libifp to communicate with
> devices.
Hmm, where to get that iriverfs driver. The one I have just reimplements
all features.

> I don't know what gnome-volume-manager is, but I'm guessing it's a gui
> for mount, hotplug and friends.
gnome-volume-manager listens messages from HAL (hardware abstraction
layer) and if it gets message that new volume is accesible to mount, it
mounts it.

> And I'm guessing you can't get it working with iriverfs because it doesn't need
> a block device and/or block devices don't automatically appear in devfs when they're plugged
> in.  is that right?  IMHO this seems to be a limitation of gnome-volume-manager, not iriverfs.
Yup, GVM assumes that all storage devices is a block devices. But I
guess it's right to register a storage block device for a mountable
audio player that can be also used as a simple removable storage device.
Users (or some automation programs) are used to do something like
"mount /dev/sda1 /media/usbdisk" when they plug in a storage device.

> Note that iriverfs doesn't yet support multiple ifp devices.  When it
> does, your problem might go away on its own.. I've been considering
> using files in /proc/bus/usb/* or dummy block devices as the mount
> device.
The good start is to create a block devices for just one device also. :)

> If this looks simple to or you have a simple work-around, then by all
> means send me a patch.. I'd be happy to apply it.
I started learning linux module programming interface just yesterday, so
don't expect much code from me yet.

-- 
Dan Korostelev <da...@at...>