[PATCH 2/2] DSPBRIDGE: Distinguish between read or write buffers

This patch introduces the check to differentiate the buffers coming to the dsp through bridgedriver. So far they can be input (read) or output (write) or rw (which are treated the same way as an output buffer), this distinctions are made from dsp perspective. Since this needs to be checked on map

Re: [RFC][PATCH 2/2] DSPBRIDGE: Distinguish between read or write buffers

On 2/19/2010 7:44 AM, Chitriki Rudramuni, Deepak wrote: Ramirez Luna, Omar wrote: This patch introduces the check to differentiate the buffers coming to the dsp through bridgedriver. So far they can be input (read) or output (write) or rw (which are treated the same way as an output buffer), thi

Re: [RFC][PATCH 2/2] DSPBRIDGE: Distinguish between read or write buffers

Ramirez Luna, Omar wrote: This patch introduces the check to differentiate the buffers coming to the dsp through bridgedriver. So far they can be input (read) or output (write) or rw (which are treated the same way as an output buffer), this distinctions are made from dsp perspective. Since this

[RFC][PATCH 2/2] DSPBRIDGE: Distinguish between read or write buffers

This patch introduces the check to differentiate the buffers coming to the dsp through bridgedriver. So far they can be input (read) or output (write) or rw (which are treated the same way as an output buffer), this distinctions are made from dsp perspective. Since this needs to be checked on map