Hello Jussi > On Sep 18, 2014, at 11:03, Jussi Laako <[email protected]> wrote: > > Hi, > > We have now a working architecture and proof-of-concept setup for > simultaneous multi-user multi-seat configuration with VTC-1010: > 1xGPU > 2xDisplay (DP + VGA) > 2xKeyboard > 2xMice > 1xTouch-screen > > I believe this architecture can also work well with GENIVI and real-time > dashboard functionalities.
Sounds like it. > > Goal of the architecture in short is to have two simultaneous user > sessions, having their own displays and input methods (keyboard, mouse > and touch). We have now proven that this also works in practice. Makes sense - I think you will figure out more usability aspects by trying it in practice. > > Architecture description and other related information can be found from: > https://wiki.tizen.org/wiki/Multi-seat_Architecture > > Current user "display" is to be renamed something more generic, we've > been thinking about "system", but we'd like to hear about better > proposals. (this would also possibly be the GENIVI user/session) Yes I would say display is still better than system. You are here dealing with the scenario of one single system (more precisely one ECU) driving multiple displays / input peripherals. Often people will say system when they mean ECU. And if that's not what they mean, they mean several interconnected ECU make up a system, like the car electrical system. The term "Seat” is used in GENIVI and if you like it you could adopt it. Of course in the real world persons sitting in actual car seats could share a display, but we think of it as a more abstract concept when dealing with the software system. Seat number (0,1,2,3...) in GENIVI terms simply indicates any physical location where a display (+ input) exists. In current GENIVI proposal a user login is associated with a Seat and we presume the person will not move very much. If they do, a new session at their new location would be needed. Tizen currently seems to allow the session to be independent of physical location since you can move one user application from one display to another (as of now, in this case where multiple displays are driven by a single computer). But I would guess there is still need for some way of knowing where a logged in user would prefer their apps to appear. Similarly, you need to associate input peripherals with the person operating them. It won't be like a desktop system where you point your mouse to a window and the input goes there. HTH. - Gunnar > > Document is to be further updated with relevant sections on > Bluetooth/WiFi and other needed areas. > > > Comments are more than welcome! :) > > > Best regards, > > - Jussi Laako > -- Gunnar Andersson Lead Architect, GENIVI Alliance Infotainment, Volvo Car Corporation _______________________________________________ IVI mailing list [email protected] https://lists.tizen.org/listinfo/ivi
