On 14 May 2012 13:40, Tushar Behera <tushar.beh...@linaro.org> wrote: > On 05/12/2012 11:09 PM, Andrey Konovalov wrote: >> Tushar, >> >> On 05/11/2012 09:04 AM, Tushar Behera wrote: >>> On 05/11/2012 01:04 AM, Andrey Konovalov wrote: >>>> Greetings, >>>> >>>> So far I wasn't updating the linux-linaro tree since the 12.04 release. >>>> (The generic topic updates were being done to the >>>> linux-linaro-core-tracking tree) >>>> >>>> Now it is time to move the focus to the linux-linaro tree. For one week >>>> it will use the mainline tip as the base. Then, on next Thursday the >>>> most recent -rc will be selected as the base, and won't be changed until >>>> 12.05 is released. Most probably it will be v3.4-rc7. >>>> >>>> The 12.05 linux-linaro tree will get the ARM and Samsung LTs topics plus >>>> the 7 generic topics currently included into the >>>> linux-linaro-core-tracking tree: >>>> ufs (ufs-for-linux-linaro) >>>> emmc (emmc-for-linux-linaro) >>>> thermal_exynos4_imx6 (thermal_exynos4_imx6_work) >>>> linaro-android-3.4 >>>> armlt-gator (tracking-armlt-gator) >>>> umm-wip (umm-3.4rc4-wip) >>>> linaro-configs-3.4 >>>> If you don't see your generic topic in this list, but you think it >>>> should be there, please let me know ASAP. If you have a new topic to >>>> add, please send me the request before the next Thursday, May 17; the >>>> sooner, the better. The requirements for a topic can be found here: >>>> https://wiki.linaro.org/Platform/DevPlatform/LinuxLinaroKernelTreeProcess#Adding_a_topic_to_linux-linaro_kernel_and_maintaining_it >>>> >>>> >>>> >>>> The landing teams - please update your topic branches if needed: >>>> ARM: >>>> tracking-armlt-hdlcd tracking-armlt-mmc >>>> tracking-armlt-arm-arch-fixes tracking-armlt-misc-fixes >>>> tracking-armlt-ubuntu-config tracking-armlt-android-config >>>> Samsung: >>>> topic/base topic/core topic/bl topic/dt topic/fb topic/pd >>>> topic/s2ram topic/asv_cpufreq topic/led topic/dummy_reg >>>> topic/gadget topic/touch topic/wlan topic/audio topic/hdmi >>>> topic/mali topic/cma_v24 topic/android_config >>>> >>> Is any other LT using CMA patchset? If so, this topic branch can be >>> moved into linux-linaro-core-tracking. >> >> That's a good idea, thanks! >> >> The only problem is that your topic/cma_v24 is based on the topic/base, >> and thus includes "CONFIG: ORIGEN:" commits and an older version of >> linaro-configs-3.4 topic. In particular, the latter recreates >> configs/panda.conf file which has been deleted from the current >> linaro-configs-3.4. Could you please make topic/cma_v24 mainline based >> (drop these "CONFIG: ORIGEN:" and configs/* changes)? And is the >> "CONFIG_CMA_SIZE_MBYTES=32" option Origen specific or generic? If it is >> generic, it should go into a separate file, e.g. configs/cma.conf. >> > I didn't mean to include topic/cma_v24 with the patches from topic/base, > rather the clean patchset from Marek. But now that we have the umm topic > branch in linux-linaro-core-tracking, we don't need topic/cma_v24 > anymore. If any fixes with respect to Origen are required, I will queue > them up in another topic branch. > > I will shortly send you the list of topic branches for 2012.05 release, > now that 3.4-rc7 is already released. >
While migrating the Android solution to use linux-linaro-core-tracking, I get kernel panic with umm-patchset (haven't dug deep into it though, it might be because the multimedia drivers are not yet migrated for using UMM). Would it be ok if we only include CMA patchset, but not the dma-buf and dma-mapping patches? I would like to know the opinion of others regarding this. >> Thanks, >> Andrey > > > -- > Tushar Behera -- Tushar Behera _______________________________________________ linaro-dev mailing list linaro-dev@lists.linaro.org http://lists.linaro.org/mailman/listinfo/linaro-dev
