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 ^^ 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 _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
