Many thanks Ismo for the prompt response, Some further commentary if I may....
> -----Original Message----- > From: Puustinen, Ismo > Sent: Tuesday, April 01, 2014 1:03 PM > To: Counihan, Tom > Cc: [email protected] > Subject: Re: Understanding AMB dependencies on Murphy > > Hello Tom, > > > While groking AMB, I happened across the murphyplugin. > > Therein, I see some indication of traffic from murphy to AMB; > > "Received a message from Murphy" > > "recvfrom_msg(mrp_transport_t *transp, mrp_msg_t *msg ....." > > > > Am I correct in assuming this presents a dependency AMB has on Murphy? > > Can someone help me understand what events Murphy fires to AMB? > > Murphy uses basic information from AMB (such as speed, transmission, > exterior brightness, ...) to be able to do decisions about the vehicle state. > These > decisions are then used for policing, such as regulating on-screen > applications if > the vehicle is moving. This piece I understood - it makes sense to me, as a policy engine you require input to drive policy rules... >The processed states are then communicated back to > AMB so that other applications can use the same information. At the moment > Murphy controls "DrivingMode" and "NightMode" AMB properties. The control To better understand this - can you elaborate on what influences these properties in Murphy? By that I mean what trigger events push each of these properties into their various states? > interface is the Murphy plugin that you have found from the AMB source code. > > So, to recap: from Murphy's point of view AMB is a source of system events and > a place for propagating policy decisions to applications and other interested > parties in the system. From AMB's point of view Murphy is a client for > property > changes and a provider of higher-level vehicle states. Can you elaborate on the boot sequence order here? Will AMB be fully functional before Murphy awakes? An example - if I park my vehicle last night (NightMode = true), and I return in the morning at day-break, does Murphy need to be up and running, observe the correct Nightmode value, pass it to AMB, which then raises the state change for the HMI to correctly adjust the user backlighting experience ] Finally - could you explain the concurrency model in AMB - I'd like to understand the threading model better, specifically around having multiple clients delivering inbound events at various frequencies, normalising these to a standard interface and then potentially delivering these to various consumers... > > -- > Ismo Puustinen <[email protected]> -------------------------------------------------------------- Intel Shannon Limited Registered in Ireland Registered Office: Collinstown Industrial Park, Leixlip, County Kildare Registered Number: 308263 Business address: Dromore House, East Park, Shannon, Co. Clare This e-mail and any attachments may contain confidential material for the sole use of the intended recipient(s). Any review or distribution by others is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies. _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
