On Mon, Mar 03, 2003 at 08:56:07PM +0100, Jaroslav Kysela wrote:
we are going to release 0.9.0 final this week. The 0.9.0rc8 serie
is the last. I will release next 0.9.0rc8 package as soon as a serious bug
is fixed. Please, report us compilation problems and functional problems
to the
i've been rebuilding kernels and drivers and stuff like that. after a
complete new checkout of ALSA, a complete rebuild of 2.4.19 and of
alsa-driver, then installing ALSA, i get this:
% sudo depmod -ae
depmod: *** Unresolved symbols in /lib/modules/2.4.19-pre6/kernel/sound/acore/snd-pcm.o
depmod:
On Tue, 4 Mar 2003, Paul Davis wrote:
i've been rebuilding kernels and drivers and stuff like that. after a
complete new checkout of ALSA, a complete rebuild of 2.4.19 and of
alsa-driver, then installing ALSA, i get this:
% sudo depmod -ae
depmod: *** Unresolved symbols in
module-init-tools 0.9.10
^
Probably bug in this package. I don't know the exact status of modules in
2.5 (it's dramaticaly changing), but all ALSA modules are GPLed, thus this
problem shouldn't occur.
good first guess, but no luck. i uninstalled it, reinstalled modutils
At Tue, 04 Mar 2003 11:09:14 -0500,
Paul Davis wrote:
module-init-tools 0.9.10
^
Probably bug in this package. I don't know the exact status of modules in
2.5 (it's dramaticaly changing), but all ALSA modules are GPLed, thus this
problem shouldn't occur.
good first
On Tue, Mar 04, 2003 at 11:09:14AM -0500, Paul Davis wrote:
module-init-tools 0.9.10
^
Probably bug in this package. I don't know the exact status of modules in
2.5 (it's dramaticaly changing), but all ALSA modules are GPLed, thus this
problem shouldn't occur.
good
good first guess, but no luck. i uninstalled it, reinstalled modutils
2.4.9, and the same problem occurs.
modutils-2.4.9 is fairly old.. isn't it 2.4.19?
GACK!! this is what happens when the output of ftp's ls command
scrolls off the screen, and you conclude that 2.4.9 is the latest.
Enclosed below is a substantial patch (against current CVS) for the
HDSP driver. It does a number of things:
* read access to mixer
* remove force_firmware option, since it does nothing (the
h/w can't be reloaded without a power cycle)
* fix RMS meter offsets
Paul,
Thanks for the work. As I am Planet flow, I'll have to wait for
Fernando's next Alsa build cycle to test the HDSP 9652 mixer, but I'll be on
it within minutes of his release, I promise. (And I understand it is
untested and may not work at all.)
Or, if someone wants to help me through
(sorry for the off-topic post, but i want people
on these lists to have the first chance at this)
Rev 1.5 Hammerfall Digi9652
all cables
Windows/Mac driver CD
original packing materials
current street price: about $580
asking price: $480 OBO + shipping
uuencoded, bzipped, tar file of 2 firmware files. takashi - i promise
to add loading from disk after i get back from ZKM, ok ? :))
--p
begin 664 hdsp-firmware-rev11.tar.bz2
M0EIH.3%!6293641()]H`^X9_Y/[EMAIL PROTECTED]O^GW\H`0`#D
M'P?#WO?;'HW=JY.G`!]2076^[GV:R]N1WLP[UN[+NG5NNJ[%;WY-6IQZ
This was intended to reach the list, I guess.
On Tue, 2003-03-04 at 22:54, Paul Davis wrote:
[not posted to alsa-dev]
Why didn't you keep the limit calculation. It avoids having useless
simple mixer entries with the multiface. (Think of users using
alsamixer) ?
ah, actually, that was what
Hi,
I started writing a new driver for the Aureal Vortex soundcards.
Now the howto is pretty good, and the basic stuff is nearly
complete, but
how do i integrate my driver into the configure scripts,
Makefiles, and
all sorts of thingiees that makee up the tree ?
I placed the driver (several
This is a new version of the previous patch, but now also includes:
* use of udelay to force timed loops rather than count-based loops
* fix hdsp_is_9652()
* don't include unnecessary playback mixer controls for Multiface
* don't attempt to download firmware to HDSP9652 systems
What is the official procedure to integrate my driver ?
my approach has always been:
cd $TOP_OF_ALSA_TREE
find . -type f | xargs grep SOME_OTHER_CARD_NAME
where SOME_OTHER_CARD_NAME is picked from a suitable existing driver.
this lets me see all the places i have to refer to it.
but
Hi,
On Tue, Mar 04, 2003 at 03:20:05PM -0800, [EMAIL PROTECTED] wrote:
Message: 2
Date: Tue, 4 Mar 2003 19:35:35 -0400
From: mjander [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Subject: [Alsa-devel] New driver
Hi,
I started writing a new driver for the Aureal
Hi all,
The new pcm_jack thing presents a bit of a chicken and egg problem; I
just compiled alsa-lib twice because jack depends on alsa-lib and if you
configure alsa-lib with jack support, it depends on jack. Would it be
possible for pcm_jack to be distributed seperately?
Cheers,
Bob
--
Bob
I think snd-serialmidi is broken for MS-124W MIDI interfaces in MB mode,
and that it has something to do with running status not being handled
correctly.
You need my patch, which I posted previously, to get MB mode working at
all.
The MS-124W seems to work in SA mode.
When I run this interface
lists about this and to do it cleanly it would be nice to have available
in /proc/asound the list of modules currently loaded. That is not
available today (I think Takashi said he might add that).
cat /proc/modules | grep '^snd'
This relies in an (AFAIK) unenforceable
lists about this and to do it cleanly it would be nice to have available
in /proc/asound the list of modules currently loaded. That is not
available today (I think Takashi said he might add that).
cat /proc/modules | grep '^snd'
I wrote this:
This relies in an (AFAIK) unenforceable
20 matches
Mail list logo
