<html> <head> <meta content="text/html; charset=UTF-8" http-equiv="Content-Type"> </head> <body text="#000000" bgcolor="#FFFFFF"> <div class="moz-cite-prefix">Hi Steven I'm glad to see you to discuss about rk29xx. On 2014年10月08日 06:26, Steven Newbury wrote: </div> <blockquote cite="mid:1412720776.2797.8.camel@snewbury.org.uk" type="cite"> <pre wrap="">I've just been discussing how this relates to rk29xx on #etnaviv. I looked through the patch and it's good to see it's not limited to supporting Mali GPUs. I see no reason this wouldn't be compatible with etna_viv for rk29xx (or future Rockchip designs with alternative GPUs) as long as the rest of the infrastructure to support rk29 is in place iommu (ARM SMMU?) driver, for example. </pre> </blockquote> Now the drm driver only test on rk3288, and future when we add compatible for rk29xx, we would consider to add a non-iommu path for it.<span style="color: rgb(51, 51, 51); font-family: arial; font-size: 18px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: 22px; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255); display: inline !important; float: none;"> <blockquote cite="mid:1412720776.2797.8.camel@snewbury.org.uk" type="cite"> <pre wrap=""> IMHO it's vital to keep a logical separation between the video display hardware and the graphics processor on SoCs. </pre> </blockquote> Sure, the graphics processor maybe change in different solutions, logical separation is that we try to keep. <blockquote cite="mid:1412720776.2797.8.camel@snewbury.org.uk" type="cite"> <pre wrap=""> </pre> </blockquote> Regards -Ｍark </body> </html>