Given that, technically, I can use ALSA with a user-space device driver, am
I right in thinking that the user-space driver must have a license that is
GPL compatible?
Or is a closed source driver allowed?
Thanks,
Phil
> -----Original Message-----
> From: Jaroslav Kysela [mailto:[EMAIL PROTECTED]]
> Sent: 06 September 2001 16:21
> To: Phil Thompson
> Cc: '[EMAIL PROTECTED]'
> Subject: Re: [Alsa-devel] User Space Device Driver
>
>
> On Thu, 6 Sep 2001, Phil Thompson wrote:
>
> > I want to provide an ALSA API library interface to a
> particular audio
> > device. Unusually, the published API to the device is
> itself a user space
> > library (there are good reasons for this).
> >
> > I guess the first question is: would the existing ALSA
> architecture cope
> > with this?
> >
> > Originally I was planning just to implement a thin wrapper
> around the device
> > API that provided a sub-set of the ALSA API - not using any
> ALSA code, just
> > stealing part of the API definition. (It's for an embedded
> system, so there
> > would be no problem with users wanting to install the real ALSA API
> > library.)
> >
> > Then is occured to me that maybe I can use the ALSA API
> library, but just
> > replace the hwdep/hwdep_hw.c file with something that calls
> the device API.
> > Is it as simple as that?
>
> Yes, it is. You can name your output with different name and
> describe your
> output device in configuration file...
>
> > Obviously I would have to conform to the API library/kernel
> interface. I
> > appreciate that this isn't part of the published API - but
> is it explicitly
> > documented somewhere, or is it a question of using the source?
>
> Unfortunately, we haven't any documentation about this interface.
>
> Jaroslav
>
> -----
> Jaroslav Kysela <[EMAIL PROTECTED]>
> SuSE Linux http://www.suse.com
> ALSA project http://www.alsa-project.org
>
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel
