lkml.org 
[lkml]   [2006]   [Jan]   [9]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [Alsa-devel] Re: [OT] ALSA userspace API complexity
    Date
    Hi,

    On Sunday 08 January 2006 10:24, Jaroslav Kysela wrote:

    > > > > > - PCM with non-interleaved formats
    > > > > There is no need to handle non-interleaved data in kernel level drivers
    > > > > because all the devices use interleaved formats.
    > > >
    > > > Many RME boards support only non-intereleave data.
    > > In such cases it's better to do interleavin/deinterleaving in the kernel
    > > rather than forcing the apps to check which method they should use.
    >
    > I don't think so. The library can do such conversions (and alsa-lib does)
    > quite easy. If we have a possibility to remove the code from the kernel
    > space without any drawbacks, then it should be removed. I don't see any
    > advantage to have such conversions in the kernel.

    Also, when the data is already available as single streams in a user-space
    multi track application, why should it be forced interleaved, when the hardware
    could handle the format just fine?

    Yours,
    Rene

    --
    ExactCODE, Berlin
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2006-01-09 14:08    [W:0.021 / U:2.416 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site