On Tue, May 3, 2016 at 9:58 AM, <[email protected]> wrote:

> Hello all,
>
> I've noticed some bad HDMI jitter/flickering when using the -bone kernel,
> which is present both in 3.14 and latest 4.1. However this flickering is
> not present when using the -ti kernel, regardless of the version; the -ti
> version is used by default in rcn's netinstall script. Unfortunately,
> building sgx modules fails with the -ti kernel ("error: implicit
> declaration of function fb2display") but works fine, using the same SDK,
> when using -bone kernel as compiled with rcn's bb-kernel repo (branch
> am33x-3.14).
>

"flickering" should be gone in am33x-4.4+ as tilcdc patches went mainline a
couple months back and i back ported it..


>
> Therefore I'm wondering what is ultimately the difference between those
> two (isn't it a waste of effort to maintain two separate kernels?), and if
> any of you had a solution for this build issue. Hopefully I'd like to use
> the kernel with the least bugs, which seems to be -ti so far regarding
> HDMI. Nonetheless I'd like to thank Robert C. Nelson for his work and in
> particular the very useful netinstall/bb-kernel repos.
>

It's only a mess right now, as we have a couple transitions in flight..

uio_pruss -> remoteproc_pruss
old_sgx_drivers -> new_sgx_drivers

A lot of users, use uio_pruss and the old_sgx_drivers, thus they are
currently stuck in the "bone" kernel's..

at some point, remoteproc_pruss will fulfill uio_pruss users needs (and
also go mainline), thus solving that problem..

sgx = no comment...

Regards,

-- 
Robert Nelson
https://rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/CAOCHtYgg8RvZUpMJp-0q8oFau5ffYyypY3YogNdU65ek0MGNvA%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to