Kay Sievers wrote:
quoted text
> Not sure if I understand that correctly. Remember, that there is a
> symlink "subsystem" at each device, and udev, HAL, DeviceKit reads it.
> If the uevent environment key "SUBSYSTEM" does not match the symlink
> target, things will break horribly. So no device can be a member of
> class "cuse" but carry a SUBSYSTEM value of a different class.
>
> If that is how it works, I guess that must be solved differently, by
> hooking into the subsystem code and create "virtual devices" at the
> original class they fake, instead of their own "cuse" class. Possibly
> by making cuse a "bus", and use the cuse device as a parent for the
> "real" class device.

For OSS emulation, it didn't really matter.  For cases where it matters,
I think easier path to take would be let the userland emulation set up a
directory containing pseudo files and just override DEVPATH to it.
Would that work?

Thanks.

-- 
tejun
--
unsubscribe notice
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/