Mailing list moving to Sourceforge

Hello all,

The server used to host current oss-devel mailing lists will be closed 
soon. The replacement list opensound-devel <at> lists.sourceforge.net is 
managed by SourceForge. Further postings should be sent to the new list.

Please register at 
https://lists.sourceforge.net/lists/listinfo/opensound-devel

Best regards,

Hannu

OSS driver for OMAP4 Panda

_______________________________________________
oss-devel mailing list
oss-devel <at> mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

Status of USB audio support in OSS v4 on Linux ?

_______________________________________________
oss-devel mailing list
oss-devel <at> mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

Question about lynxtwo module

I am a user with a question about the lynxtwo module.  On the Open Sound System
forum, cesium suggested sending a note to the
developer's mailing list, because he did not
know the answer.

Could someone please tell me which version 
of Lynx Studio's AES 16 driver the current
OSS lynxtwo module is based on?   
The reason I ask is that I would like to know
whether the OSS module is compatible with the
newest version of the firmware for the AES16.

Lynx Studio made an important improvement in the firmware in Firmware Build 24, 5 August 2010. This version
of the firmware improves the operation of the hardware clock and reduces jitter.
Build 24 of the firmware requires Version
2.0 Build 14 of the Windows driver, or newer,
to function correctly.  So, I would appreciate knowing whether the lynxtwo module is based
on Version 2.0 Build 14 driver or newer.

Thank you,
 Steven German

[PATCH] Linux scripts: Use CC and LD variables

Hi

These changes let cross-compiling work for my case (x86 > x64 and vice
versa).

- Lauri

-- 
http://www.fastmail.fm - A no graphics, no pop-ups email service

From cf8e581748d18d9831a82ef4641c25e91fd43a8e Mon Sep 17 00:00:00 2001
From: Lauri Kasanen <curaga <at> operamail.com>
Date: Fri, 9 Sep 2011 14:34:29 +0300
Subject: [PATCH] Linux scripts: Use CC and LD variables

This fixes cross-compiling.

Signed-off-by: Lauri Kasanen <curaga <at> operamail.com>
---
 setup/Linux/build.sh             |   10 ++++++----
 setup/Linux/oss/build/install.sh |    6 ++++--
 setup/setupdir.sh                |    8 +++++---
 3 files changed, 15 insertions(+), 9 deletions(-)

diff --git a/setup/Linux/build.sh b/setup/Linux/build.sh
index 4b7838c..e889bfe 100644
--- a/setup/Linux/build.sh
+++ b/setup/Linux/build.sh
 <at>  <at>  -11,6 +11,8  <at>  <at>  else
    TXT2MAN=./txt2man
 fi

