Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
ioremap on system memory
35 views
Skip to first unread message
Marcus Folkesson
Nov 10, 2011, 3:20:01 AM11/10/11
to
Hi,
I'm working with a custom based platform based on OMAP-L138.
A driver we are using is ioremapping system memory. It does this to
share data between the GPP and DSP core.
This is not allowed in later kernel versions since ARMv6+ does not support this.
Is there any good(and easy) way to get around this or is it so
fundamentally wrong that the driver should be written from scratch?
Thanks in advance
Med vänliga hälsningar / Best regards
Marcus Folkesson
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
I'm working with a custom based platform based on OMAP-L138.
A driver we are using is ioremapping system memory. It does this to
share data between the GPP and DSP core.
This is not allowed in later kernel versions since ARMv6+ does not support this.
Is there any good(and easy) way to get around this or is it so
fundamentally wrong that the driver should be written from scratch?
Thanks in advance
Med vänliga hälsningar / Best regards
Marcus Folkesson
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majo...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Ryan Mallon
Nov 10, 2011, 5:20:02 PM11/10/11
to
On 10/11/11 19:06, Marcus Folkesson wrote:
> Hi,
>
> I'm working with a custom based platform based on OMAP-L138.
> A driver we are using is ioremapping system memory. It does this to
> share data between the GPP and DSP core.
> This is not allowed in later kernel versions since ARMv6+ does not support this.
>
> Is there any good(and easy) way to get around this or is it so
> fundamentally wrong that the driver should be written from scratch?
Cc'ed the ARM kernel list and Marek Szyprowski (CMA developer). The CMA
> Hi,
>
> I'm working with a custom based platform based on OMAP-L138.
> A driver we are using is ioremapping system memory. It does this to
> share data between the GPP and DSP core.
> This is not allowed in later kernel versions since ARMv6+ does not support this.
>
> Is there any good(and easy) way to get around this or is it so
> fundamentally wrong that the driver should be written from scratch?
patches I think do what you want, but I am not sure if they are merged
yet. The other solution (again, I'm not an expert on this area) is to
not pass the region of memory you want to manage as part of Linux's
normal system memory. See how the OMAP framebuffer driver reserves a
region of SDRAM (arch/arm/plat-omap/fb.c).
Some one else on the ARM list can probably explain in more detail.
~Ryan
Marcus Folkesson
Nov 11, 2011, 2:00:02 AM11/11/11
to
2011/11/10 Ryan Mallon <rma...@gmail.com>
Thank you!
Med vänliga hälsningar / Best regards
Marcus Folkesson
>
> On 10/11/11 19:06, Marcus Folkesson wrote:
>
> > Hi,
> >
> > I'm working with a custom based platform based on OMAP-L138.
> > A driver we are using is ioremapping system memory. It does this to
> > share data between the GPP and DSP core.
> > This is not allowed in later kernel versions since ARMv6+ does not support this.
> >
> > Is there any good(and easy) way to get around this or is it so
> > fundamentally wrong that the driver should be written from scratch?
>
>
> Cc'ed the ARM kernel list and Marek Szyprowski (CMA developer). The CMA
> patches I think do what you want, but I am not sure if they are merged
> yet. The other solution (again, I'm not an expert on this area) is to
> not pass the region of memory you want to manage as part of Linux's
> normal system memory. See how the OMAP framebuffer driver reserves a
> region of SDRAM (arch/arm/plat-omap/fb.c).
>
> Some one else on the ARM list can probably explain in more detail.
>
> ~Ryan
>
Not passing the region of the concerned memory seems to solve the problem.
> On 10/11/11 19:06, Marcus Folkesson wrote:
>
> > Hi,
> >
> > I'm working with a custom based platform based on OMAP-L138.
> > A driver we are using is ioremapping system memory. It does this to
> > share data between the GPP and DSP core.
> > This is not allowed in later kernel versions since ARMv6+ does not support this.
> >
> > Is there any good(and easy) way to get around this or is it so
> > fundamentally wrong that the driver should be written from scratch?
>
>
> Cc'ed the ARM kernel list and Marek Szyprowski (CMA developer). The CMA
> patches I think do what you want, but I am not sure if they are merged
> yet. The other solution (again, I'm not an expert on this area) is to
> not pass the region of memory you want to manage as part of Linux's
> normal system memory. See how the OMAP framebuffer driver reserves a
> region of SDRAM (arch/arm/plat-omap/fb.c).
>
> Some one else on the ARM list can probably explain in more detail.
>
> ~Ryan
>
Thank you!
Med vänliga hälsningar / Best regards
Marcus Folkesson
0 new messages