On Tue, 2013-04-16 at 12:16 +0800, Andy Green wrote:
On 16/04/13 10:08, the mail apparently from Selina Kuo included:
Hi, John,
Your assumption is right. The ump code is part of the out-of-tree mali driver.
- Selina Kuo, one of Andy's colleagues ^^
As Selina says it's a code drop we got via Fujitsu from ARM for the OOT Mali driver.
However that code is all GPL2, as it should be.
I assume it's not for as yet unreleased IP and under NDA or anything. (Just thought I would throw that in there.)
I think any of the options are good,
make our own repo and keep it in sync with llct
privately encourage ARM to keep it in sync with Linus' HEAD, publicly
upstream it so it's always in sync
This obviously helps of all LT who want to / can harmonize their tree on llct basis.
Tushar, do you have any opinion?
Anyone who dealt with this code or at ARM (Tixy?)
I've never dealt with this code but one thing occurs to me: how would you manage the user side binary blob? If different members have different versions of the blobs (or have tweaked them) are they all going to work with a common version of the kernel driver or have different members tweaked things for there own needs?