From: "Pavana Sharma" <pavans@india.ti.com>
To: 'Jaroslav Kysela' <perex@suse.cz>, 'Takashi Iwai' <tiwai@suse.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: RE: OSS mapping for ALSA controls
Date: Mon, 12 Apr 2004 14:05:27 +0530 [thread overview]
Message-ID: <03f901c42069$1bdbc8a0$f8b6a8c0@ent.ti.com> (raw)
In-Reply-To: <Pine.LNX.4.58.0404081911240.1867@pnote.perex-int.cz>
Shell supported by the target are ash , dash
Is this causing problem ..??
Regards
Pavan S
-----Original Message-----
From: Jaroslav Kysela [mailto:perex@suse.cz]
Sent: Thursday, April 08, 2004 10:43 PM
To: Takashi Iwai
Cc: pavans@india.ti.com; alsa-devel@lists.sourceforge.net
Subject: Re: [Alsa-devel] OSS mapping for ALSA controls
On Thu, 8 Apr 2004, Takashi Iwai wrote:
> At Thu, 8 Apr 2004 10:59:50 +0530,
> Pavana Sharma wrote:
> >
> > yes, I did this as root ..
>
> hmm, it works for me.
>
> # echo 'VOLUME "Line Playback" 0' > /proc/asound/card0/oss_mixer
> # cat /proc/asound/card0/oss_mixer | grep VOLUME
> VOLUME "Line Playback" 0
Shell problem? The embedded devices has stripped things.
Jaroslav
-----
Jaroslav Kysela <perex@suse.cz>
Linux Kernel Sound Maintainer
ALSA Project, SuSE Labs
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click
prev parent reply other threads:[~2004-04-12 8:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 14:08 OSS mapping for ALSA controls Pavana Sharma
2004-04-07 18:10 ` Takashi Iwai
2004-04-08 5:29 ` Pavana Sharma
2004-04-08 17:07 ` Takashi Iwai
2004-04-08 17:12 ` Jaroslav Kysela
2004-04-12 8:35 ` Pavana Sharma [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='03f901c42069$1bdbc8a0$f8b6a8c0@ent.ti.com' \
--to=pavans@india.ti.com \
--cc=alsa-devel@lists.sourceforge.net \
--cc=perex@suse.cz \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox