On Wed, May 2, 2012 at 10:05 AM, Martin Langhoff <martin.langh...@gmail.com> wrote: > Yep. In genral, a modprobe/udevtrigger/waitforpath approach seems to work. > > I am a bit annoyed that systemd/udev doesn't provide some useful > facilities for this. We are early users, and as such we hit all the > early issues. Not sure how to put it to upstream.
I think they would just point out that the solution we're working towards is the wrong approach. That is, we're requiring the hardware to be connected at boot for it to be used. If you connect it after boot, nothing happens. That may be what we had working before, but its not great. Everything is moving to be hotpluggable. And how can we make this hotpluggable? This is probably the right question to ask upstream. I suspect the answer will involve the multi-seat support which has improved enormously in recent months. Daniel _______________________________________________ Devel mailing list Devel@lists.laptop.org http://lists.laptop.org/listinfo/devel
