On Fri, 16 Jan 2015 23:30:11 +0100 Jens Thiele <[email protected]> wrote:
> with kernel sunxi-3.4.103 (sunxi-3.4 branch) and CONFIG_CMA=y (as in > sun7i_defconfig) i have no mmc device. > > hardware: > a20 olinuxino micro > > [ 3.494360] [mmc-msg] sw_mci_init > [ 3.503435] [mmc-msg] MMC host used card: 0x9, boot card: 0x0, io_card 8 > [ 3.513585] [mmc-err] alloc dma des failed > [ 3.522066] [mmc-err] sunxi-mmc.0: Failed to get resouce. > [ 3.530705] [mmc-err] alloc dma des failed > [ 3.539168] [mmc-err] sunxi-mmc.3: Failed to get resouce. > > should sun7i_defconfig be adjusted (is CONFIG_CMA=y)? > other hints? You can check whether you have initrd enabled, it might be clashing with the CMA area reservation. If CMA is enabled but fails to initialize, then mmc fails too. If this is the case, then just move initrd to a different location in RAM. > all using mainline now? As for "using", this depends on whether you want full cedar and mali acceleration right now. But as for "developing", the 3.4 kernel is de-facto in the "critical bugfixes only" mode since at least half a year ago. New features are not likely to appear in 3.4, and the known non-critical limitations are not likely to be lifted. This does not mean that it is forbidden to contribute to 3.4 though. Anyone is welcome to submit 3.4 patches, as long as (s)he finds at least one reviewer for them. Please note that even if the patches are posted to the mailing list, not everyone is eager to waste time reviewing 3.4 patches today. -- Best regards, Siarhei Siamashka -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
