#4243: rtems_cache_coherent_allocate fallback is to return heap memory
-------------------------+---------------------
Reporter: Chris Johns | Owner: (none)
Type: defect | Status: new
Priority: normal | Milestone: 6.1
Component: lib | Version: 6
Severity: normal | Resolution:
Keywords: | Blocked By:
Blocking: |
-------------------------+---------------------
Comment (by Sebastian Huber):
Replying to [comment:5 Chris Johns]:
> Replying to [comment:4 Sebastian Huber]:
> > Replying to [comment:3 Chris Johns]:
> > > Replying to [comment:2 Sebastian Huber]:
> > > > The fall back is correct for systems in which all memory is cache
coherent also for DMA.
> > >
> > > It is not correct for a call of this type to make **any** assumption
other than returning memory from the pool it has been given.
> >
> > It is the responsibility of the BSP to set up this allocator.
>
> Agreed, so ....
>
> > There are a couple of BSP for which this fall back is absolutely the
right thing to do.
>
> ... why not have those couple of BSPs take responsibility like all other
BSPs and set up the allocator?
The function to simply use the heap on systems where this makes sense
should be preserved. If you want an explicit initialization for this case,
then please add it.
--
Ticket URL: <http://devel.rtems.org/ticket/4243#comment:7>
RTEMS Project <http://www.rtems.org/>
RTEMS Project
_______________________________________________
bugs mailing list
[email protected]
http://lists.rtems.org/mailman/listinfo/bugs
