All of lore.kernel.org
 help / color / mirror / Atom feed
From: Viral Mehta <viral.mehta@einfochips.com>
To: James Courtier-Dutton <james.dutton@gmail.com>
Cc: alsa-devel@alsa-project.org
Subject: Re: ALSA layer in Linux 2.6.18 and OSS
Date: Mon, 16 Feb 2009 16:55:59 +0530	[thread overview]
Message-ID: <49994D47.10608@einfochips.com> (raw)
In-Reply-To: <ad2655cb0902160304i33439a6fie7c029d918fe6af1@mail.gmail.com>



James Courtier-Dutton wrote:
> 2009/2/16 Viral Mehta <viral.mehta@einfochips.com>:
>   
>> Hi All,
>>
>>
>> When I booted my kernel, I found that there was no "/dev/dsp" device and
>> so my application was not able to run. The application opens "/dev/dsp"
>> device first and then does other things.
>>
>>     
>
> /dev/dsp is the OSS API. So an install without OSS will not have /dev/dsp.
> An application that supports alsa will link to libasound.
> If you have an OSS application that you want to work with ALSA, you
> need to add the ALSA OSS emulation layer.

So, the last question.
Is it possible to write an application totally using ALSA user and 
kernel things (i.e., without having OSS emulation layer)?

In that case, if application will not open /dev/dsp then what ll it do ? 
Just pointers will be great for me.

And will it be possible to implement full-featured application which 
plays stereo and also provides equalizer and etc just by using ALSA ?
-- 
_____________________________________________________________________
Disclaimer: This e-mail message and all attachments transmitted with it
are intended solely for the use of the addressee and may contain legally
privileged and confidential information. If the reader of this message
is not the intended recipient, or an employee or agent responsible for
delivering this message to the intended recipient, you are hereby
notified that any dissemination, distribution, copying, or other use of
this message or its attachments is strictly prohibited. If you have
received this message in error, please notify the sender immediately by
replying to this message and please delete it from your computer. Any
views expressed in this message are those of the individual sender
unless otherwise stated.Company has taken enough precautions to prevent
the spread of viruses. However the company accepts no liability for any
damage caused by any virus transmitted by this email.
__________________________________________________________________________

      reply	other threads:[~2009-02-16 11:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-02-16  7:54 ALSA layer in Linux 2.6.18 and OSS Viral Mehta
2009-02-16 10:52 ` Takashi Iwai
2009-02-16 10:57   ` Viral Mehta
2009-02-16 11:07     ` Takashi Iwai
2009-02-16 20:10     ` Colin Guthrie
2009-02-16 11:04 ` James Courtier-Dutton
2009-02-16 11:25   ` Viral Mehta [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49994D47.10608@einfochips.com \
    --to=viral.mehta@einfochips.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=james.dutton@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
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.