ected to be merged via akpm tree together with other core memory
management
patches. I got a message that Andrew Morton scheduled it for v3.5 kernel, so it
should
be soon available in linux-next tree.
Best regards
--
Marek Szyprowski
Samsung
= ALIGN(limit, alignment);
> + limit &= ~(alignment - 1);
>
> /* Reserve memory */
> if (base) {
> --
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
___
linaro-dev mailing list
linaro-dev@lists.linaro.org
http://lists.linaro.org/mailman/listinfo/linaro-dev
hat really want a 64 bit machine anyway.
I know, I just suggested it as a workaround of the current CMA initialization
bug. The other temporary solution is to enable DMA zone and set it to some
high value (like 512MiB).
Best regards
--
Marek Szyprowski
Samsung Poland R&D Center
__
> If it's expected to blow chunks, is there a hack or workaround that will
> allow us to have both HIGHMEM and CMA on OMAP4?
I'm aware of this issue, I hope to post a fix ASAP I finish some of my urgent
bug fixing related to our project. In meantime I suggest using 2G/2G me
v-ehci.c is the only consumer of setup-usb-phy.c,
> could setup-usb-phy.o be made dependent on the S5P_DEV_USB_EHCI config
> option? Any particular reason to create a new EXYNOS4_SETUP_USB_PHY
> config option in this case? Will there be a case where usb phy
> configuration
lution).
>
> I am currently aware of the following solutions floating around the net
> that all solve different parts of the problem:
>
> In the kernel: GEM and TTM.
> Out-of-tree: HWMEM, UMP, CMA, VCM, CMEM, PMEM.
>
> I'm sure that last list is incomplete.
Best re
Hello,
On Tuesday, March 01, 2011 11:26 AM Edward Hervey wrote:
> On Mon, 2011-02-28 at 09:50 +0100, Marek Szyprowski wrote:
> > Hello,
> [...]
> >
> > I'm not sure that highmem is the right solution. First, this will force
> > systems with rather small
or making physically contiguous
>segments available.
I'm not sure that highmem is the right solution. First, this will force
systems with rather small amount of memory (like 256M) to use highmem just
to support DMA allocable memory. It also doesn't solve the issue with
specific mem