+[ -z "$LD" ] && LD=ld
+
 rm -rf prototype

 mkdir prototype
 <at>  <at>  -105,7 +107,7  <at>  <at>  cp -a $SRCDIR/setup/Linux/oss/* prototype/$OSSLIBDIR/
 cp -a $SRCDIR/setup/Linux/sbin prototype/usr/
 chmod +x prototype/$OSSLIBDIR/scripts/*

-if ! ld -r -o prototype/$OSSLIBDIR/$OBJECTS/osscore.o target/objects/*.o
+if ! $LD -r -o prototype/$OSSLIBDIR/$OBJECTS/osscore.o target/objects/*.o
 then
   echo Linking osscore failed!
   exit 1
 <at>  <at>  -121,7 +123,7  <at>  <at>  done
 for n in target/modules/*.o
 do
 	N=`basename $n .o`
-	ld -r -o prototype/$OSSLIBDIR/$MODULES/$N.o $n
+	$LD -r -o prototype/$OSSLIBDIR/$MODULES/$N.o $n
 	echo Check devices for $N
   	grep "^$N[ 	]" ./devices.list >> devlist.txt

 <at>  <at>  -147,12 +149,12  <at>  <at>  rm -f /tmp/ossman.txt
 # Link the optional NOREGPARM modules
 if test -d noregparm
 then
-   ld -r -o prototype/$OSSLIBDIR/objects.noregparm/osscore.o noregparm/target/objects/*.o
+   $LD -r -o prototype/$OSSLIBDIR/objects.noregparm/osscore.o noregparm/target/objects/*.o

    for n in noregparm/target/modules/*.o
    do
 	N=`basename $n .o`
-	ld -r -o prototype/$OSSLIBDIR/modules.noregparm/$N.o $n
+	$LD -r -o prototype/$OSSLIBDIR/modules.noregparm/$N.o $n
    done
 fi

diff --git a/setup/Linux/oss/build/install.sh b/setup/Linux/oss/build/install.sh
index e42a3e5..13fdbc2 100644
--- a/setup/Linux/oss/build/install.sh
+++ b/setup/Linux/oss/build/install.sh
 <at>  <at>  -7,6 +7,8  <at>  <at>  else
   echo "OSSLIBDIR=/usr/lib/oss" > /etc/oss.conf
 fi

+[ -z "$LD" ] && LD=ld
+
 cd $OSSLIBDIR/build

 rm -f $OSSLIBDIR/.cuckoo_installed
 <at>  <at>  -201,7 +203,7  <at>  <at>  then
 	exit 3
 fi

-if ! ld -r osscore.ko osscore_mainline.o -o /lib/modules/$UNAME/kernel/oss/osscore.ko
+if ! $LD -r osscore.ko osscore_mainline.o -o /lib/modules/$UNAME/kernel/oss/osscore.ko
 then
 	echo Linking the osscore module failed
 	exit 5
 <at>  <at>  -238,7 +240,7  <at>  <at>  do
 		exit 4
 	fi

-	if ! ld -r $N.ko $N_mainline.o -o /lib/modules/$UNAME/kernel/oss/$N.ko
+	if ! $LD -r $N.ko $N_mainline.o -o /lib/modules/$UNAME/kernel/oss/$N.ko
 	then
 		echo Linking $N module failed
 		exit 6
diff --git a/setup/setupdir.sh b/setup/setupdir.sh
index f9470d0..9bb9f37 100644
--- a/setup/setupdir.sh
+++ b/setup/setupdir.sh
 <at>  <at>  -9,6 +9,8  <at>  <at>  then
 	exit 1
 fi

+[ -z "$CC" ] && CC=cc
+
 echo srcdir=$SRCDIR

 BLDDIR=`pwd`
 <at>  <at>  -84,7 +86,7  <at>  <at>  echo BLDDIR=$BLDDIR > .directories
 echo SRCDIR=$SRCDIR >> .directories
 echo OSSLIBDIR=$OSSLIBDIR >> .directories

-cc -o dirsetup $SRCDIR/setup/dirsetup.c
+$CC $LDFLAGS -o dirsetup $SRCDIR/setup/dirsetup.c

 # Make sure the latest soundcard.h version is installed in the system
 #rm /usr/include/sys/soundcard.h
 <at>  <at>  -142,7 +144,7  <at>  <at>  then
   DTARGETOS="-D$TARGETOS"
 fi

-cc -D`uname -s` $DTARGETOS -o srcconf $SRCDIR/setup/srcconf.c
+$CC $LDFLAGS -D`uname -s` $DTARGETOS -o srcconf $SRCDIR/setup/srcconf.c

 if ./srcconf $*
 then
 <at>  <at>  -245,7 +247,7  <at>  <at>  fi
 # Setup the link to the right os.h file for this operating system.
 (cd kernel/framework/include;ln -s ../../../kernel/OS/$OS/os_*.h os.h)

-cc -o ossvers -I./kernel/framework/include  setup/ossvers.c
+$CC $LDFLAGS -o ossvers -I./kernel/framework/include  setup/ossvers.c
 ./ossvers > .version
 rm ./ossvers

--

-- 
1.7.2.1

_______________________________________________
oss-devel mailing list
oss-devel <at> mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

Support for Xonar DG in Revision 2005

I posted in the forums to get help because my card wasn't working.
(http://4front-tech.com/forum/viewtopic.php?f=5&t=4394)

I was advised that the support announced for the Xonar DG might have
been a typo, and they meant the DS. Is this true? if it is, are there
plans on supporting the DG?

'OSS v4.x API reference - Developing applications for Open Sound System version 4.1' international

Hi!

I'm willing to translate page located at 
http://manuals.opensound.com/developer/ to the Belorussian language (my 
mother tongue). What I'm asking for is your written permission, so you 
don't mind after I'll post the translation to my blog. The translation 
is intended only for web, no print copies planned.

Visitors of your website, who come from Minsk (Belorussia) will be the 
ones, who will read this blogpost, that's the only way to spread them, 
no additional instruments we can use. Every translation we ever do does 
not costs a penny for the webpage, which is translated. All we ask is to 
link back in whatever way you feel confident about it.

You can leave a voice message and I will call you back, if you prefer a 
call instead of emails. Do you prefer email or IM for contact (if any 
questions regarding the translation arise)? What instant messaging 
client (if any) do you use? AIM, MSN, Skype?
Thank you!

Sincerely,
Alyona Lompar
+(360) 488-0303

---
This e-mail, including attachments, may include confidential and/or 
proprietary information, and may be used only by the person or entity to 
which it is addressed. If the reader of this e-mail is not the intended 
recipient or his or her authorized agent, the reader is hereby notified 
that any dissemination, distribution or copying of this e-mail is 
prohibited. If you have received this e-mail in error, please notify the 
sender by replying to this message and delete this e-mail immediately.

oss build 2005 download url?

Hi,

Where can I get the tarball for this release?
http://www.opensound.com/forum/viewtopic.php?f=19&t=4391

it's not in here:
http://www.4front-tech.com/developer/sources/stable/gpl/

--

-- 
Florian Pritz

_______________________________________________
oss-devel mailing list
oss-devel <at> mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

[PATCH] Add sven's oss_hdaudio patch, fix build, change install, others

Hi,

  Attached are several patches:

  1) sven_hdaudio - add support for intel SCH. Posted earlier by Sven to the 
list - I just changed this to unified diff format.
  2) oss_hdaudio - add some ids.
  3) oss_audiopci - fix build.
  4) oss_install - change copy make stage on Linux - 'cp -R' errors out if 
destination has dir symlinks on copied path.
  5) osscore - document max_intrate=0
  6) ossplay/ossrecord - allow fractional time in args for -S, -t options.

Yours,
	Yair K.

_______________________________________________
oss-devel mailing list
oss-devel <at> mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

MIDI in jack not working, envy24HT (ap192)

Hello there!
I finally desided to buy myself a midi keyboard so that I
don't have to use a virtual midi keyboard anymore. And
because I really want to use the midi ports on my
Audiophile 192 ;)

Now to my problem. 
It seems like the midi in jack doesn't work/register any
midi events sent to it.
cat /dev/midi00 (midi input) is silent no matter what I
send and the same happens with the example midi program at:
http://manuals.opensound.com/developer/midiin.c.html

Now the strange thing is that the midi out jack works. So
if I try to send any event with the /dev/midi interface
they seem to be transmitted correctly.

I've tried to look at the driver sourcecode but I just got
confused how the midi stuff works/looks for inputs/outputs.
As midi out works perhaps the driver is listening to the
wrong input?

If this is not the place to ask for help with this matter I
am terribly sorry.

Regards,
Sebasitan Parborg

Intel HD Audio Cougar Point added

Hi,

i successfully managed to add the Intel HD Audio Cougar Point codec of my new Sandy Bridge motherboard to
OSS4. The codec is the ALC892 from Realtek ,which appears to be very similar to the ALC889. I use Linux
Ubuntu 10.04 as my OS. 
This is the output of lspci -s1b -vnn:
00:1b.0 Audio device [0403]: Intel Corporation Cougar Point High Definition Audio Controller
[8086:1c20] (rev 04)
	Subsystem: Micro-Star International Co., Ltd. Device [1462:7673]
	Flags: bus master, fast devsel, latency 0, IRQ 22
	Memory at fe700000 (64-bit, non-prefetchable) [size=16K]
	Capabilities: [50] Power Management version 2
	Capabilities: [60] MSI: Enable- Count=1/1 Maskable- 64bit+
	Capabilities: [70] Express Root Complex Integrated Endpoint, MSI 00
	Capabilities: [100] Virtual Channel
	Capabilities: [130] Root Complex Link
	Kernel driver in use: oss_hdaudio

I applied the following patches to OSS4.2 build 2004:

diff -r -u oss-v4.2-build2004-src-gpl/devlists/Linux /usr/local/src/oss-v4.2-build2004-src-gpl/devlists/Linux
--- oss-v4.2-build2004-src-gpl/devlists/Linux	2011-01-05 21:08:25.000000000 +0100
+++ /usr/local/src/oss-v4.2-build2004-src-gpl/devlists/Linux	2011-04-09 11:59:04.256697114 +0200
 <at>  <at>  -69,6 +69,7  <at>  <at> 
 oss_geode	pci100b,503	National Semiconductor Geode SC1200
 oss_geode	pci1078,103	National Semiconductor Geode CS5530
 oss_geode	pci1022,2093	AMD Geode CS5536 
+oss_hdaudio	pci8086,1c20	Intel High Definition Audio (CPT)
 oss_hdaudio	pci8086,2668	Intel High Definition Audio (ICH6)
 oss_hdaudio	pci8086,27d8	Intel High Definition Audio (ICH7)
 oss_hdaudio	pci8086,269a	Intel High Definition Audio (ESB2)
diff -r -u oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/.devices /usr/local/src/oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/.devices
--- oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/.devices	2011-01-05 02:33:07.000000000 +0100
+++ /usr/local/src/oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/.devices	2011-04-17
18:58:03.468056002 +0200
 <at>  <at>  -7,6 +7,7  <at>  <at> 
 oss_hdaudio	pci8086,3a3e	Intel High Definition Audio (ICH10)
 oss_hdaudio	pci8086,3a6e	Intel High Definition Audio (ICH10)
 oss_hdaudio	pci8086,3b56	Intel High Definition Audio (PCH)
+oss_hdaudio	pci8086,1c20	Intel High Definition Audio (CPT)
 oss_hdaudio	pci10de,26c	Nvidia High Definition Audio (MCP51)
 oss_hdaudio	pci10de,371	Nvidia High Definition Audio (MCP55)
 oss_hdaudio	pci10de,3e4	Nvidia High Definition Audio (MCP61)
diff -r -u oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/hdaudio_codecids.h /usr/local/src/oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/hdaudio_codecids.h
--- oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/hdaudio_codecids.h	2011-01-05
22:06:27.000000000 +0100
+++
/usr/local/src/oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/hdaudio_codecids.h	2011-04-17
20:40:01.587096801 +0200
 <at>  <at>  -843,6 +843,7  <at>  <at> 
   {0x10ec0885, "ALC885", VF_ALC88X_HACK, (char **) &alc883remap}, 
   {0x10ec0888, "ALC888", VF_ALC88X_HACK, (char **) &alc883remap}, 
   {0x10ec0889, "ALC889", VF_ALC88X_HACK, (char **) &alc883remap}, 
+  {0x10ec0892, "ALC892", VF_ALC88X_HACK, (char **) &alc883remap}, 

   /* CMedia HDA codecs */
   {0x13f69880, "CMI9880", VF_NONE, (char **) &cmi9880remap},
