2010/12/1 <[email protected]>: > Hi, > >>-----Original Message----- >>From: Carsten Munk >>Sent: 01 December, 2010 12:02 >> >>Hi, >> >>We have http://bugs.meego.com/show_bug.cgi?id=4049 which is about how >>to deal with a USB cable being plugged in. > > Maybe a silly question but how there can be a bug (by a system > tester?) if there's no FEA that requests some functionality?
I wonder this occasionally too but I guess there's value in what the casual tester notices as lacking in a system as that'd indicate directions/new features we should implement. > >>Can someone elaborate on the intended technical behaviour on USB cable >>being plugged in and what technical components will handle it? >> >>FEA http://bugs.meego.com/show_bug.cgi?id=5770 exists but it's 'WAITING' > > Technical behavior in brief is: > - signal USB connection status > - pop-up selection UI > - based on UI input select desired mode and > * load proper g_* > * set up device nodes, (mount/unmount fs,) and start needed daemons > - signal selected mode or error > > systemui code has usbui.cpp (for UI selection dialog) but the rest is > missing (especially the daemon that does all the work). I'm wondering if this would be policy daemon, mce or a third thing handling part of this. And what parts would be hardware adaptation specific. I guess a flowchart and pieces needed would be good, but since the feature isn't accepted for 1.2 (so far), maybe it's too early to think about. BR Carsten Munk _______________________________________________ MeeGo-handset mailing list [email protected] http://lists.meego.com/listinfo/meego-handset
