On Thu, 9 Jun 2011 at 00:13:30 Russell King - ARM Linux wrote:
> On Wed, Jun 08, 2011 at 11:53:49PM +0200, Janusz Krzysztofik wrote:
> > On Fri 10 Dec 2010 at 22:03:52 Janusz Krzysztofik wrote:
> > > Friday 10 December 2010 18:03:56 Russell King - ARM Linux napisał(a):
> > > > On Fri, Dec 10, 2010
On Thu 09 Jun 2011 at 00:13:30 Russell King - ARM Linux wrote:
>
> I stand by my answer to your patches quoted above from a technical
> point of view; we should not be mapping SDRAM using device mappings.
>
> That ioremap() inside dma_declare_coherent_memory() needs to die,
Then how about your a
On Wed, Jun 08, 2011 at 11:53:49PM +0200, Janusz Krzysztofik wrote:
> On Fri 10 Dec 2010 at 22:03:52 Janusz Krzysztofik wrote:
> > Friday 10 December 2010 18:03:56 Russell King - ARM Linux napisał(a):
> > > On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> > > > void __init oma
On Fri 10 Dec 2010 at 22:03:52 Janusz Krzysztofik wrote:
> Friday 10 December 2010 18:03:56 Russell King - ARM Linux napisał(a):
> > On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> > > void __init omap1_camera_init(void *info)
> > > {
> > >
> > > struct platform_device *
Wednesday 15 December 2010 18:01:42 Russell King - ARM Linux wrote:
> On Wed, Dec 15, 2010 at 12:39:20PM +, Catalin Marinas wrote:
> >
> > Should we not try to fix the generic code and still allow platforms
> > to use dma_declare_coherent_memory() in a safer way? I guess it may
> > need some ar
On Wed, Dec 15, 2010 at 12:39:20PM +, Catalin Marinas wrote:
> On 13 December 2010 16:29, Russell King - ARM Linux
> wrote:
> > On Mon, Dec 13, 2010 at 03:52:20PM +, Catalin Marinas wrote:
> >> On 10 December 2010 17:03, Russell King - ARM Linux
> >> wrote:
> >> > On Fri, Dec 10, 2010 at
On 13 December 2010 16:29, Russell King - ARM Linux
wrote:
> On Mon, Dec 13, 2010 at 03:52:20PM +, Catalin Marinas wrote:
>> On 10 December 2010 17:03, Russell King - ARM Linux
>> wrote:
>> > On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
>> >> void __init omap1_camera_i
On Mon, Dec 13, 2010 at 03:52:20PM +, Catalin Marinas wrote:
> On 10 December 2010 17:03, Russell King - ARM Linux
> wrote:
> > On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> >> void __init omap1_camera_init(void *info)
> >> {
> >> struct platform_device *dev = &
On 10 December 2010 17:03, Russell King - ARM Linux
wrote:
> On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
>> void __init omap1_camera_init(void *info)
>> {
>> struct platform_device *dev = &omap1_camera_device;
>> + dma_addr_t paddr = omap1_camera_phys_mempool_ba
Friday 10 December 2010 18:03:56 Russell King - ARM Linux napisał(a):
> On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> > void __init omap1_camera_init(void *info)
> > {
> > struct platform_device *dev = &omap1_camera_device;
> > + dma_addr_t paddr = omap1_camera_phys_
On Fri, Dec 10, 2010 at 12:03:07PM +0100, Janusz Krzysztofik wrote:
> void __init omap1_camera_init(void *info)
> {
> struct platform_device *dev = &omap1_camera_device;
> + dma_addr_t paddr = omap1_camera_phys_mempool_base;
> + dma_addr_t size = omap1_camera_phys_mempool_size;
>
OMAP1 camera driver, when starting up in its videobuf_contig mode, may have
problems with allocating dma coherent memory after system memory gets
fragmented if there is no dedicated memory declared as a dma coherent memory
block associated with the device. To solve this issue, allow for removing
OMAP1 camera driver, when starting up in its videobuf_contig mode, may have
problems with allocating dma coherent memory after system memory gets
fragmented if there is no dedicated memory declared as a dma coherent memory
block associated with the device. To solve this issue, allow for removing
13 matches
Mail list logo
