On 28/07/15 02:31, Pavel Pisa wrote:
>I think it's much closer to what we expected. you may checkout my github
>and my dropbox. 
>https://github.com/yangqiao/rtems/tree/framebuffer
>https://www.dropbox.com/sh/95bu6skofkmrlvc/AABXjwvvFhQScJdo_rwj12V6a?dl=0
>
>The commits log is messy, I'll rebase it afterward until we think it's
>acceptable.
I think that Sebastian, Joel or some other core developer opinion
would be nice there.

I don't have time to check out external repositories. I will only look at information included in e-mails posted to the devel list.

I am not sure why you need additional sections in the MMU table for the frame buffer. In case it needs non-cachable memory, why don't you put it into the .bsp_nocache section? You can also use a heap for this section, see rtems_cache_coherent_allocate().

--
Sebastian Huber, embedded brains GmbH

Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone   : +49 89 189 47 41-16
Fax     : +49 89 189 47 41-09
E-Mail  : sebastian.hu...@embedded-brains.de
PGP     : Public key available on request.

Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.

_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel

Reply via email to