diff -r -u oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/oss_hdaudio.c /usr/local/src/oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/oss_hdaudio.c
--- oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/oss_hdaudio.c	2011-01-05
22:06:27.000000000 +0100
+++
/usr/local/src/oss-v4.2-build2004-src-gpl/kernel/drv/oss_hdaudio/oss_hdaudio.c	2011-04-17
17:25:51.785880000 +0200
 <at>  <at>  -32,6 +32,7  <at>  <at> 
 #define INTEL_DEVICE_ICH10_B	0x3a6e
 #define INTEL_DEVICE_PCH	0x3b56
 #define INTEL_DEVICE_P35        0x293e
+#define INTEL_DEVICE_CPT        0x1c20

 #define NVIDIA_VENDOR_ID        0x10de
 #define NVIDIA_DEVICE_MCP51     0x026c
 <at>  <at>  -1821,6 +1822,7  <at>  <at> 
     case INTEL_DEVICE_ICH10:
     case INTEL_DEVICE_ICH10_B:
     case INTEL_DEVICE_PCH:
+    case INTEL_DEVICE_CPT:
       devc->chip_name = "Intel HD Audio";
       break;

As you can see, it is 5 lines of code that i had to add.

kind regards,
Geert

--

-- 
gr.
Geert Hedde

NEU: FreePhone - kostenlos mobil telefonieren und surfen!			
Jetzt informieren: http://www.gmx.net/de/go/freephone