Re: [Xen-devel] [Embedded-pv-devel] [PATCH RFC 00/18] System adjustment to customer needs.

[Andrii Anisov <andrii.anisov@xxxxxxxxxxxxxxx>]

All,

See the system details I can reveal below:

• There are two OS in the system Linux(Dom0) and Android(DomU)
• Android provides almost all infotainment functionality. Linux covers functionality with higher reliability requirements and backup in case if Android crashes/glitches.
• Linux (Dom0) handles all HW except GPU.
• Android (DomD) runs with number of PV drivers, has an exclusive access to GPU.
• The system has 2Gb(-16MB due to errata) RAM under 4GB, and a memory bank mapped over 4GB
• Due to relatively small amount of dma-able memory both domains should have assigned RAM both from under 4GB and over 4GB spaces.
• Several "data flow" mixing scenarios should be provided on Linux side I.e. controlling Android audio level, Android audio mute, mixing Android audio stream from stream generated by Linux. Same for Android displaying, events passing.
• Domains should share HW codecs. 

>> Similarly, what are the limitations for the Jacinto6 SoC that need to
>> be workaround?

The main limitation is that Jacinto6 lacks of SMMU. All transaction initiators can address 32bit only, some initiators have no MMU and do not support sg-lists (require buffers continuous in maddr).

Andrii Anisov | Associate Manager, Engineering
GlobalLogic
Kyiv, 03038, Protasov Business Park, M.Grinchenka, 2/1
P +38.044.492.9695x3664  M +380505738852  S andriyanisov
www.globallogic.com

http://www.globallogic.com/email_disclaimer.txt


On Thu, May 19, 2016 at 2:00 PM, Julien Grall <julien.grall@xxxxxxx> wrote:
> Hello,
>
> On 18/05/16 20:17, Meng Xu wrote:
>>
>> On Wed, May 18, 2016 at 12:32 PM, Andrii Anisov
>> <andrii.anisov@xxxxxxxxxxxxxxx> wrote:
>>>
>>> This series RFC patches from the currently ongoing production project.
>>> This patch series presents changes needed to fit the system into
>>> customer requirements as well as workaround limitations of the
>>> Jacinto6 SoC.
>>
>>
>> IMHO, it will be better, if possible, to describe the exact customer
>> requirements this patch series tries to satisfy. I'm curious at what
>> the requirements are and if the requirements are general enough for
>> many other customers. :-)
>
>
> I agree with Meng here. We need to understand the use case and see if it is
> possible to generalize it for everyone.
>
> I looked quickly at this patch series and noticed that most of patches miss
> details on why it is necessary and what you are trying solve. Can you give
> us more details?
>
>> Similarly, what are the limitations for the Jacinto6 SoC that need to
>> be workaround? If the board is not supported by Xen, can we say Xen
>> will support the board with the warkaround?
>
>
> Regards,
>
> --
> Julien Grall

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel