On 04/16/2013 09:46 AM, 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 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? >
It would always help to have the Mali driver synced with latest upstream and getting merged into 'llct'. The LT's who need to use this driver can have their modifications (if any) on top of it. > Anyone who dealt with this code or at ARM (Tixy?) > > FWIW our TSC rep is aware of this and I believe would support whatever > the best-looking of these solutions is. > > -Andy > >> On 16 April 2013 07:50, John Stultz <john.stu...@linaro.org> wrote: >>> On 04/13/2013 03:22 AM, Andy Green wrote: >>>> >>>> On 13/04/13 09:07, the mail apparently from Andy Green included: >>>> >>>>> I'm hoping someone else will write the patches ^^ but if not I'll try >>>>> to sort something out. >>>> >>>> >>>> The attached series gets it building cleanly against current llct with >>>> ION. >>> >>> >>> Cool. Although the patches look like they are all against the ump >>> driver(which I'm not familiar with), as opposed to changes to the ION >>> infrastructure itself. So they won't apply to the AOSP trees, and I >>> can't >>> send them upstream. >>> >>> I assume the ump code is part of the out-of-tree mali driver? Looking at >>> llct, I don't see a drivers/base/ump directory. >>> >>> https://git.linaro.org/gitweb?p=kernel/linux-linaro-tracking.git;a=tree;f=drivers/base;h=cbad2d664fa248ec366430dbd1724b2959ae43ee;hb=refs/heads/linux-linaro-core-tracking >>> >>> >>> But I'm guessing this is the point of your original mail in this >>> thread: we >>> need a mali tree upon which fixes like these can be applied and then >>> pulled >>> into llct. >>> >>> Or even better, can we get the mali devs to publish a repo of their >>> latest >>> work (to which fixes like Andy's can be submitted to) which can also be >>> pulled into llct? >>> >>> thanks >>> -john >>> >>> >>> >>> _______________________________________________ >>> linaro-dev mailing list >>> linaro-dev@lists.linaro.org >>> http://lists.linaro.org/mailman/listinfo/linaro-dev > > -- Tushar Behera _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
