Messages in this thread | | | Date | Wed, 24 Mar 2010 09:26:16 -0700 | From | Greg KH <> | Subject | Re: [PATCH 4/6] drivers:misc: sources for Init manager module |
| |
On Wed, Mar 24, 2010 at 09:11:45AM -0700, Marcel Holtmann wrote: > > I wanted to somehow put this in staging because then it would probably have a thorough architectural review process. > > Some details about this driver - > > > > 1. This driver will be used by Bluetooth-BlueZ/FM-V4L2 and GPS (probably character device driver) using the EXPORTED symbols (-register/_unregister). > > > > 2. Much like the hciattach daemon which maintains N_HCI bluetooth line discipline, this driver will also have a User-Space N_TI_WL Init manager (UIM) maintaining the Line discipline. > > can you explain why you think this is needed and we can not interface > this directly. If it is a serial port, what protocol does it talk? > > > 3. Because of the UIM should know when to install/uninstall line discipline, the /sys entry is created a root called UIM (a new kobject) and UIM daemon would write it's PID to it. > > I don't understand this. This sounds like a broken concept to me.
I also agree, those sysfs files are not acceptable, and will not work as-designed due to the pid namespace issues :(
thanks,
greg k-h
| |