Hi Marek,
On Mon, Jan 30, 2012 at 9:43 AM, Marek Szyprowski
wrote:
> Did you managed to fix this issue?
Yes -- the recent increase in the vmalloc region triggered a bigger
truncation in the system RAM than we had before, and therefore
conflicted with the previous hardcoded region we were using.
Hello,
On Saturday, January 28, 2012 7:57 PM Ohad Ben-Cohen wrote:
> On Fri, Jan 27, 2012 at 5:17 PM, Marek Szyprowski
> wrote:
> > There have been some vmalloc layout changes merged to v3.3-rc1.
>
> That was dead-on, thanks a lot!
Did you managed to fix this issue?
>
> I did then bump into
Hi Marek,
On Fri, Jan 27, 2012 at 5:17 PM, Marek Szyprowski
wrote:
> There have been some vmalloc layout changes merged to v3.3-rc1.
That was dead-on, thanks a lot!
I did then bump into a different allocation failure which happened
because dma_alloc_from_contiguous() computes 'mask' before capp
Hello,
On Friday, January 27, 2012 3:59 PM Ohad Ben-Cohen wrote:
> 2012/1/27 Marek Szyprowski :
> > Ohad, could you tell a bit more about your issue?
>
> Sure, feel free to ask.
>
> > Does this 'large region'
> > is a device private region (declared with dma_declare_contiguous())
>
> Yes, it i
2012/1/27 Marek Szyprowski :
> Ohad, could you tell a bit more about your issue?
Sure, feel free to ask.
> Does this 'large region'
> is a device private region (declared with dma_declare_contiguous())
Yes, it is.
See omap_rproc_reserve_cma() in:
http://git.kernel.org/?p=linux/kernel/git/ohad/
2012/1/27 Marek Szyprowski :
> I've tested it with 256MiB on Exynos4 platform. Could you check if the
> problem also appears on 3.2-cma-v19 branch (I've uploaded it a few hours
> ago)
Exactly what I needed, thanks :)
Both v18 and v19 seem to work fine with 3.2.
> The above code has not been chan
Hello,
On Friday, January 27, 2012 3:28 PM Clark, Rob wrote:
> 2012/1/27 Marek Szyprowski :
> > Hi Ohad,
> >
> > On Friday, January 27, 2012 10:44 AM Ohad Ben-Cohen wrote:
> >
> >> With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
> >> In particular, this seems to fail:
> >>
>
2012/1/27 Marek Szyprowski :
> Hi Ohad,
>
> On Friday, January 27, 2012 10:44 AM Ohad Ben-Cohen wrote:
>
>> With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
>> In particular, this seems to fail:
>>
>> On Thu, Jan 26, 2012 at 11:00 AM, Marek Szyprowski
>> wrote:
>> > +static in
Hi Ohad,
On Friday, January 27, 2012 10:44 AM Ohad Ben-Cohen wrote:
> With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
> In particular, this seems to fail:
>
> On Thu, Jan 26, 2012 at 11:00 AM, Marek Szyprowski
> wrote:
> > +static int cma_activate_area(unsigned long base_p
Hi Marek,
With v19, I can't seem to allocate big regions anymore (e.g. 101MiB).
In particular, this seems to fail:
On Thu, Jan 26, 2012 at 11:00 AM, Marek Szyprowski
wrote:
> +static int cma_activate_area(unsigned long base_pfn, unsigned long count)
> +{
> + unsigned long pfn = base_pfn;
>
10 matches
Mail list logo
