* User space drivers
@ 2007-08-02 21:39 Wallace, Brooke
2007-08-02 23:25 ` Rene Herman
2007-08-03 0:04 ` James Courtier-Dutton
0 siblings, 2 replies; 7+ messages in thread
From: Wallace, Brooke @ 2007-08-02 21:39 UTC (permalink / raw)
To: alsa-devel
Hi,
I've been trying to sort thru the ALSA docs and am starting to get the
impression that all of the existing drivers are written as Kernel
Modules. Doesn't this mean that they are running in Kernel space and
infact are not User Space drivers? Shouldn't there be an ALSA Drivers
API document that covers an API that User Space Drivers can use? I must
be mssing something here...
I'm looking into ALSA because my company wants to use this standard for
writing User Space drivers for our product running on various linux
kernels. The reasoning for this is strictly proprietary licensing - our
leagl department is not comfortable with the GPL and the possiblitiy
that something written for Kernel space could at some time be considered
as required to be GPL - not my decision...
-Brooke
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: User space drivers
2007-08-02 21:39 User space drivers Wallace, Brooke
@ 2007-08-02 23:25 ` Rene Herman
2007-08-03 0:04 ` James Courtier-Dutton
1 sibling, 0 replies; 7+ messages in thread
From: Rene Herman @ 2007-08-02 23:25 UTC (permalink / raw)
To: Wallace, Brooke; +Cc: alsa-devel
On 08/02/2007 11:39 PM, Wallace, Brooke wrote:
> I've been trying to sort thru the ALSA docs and am starting to get the
> impression that all of the existing drivers are written as Kernel
> Modules.
Yes. Some stuff like mixing happens in userspace but the lowlevel drivers
are in kernel space.
> Doesn't this mean that they are running in Kernel space and infact are
> not User Space drivers?
Yes.
> Shouldn't there be an ALSA Drivers API document that covers an API that
> User Space Drivers can use? I must be mssing something here...
I believe you are. Who told you that ALSA drivers ran in userspace?
> I'm looking into ALSA because my company wants to use this standard for
> writing User Space drivers for our product running on various linux
> kernels. The reasoning for this is strictly proprietary licensing - our
> leagl department is not comfortable with the GPL and the possiblitiy that
> something written for Kernel space could at some time be considered as
> required to be GPL - not my decision...
You have a sensible legal department. Many hold that distributing Linux
kernelspace code under a non GPL compatible license is illegal, period.
Your job, should you chose to accept it, is convince them that releasing the
code you will be writing under a GPL compatible license is not actually all
that scary. Pointing them to all the other companies that do so can help.
The other option you have is make do without _any_ help from _anyone_ on
this list at least. Good luck.
Rene.
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: User space drivers
2007-08-02 21:39 User space drivers Wallace, Brooke
2007-08-02 23:25 ` Rene Herman
@ 2007-08-03 0:04 ` James Courtier-Dutton
2007-08-03 2:55 ` Eliot Blennerhassett
1 sibling, 1 reply; 7+ messages in thread
From: James Courtier-Dutton @ 2007-08-03 0:04 UTC (permalink / raw)
To: Wallace, Brooke; +Cc: alsa-devel
Wallace, Brooke wrote:
> Hi,
>
> I've been trying to sort thru the ALSA docs and am starting to get the
> impression that all of the existing drivers are written as Kernel
> Modules. Doesn't this mean that they are running in Kernel space and
> infact are not User Space drivers? Shouldn't there be an ALSA Drivers
> API document that covers an API that User Space Drivers can use? I must
> be mssing something here...
>
> I'm looking into ALSA because my company wants to use this standard for
> writing User Space drivers for our product running on various linux
> kernels. The reasoning for this is strictly proprietary licensing - our
> leagl department is not comfortable with the GPL and the possiblitiy
> that something written for Kernel space could at some time be considered
> as required to be GPL - not my decision...
>
> -Brooke
>
Brooke,
What is the problem? Just license your driver as GPL. Result, no more
legal problems.
The advantage of this approach is that you then get to use your device
with Linux. Alternatives along the lines of what you are considering are
not worth the effort by yourselves, and certainly not worth our effort
helping you.
Kind Regards
James
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: User space drivers
2007-08-03 0:04 ` James Courtier-Dutton
@ 2007-08-03 2:55 ` Eliot Blennerhassett
0 siblings, 0 replies; 7+ messages in thread
From: Eliot Blennerhassett @ 2007-08-03 2:55 UTC (permalink / raw)
To: alsa-devel
James Courtier-Dutton wrote:
> Wallace, Brooke wrote:
>> Hi,
>>
>> I've been trying to sort thru the ALSA docs and am starting to get the
>> impression that all of the existing drivers are written as Kernel
>> Modules. Doesn't this mean that they are running in Kernel space and
>> infact are not User Space drivers? Shouldn't there be an ALSA Drivers
>> API document that covers an API that User Space Drivers can use? I must
>> be mssing something here...
What you may be looking for is the plugins API.
Take a look at the alsa-plugins source, there are some examples of
things that talk to other userspace things (E.g. jack or pulseaudio
plugin) or other non alsa drivers (E.g. oss or freebob)
http://hg-mirror.alsa-project.org/alsa-plugins/
But remember not to put any GPL code in your non-gpl driver ;)
As others have mentioned you may not be able to get much help for this
kind of endeavour if you are not prepared to "show us the source".
--
Eliot
^ permalink raw reply [flat|nested] 7+ messages in thread
* User space drivers
@ 2013-10-04 18:27 bmentink
2013-10-04 18:42 ` Pow, Christopher (SWCOE)
0 siblings, 1 reply; 7+ messages in thread
From: bmentink @ 2013-10-04 18:27 UTC (permalink / raw)
To: meta-ti@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 379 bytes --]
Hi all,
I am wanting to implement a user space driver complete with interrupt in yocto.
I see that there is a sample generic platform driver in the kernel, but not sure how to use it.
Say i want to talk to GPIO Is it simply a matter of pointing the .dts entry for the driver to the uio driver?
Any pointers would be very helpful ..
Cheers,
Bernie
Sent from Samsung tablet
[-- Attachment #2: Type: text/html, Size: 714 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: User space drivers
2013-10-04 18:27 bmentink
@ 2013-10-04 18:42 ` Pow, Christopher (SWCOE)
2013-10-04 18:46 ` Denys Dmytriyenko
0 siblings, 1 reply; 7+ messages in thread
From: Pow, Christopher (SWCOE) @ 2013-10-04 18:42 UTC (permalink / raw)
To: bmentink, meta-ti@yoctoproject.org
[-- Attachment #1: Type: text/plain, Size: 1122 bytes --]
Linux documentation is very clear on how to interact with GPIO from user space application and even use them as interrupts. Refer to Documentation/gpio.txt, section “Sysfs Interface for Userspace (OPTIONAL)” – also make sure you enable the sysfs portion of gpiolib in menuconfig (CONFIG_GPIO_SYSFS).
Christopher S. Pow
Senior Engineer, Systems
Honeywell SWCOE - RTOS
o:612-951-5852 c:612-910-1271
"The number you have dialed is imaginary. Please rotate your phone 90 degrees and try again."
From: meta-ti-bounces@yoctoproject.org [mailto:meta-ti-bounces@yoctoproject.org] On Behalf Of bmentink
Sent: Friday, October 04, 2013 1:28 PM
To: meta-ti@yoctoproject.org
Subject: [meta-ti] User space drivers
Hi all,
I am wanting to implement a user space driver complete with interrupt in yocto.
I see that there is a sample generic platform driver in the kernel, but not sure how to use it.
Say i want to talk to GPIO Is it simply a matter of pointing the .dts entry for the driver to the uio driver?
Any pointers would be very helpful ..
Cheers,
Bernie
Sent from Samsung tablet
[-- Attachment #2: Type: text/html, Size: 5647 bytes --]
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: User space drivers
2013-10-04 18:42 ` Pow, Christopher (SWCOE)
@ 2013-10-04 18:46 ` Denys Dmytriyenko
0 siblings, 0 replies; 7+ messages in thread
From: Denys Dmytriyenko @ 2013-10-04 18:46 UTC (permalink / raw)
To: Pow, Christopher (SWCOE); +Cc: meta-ti@yoctoproject.org
Also, you may find this project interesting:
https://github.com/jackmitch/libsoc
--
Denys
On Fri, Oct 04, 2013 at 06:42:22PM +0000, Pow, Christopher (SWCOE) wrote:
> Linux documentation is very clear on how to interact with GPIO from user
> space application and even use them as interrupts. Refer to
> Documentation/gpio.txt, section “Sysfs Interface for Userspace (OPTIONAL)” –
> also make sure you enable the sysfs portion of gpiolib in menuconfig
> (CONFIG_GPIO_SYSFS).
>
> Hi all,
>
> I am wanting to implement a user space driver complete with interrupt in
> yocto. I see that there is a sample generic platform driver in the kernel,
> but not sure how to use it.
>
> Say i want to talk to GPIO Is it simply a matter of pointing the .dts entry
> for the driver to the uio driver?
>
> Any pointers would be very helpful ..
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2013-10-04 18:46 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2007-08-02 21:39 User space drivers Wallace, Brooke
2007-08-02 23:25 ` Rene Herman
2007-08-03 0:04 ` James Courtier-Dutton
2007-08-03 2:55 ` Eliot Blennerhassett
-- strict thread matches above, loose matches on Subject: below --
2013-10-04 18:27 bmentink
2013-10-04 18:42 ` Pow, Christopher (SWCOE)
2013-10-04 18:46 ` Denys Dmytriyenko
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.