Brian Furey wrote:
> i'm using an open source VoIP application with the
> alsa driver. My card is the onboard intel8x0.
>
>My problem is figuring out the patterns I am
> getting with the alsa driver when transmitting
> packets.
This depends more on how the VoIP application does things, not on
Brian Furey wrote:
Hi James,
Im asking you becuae looking thru the archives you asked a similar
question a long time ago.
i'm using an open source VoIP application with the
alsa driver. My card is the onboard intel8x0.
My problem is figuring out the patterns I am
getting with the alsa driver
Hi James,
Im asking you becuae looking thru the archives you asked a similar question a long time ago. i'm using an open source VoIP application with thealsa driver. My card is the onboard intel8x0.
My problem is figuring out the patterns I amgetting with the alsa driver when transmittingpackets
Does anyone have a list of sound cards that alsa does not support.
It would be nice to have a list of sound cards that alsa does not
support, and next to it, details of anyone currently working on writing
a driver.
We could start a list on the wiki at http://alsa.opensrc.org/
My initial questio
Jaroslav,
Busy system cant explain something as consequent as this.
When the packet size being transmitted is 30 msecs(240bytes) or 32 msecs(240bytes), the OpenH323 app sends packets every 32 msecs.
When the packet size is 80 msecs(132 bytes), the OpenH323 app sends packets at alternate intervals
On Tue, 6 Apr 2004, Brian Furey wrote:
> Hi all,
>i'm running the alsa-driver-1.0.0. Im using it with
> the OpenH323 application. Packets are transmitted or
> received in 32 millisecond intervals or multiples of
> 32 millisecond intervals.
> For example using the G711 codec, packets are
> tran
Hi all,
i'm running the alsa-driver-1.0.0. Im using it with
the OpenH323 application. Packets are transmitted or
received in 32 millisecond intervals or multiples of
32 millisecond intervals.
For example using the G711 codec, packets are
transmitted every 32 milliseconds. For the GSM-06.10
codec
Hi,
Just checked out 1.0.4rc1 a few moments ago and I'm already missing the
snd-usb-usx2y module. AFAICT it's not being included by
./configure --with-cards option, nor it gets built when one sets
--with-cards=all.
I am quite sure this was being built as of 1.0.3 and before. The source
files are
alsa-driver-1.0.3 with Linux 2.6.4 always has a FATAL modprobe error
when loading the ALSA modules for the first time. However, if you remove
the ALSA modules and then immediately re-load them, there is never an error
and ALSA works ok. Is this a bug or a modprobe.conf problem?
Exactly the same m
On Tue, 23 Mar 2004, Jonathan Woithe wrote:
> > Could you add exactly same initialization sequence to
> > alsa-oss/test/testoss.c code? So we can debug easily the problem here.
>
> Sorry, I couldn't see where this would fit in in this file - testoss.c seems
> more like it's testing the oss redir
Hi all
> > I did this last night. The following is my analysis of the problem.
> > With full debug selected, the only message reported by the ALSA system is
> > ALSA ../alsa-kernel/core/pcm_timer.c:70: BUG? (rate != 0)
> > (called from d8c33a79)
> > That is, the assertion "rate!=0" fails. T
On Thu, 18 Mar 2004, Jonathan Woithe wrote:
> I did this last night. The following is my analysis of the problem.
>
> With full debug selected, the only message reported by the ALSA system is
> ALSA ../alsa-kernel/core/pcm_timer.c:70: BUG? (rate != 0)
> (called from d8c33a79)
> That is, the
Takashi
> > > > I have been trying cinelerra 1.1.9 in OSS mode against the OSS emulation
> > > > driver (snd-pcm-oss) from ALSA driver 1.0.2c. Whenever anything is done to
> > > > start audio playback (such as playing a video clip) the ALSA driver panics
> > > > with a divide by zero error. The d
At Tue, 16 Mar 2004 08:45:00 +1030 (CST),
Jonathan Woithe wrote:
>
> > > I have been trying cinelerra 1.1.9 in OSS mode against the OSS emulation
> > > driver (snd-pcm-oss) from ALSA driver 1.0.2c. Whenever anything is done to
> > > start audio playback (such as playing a video clip) the ALSA driv
> > I have been trying cinelerra 1.1.9 in OSS mode against the OSS emulation
> > driver (snd-pcm-oss) from ALSA driver 1.0.2c. Whenever anything is done to
> > start audio playback (such as playing a video clip) the ALSA driver panics
> > with a divide by zero error. The decoded oops is found belo
At Mon, 15 Mar 2004 09:47:07 +1030 (CST),
Jonathan Woithe wrote:
>
> Hi all
>
> I have been trying cinelerra 1.1.9 in OSS mode against the OSS emulation
> driver (snd-pcm-oss) from ALSA driver 1.0.2c. Whenever anything is done to
> start audio playback (such as playing a video clip) the ALSA driv
Hi all
I have been trying cinelerra 1.1.9 in OSS mode against the OSS emulation
driver (snd-pcm-oss) from ALSA driver 1.0.2c. Whenever anything is done to
start audio playback (such as playing a video clip) the ALSA driver panics
with a divide by zero error. The decoded oops is found below.
Unde
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=006
==
Reporter: Hai
Handler:
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=006
==
Reporter: Hai
Handler:
The following bug has been ASSIGNED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=006
==
Reporter: Hai
Handler:
The following bug has been RESOLVED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=007
==
Reporter: yahoo
Handler:
The following bug has been CLOSED
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=005
==
Reporter: ZlatkO
Han
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=007
==
Reporter: yahoo
Handler:
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=007
==
Reporter: yahoo
Handler:
The following NEW bug has been ADDED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=007
==
Reporter: yahoo
Handler:
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=005
==
Reporter: ZlatkO
Handler:
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=005
==
Reporter: ZlatkO
Handler:
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=005
==
Reporter: ZlatkO
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=005
==
Reporter: ZlatkO
Handler:
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=005
==
Reporter: ZlatkO
The following bug has been CLOSED
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=004
==
Reporter: khali
Hand
The following bug has been ASSIGNED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=005
==
Reporter: ZlatkO
The following bug has been ASSIGNED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=004
==
Reporter: khali
H
The following NEW bug has been ADDED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=006
==
Reporter: Hai
Handler:
The following NEW bug has been ADDED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=005
==
Reporter: ZlatkO
Handler:
The following NEW bug has been ADDED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=004
==
Reporter: khali
Handler:
The following bug has been CLOSED
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=002
==
Reporter: ZlatkO
Han
A BUGNOTE has been added to this bug.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_advanced_page.php?bug_id=002
==
Reporter: ZlatkO
The following NEW bug has been ADDED.
==
http://bugtrack.alsa-project.org/alsa-bug/bug_view_page.php?bug_id=002
==
Reporter: ZlatkO
Handler:
The following bug has been CLOSED
==
http://bugtrack.alsa-project.org/alsa-bugtracking-system/bug_view_page.php?bug_id=001
==
Reporter: test
I previously reported a problem on Thu, 27 Nov 2003,
with loading the snd-interwave module from alsa-driver-1.0.0pre3
into linux-2.2.25, and a "fix" for this on Fri, 12 Dec 2003.
I have looked harder at this now and think that the fix should be
to define CONFIG_ISAPNP in support/pnp/pnp.c, before
Hello, I previously reported a problem loading the snd-interwave
module from alsa-driver-1.0.0pre3 into linux-2.2.25.
I found a fix, but not the complete answer, because I'm not yet clear
about the different roles of the support/isapnp and support/pnp code.
The problem is that support/pnp/pnp.c r
After removing
sndversions.h & linux/modversions.h
from
/pcmcia/vx/vxpocket.c &
/pcmcia/vx/vxp440.c
I was able to compile alsa but this probably broke the vxp driver :)
Op do 11-12-2003, om 13:21 schreef lupus:
> package: alsa-driver-1.0.0rc2
> kernel: 2.6.0-0.test11
>
> kernel 2.6 doesn't
package: alsa-driver-1.0.0rc2
kernel: 2.6.0-0.test11
kernel 2.6 doesn't use make dep any more so modversions.h isn't created
anymore
make[1]: Binnengaan van map `/lib/modules/2.6.0-0.test11.1.99/build'
CHK include/linux/version.h
*** Warning: Overriding SUBDIRS on the command line can caus
Hi!
I have compilation problems with alsa-driver-1.0.0rc2:
--- skip
make[1]: Entering directory `/usr/src/linux-2.6.0-test11'
*** Warning: Overriding SUBDIRS on the command line can cause
*** inconsistencies
make[2]: `arch/i386/kernel/asm-offsets.s' is up to date.
CC [M] /home/dmi
Hello Takashi,
> Takashi Iwai wrote:
> Ted wrote:
> >
> > # modprobe -v snd-interwave
> > /sbin/insmod /lib/modules/2.2.25/misc/snd-interwave.o \
> > index=0 id=GusPnP enable=1 isapnp=1 port=0x220 irq=15 \
> > dma1=5 dma2=7 midi=0 pcm_channels=8 effect=1
>
> what happens if you don
At Thu, 27 Nov 2003 01:54:45 +,
Ted wrote:
>
> # modprobe -v snd-interwave
> /sbin/insmod /lib/modules/2.2.25/misc/snd-interwave.o \
> index=0 id=GusPnP enable=1 isapnp=1 port=0x220 irq=15 \
> dma1=5 dma2=7 midi=0 pcm_channels=8 effect=1
what happens if you don't pass the port
At Wed, 26 Nov 2003 23:45:52 +,
Ted wrote:
>
> Hello,
>
> Takashi Iwai <[EMAIL PROTECTED]> wrote on Tue, 25 Nov 2003:
> > right now the ALSA 1.0.0pre3 packages are released.
> [...]
> > The 2.2 kernel is still not tested well. If you can test it, please
> > let us know.
>
> alsa-driver-1.0.
Hi,
I'm trying to use alsa-driver-1.0.0pre3 with linux-2.2.25 and
gcc-2.95.3 for a GravisUltrasound PNP Pro and TMC PCI54ITS motherboard.
Previously, with alsa-driver-0.9.0rc6 and linux-2.2.20, I used isapnp
to map out certain IRQs after a cold-boot, before the snd-card-interwave
module would
Hello,
Takashi Iwai <[EMAIL PROTECTED]> wrote on Tue, 25 Nov 2003:
> right now the ALSA 1.0.0pre3 packages are released.
[...]
> The 2.2 kernel is still not tested well. If you can test it, please
> let us know.
alsa-driver-1.0.0pre3/acore/pci_compat_22.c:line 371, refers to
char *pci_n
On Mon, 24 Nov 2003 14:01:16 +0100, Takashi Iwai wrote:
>At Mon, 24 Nov 2003 02:20:07 -0500,
>Jonathan Kraut wrote:
>>
>> Everything works really well (hooray dmix! and thanks) with
>> alsa-driver-1.0.0pre2 and cmedia-8738 except the following midi related
>> things, which were working fine in v
At Mon, 24 Nov 2003 02:20:07 -0500,
Jonathan Kraut wrote:
>
> Everything works really well (hooray dmix! and thanks) with
> alsa-driver-1.0.0pre2 and cmedia-8738 except the following midi related
> things, which were working fine in version 0.9.8 and earlier:
>
> here's what i did (on gentoo)
>
Everything works really well (hooray dmix! and thanks) with
alsa-driver-1.0.0pre2 and cmedia-8738 except the following midi related
things, which were working fine in version 0.9.8 and earlier:
here's what i did (on gentoo)
$ /etc/init.d/alsasound start
$ cat /proc/asound/cards
0 [CMI8738MC6
There is a bug in the alsa-driver file
"utils/convert_isapnp_ids" that causes compilation of
alsa-driver to fail if gawk runs in POSIX mode (which
is the case if the environment variable
POSIXLY_CORRECT is set).
Line 84 of convert_isapnp_ids currently says:
if (match($0, "\{.*\}")) {
The slas
On Tue, 04 Nov 2003 12:10:23 -0500, Paul Davis wrote:
>>At Mon, 03 Nov 2003 14:41:51 -0500,
>>Jonathan Kraut wrote:
>>>
>>>
>>> Hello again. Further research:
>>>
>>> I tried an earlier version of jack (0.71.0) with alsa-driver-0.9.8, accessi
>n
>>g hw:0,2 via my .asoundrc. I get the same resu
At Tue, 04 Nov 2003 13:10:17 -0500,
Jonathan Kraut wrote:
>
>
> On Tue, 04 Nov 2003 12:10:23 -0500, Paul Davis wrote:
> >>At Mon, 03 Nov 2003 14:41:51 -0500,
> >>Jonathan Kraut wrote:
> >>>
> >>>
> >>> Hello again. Further research:
> >>>
> >>> I tried an earlier version of jack (0.71.0) with
On Tue, 04 Nov 2003 12:10:23 -0500, Paul Davis wrote:
>>At Mon, 03 Nov 2003 14:41:51 -0500,
>>Jonathan Kraut wrote:
>>>
>>>
>>> Hello again. Further research:
>>>
>>> I tried an earlier version of jack (0.71.0) with alsa-driver-0.9.8, accessin
>>g hw:0,2 via my .asoundrc. I get the same result
>At Mon, 03 Nov 2003 14:41:51 -0500,
>Jonathan Kraut wrote:
>>
>>
>> Hello again. Further research:
>>
>> I tried an earlier version of jack (0.71.0) with alsa-driver-0.9.8, accessin
>g hw:0,2 via my .asoundrc. I get the same result as before, but in addition th
>is particular version of jackd
At Mon, 03 Nov 2003 14:41:51 -0500,
Jonathan Kraut wrote:
>
>
> Hello again. Further research:
>
> I tried an earlier version of jack (0.71.0) with alsa-driver-0.9.8, accessing hw:0,2
> via my .asoundrc. I get the same result as before, but in addition this particular
> version of jackd tells
Hello again. Further research:
I tried an earlier version of jack (0.71.0) with alsa-driver-0.9.8, accessing hw:0,2
via my .asoundrc. I get the same result as before, but in addition this particular
version of jackd tells me:
...
Sorry. The PCM device "cmipci"doesn't support the same sample f
(I sent this earlier twice but forgot to subscribe and then gave wrong email address,
so earlier two are pending moderator approval. Please ignore those, and sorry).
Hi,
Alsa-driver-0.9.8 doesn't work properly for full duplex operation with jack-0.80 and
spdif from a cmedia 8738. (I had been
Apologies for not including this at first. The proper
fix is not to delete the { }, although this originally
worked in my case. The { } should actually be escaped
as follows:
if (match($0, "\{.*\}"))
This works regardless of whether gawk is operating in
POSIX mode.
The reason for this is that
I have discovered a bug in
alsa-driver-0.9.7/utils/convert_isapnp_ids line 84.
Ordinarilly in GNU gawk, the line
if (match($0, "{.*}"))
works fine. However, if the environment
POSIXLY_CORRECT is set (it is on my system, since I
like things to be standards-compliant, although it
probably is not
config
> > files. The error happens during the search of some
> > sound
> > config files in conf.c file of ALSA lib.
> >
> > The .asoundrc file is kept at / and /root. The
> > alsa.conf file is placed in /alsa and
> /usr/share/alsa
>
> / is not referred at all.
> the file is either ~/.asoundrc
At Wed, 16 Jul 2003 07:40:08 -0700 (PDT),
Prince John wrote:
> Looks like, both utilities are looking for some config
> files. The error happens during the search of some
> sound
> config files in conf.c file of ALSA lib.
>
> The .asoundrc file is kept at / and /root. The
> alsa.conf file is plac
Hi,
I'm facing some problems while testing a driver
developed for a Hitachi SH4 based board. The board has
an AC97 codec and codec controller.
I'm working as 'root'. The devices are created with
'snddevices' and all modules are loaded properly.
When tried to test the driver by running 'amixer' and
Hi,
I am about to start writing an alsa driver for a bluetooth headset.
Is anyone else working on this, or shall I start from scratch.
I will be using information from the kernel bluetooth modules together
with the affix project. (affix.sf.net)
Once finished I will post the source code to this li
At Thu, 20 Mar 2003 12:49:26 +0200,
Andrei Boros wrote:
>
> Takashi Iwai wrote:
> >
> > > I got make 3.79 installed, hopefully the sequencer module problems will
> > > be solved, but I get a tiny error that didn't appear before when runing
> > > cvscompile :
> > >
> > > I updated the cvs tree, di
At Thu, 20 Mar 2003 10:20:53 +0200,
Andrei Boros wrote:
>
>
> I got make 3.79 installed, hopefully the sequencer module problems will
> be solved, but I get a tiny error that didn't appear before when runing
> cvscompile :
>
> I updated the cvs tree, did a make clean, deleted Makefile, then ran
I got make 3.79 installed, hopefully the sequencer module problems will
be solved, but I get a tiny error that didn't appear before when runing
cvscompile :
I updated the cvs tree, did a make clean, deleted Makefile, then ran
./cvscompile.
This is the first line it outputs:
make: *** No rule to m
At Mon, 10 Mar 2003 13:22:22 +0200,
Andrei Boros wrote:
>
>
> CVS update 5 min. ago gives the following error when attempting driver
> compilation with cs46xx and opti92x-ad1848 :
these errors seem strange.
could you run "make clean" and cvscompile again?
Takashi
At Sun, 09 Mar 2003 20:44:35 -0400,
Manuel Jander wrote:
>
> Oops, i'm very sorry... wrong list :-(.
> Won't happen again, i swear.
> Please excuse my mistake. Was ment for the OpenVortex devel list.
don't worry :)
i'd like to see the development of ALSA vortex driver.
it would be appreciated if
CVS update 5 min. ago gives the following error when attempting driver
compilation with cs46xx and opti92x-ad1848 :
gcc -D__KERNEL__ -DMODULE=1
-I/serve/install/alsa-cvs/alsa-driver/include -I/usr/src/linux/include
-O2 -march=i586 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer
-Wno-trigr
Oops, i'm very sorry... wrong list :-(.
Won't happen again, i swear.
Please excuse my mistake. Was ment for the OpenVortex devel list.
---
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging
Hi everyone,
I'm writing a Vortex ALSA driver, recycling most hardware stuff from the
experimental OSS driver on savannah. I only own a AU8820, but support
for the other cards shouldnt be difficult, because anything was done
with portability in mind, and i keep looking into the other cards
dis
right?
Thanks,
Prince
"mjander " <[EMAIL PROTECTED]> on 03/06/2003 11:30:31 PM
Please respond to [EMAIL PROTECTED]
To: Prince John/in2/[EMAIL PROTECTED]
cc:
Subject: Re: [Alsa-devel] ALSA driver for AD1881 ?
hi,
For controlling the ac97 registers, use the ac97 code
Hi,
I have a Hitachi SH4 based evaluation board with an AD1881 codec (onboard). It
is an AC'97 compliant codec. I'm in need of an ALSA driver for the same. Is
there an ALSA driver already available for AD1881? If not where should I start
to develop a driver for it? I have gone through the Documen
At Thu, 12 Sep 2002 17:10:44 +0100,
Ian Grant wrote:
>
> > At Thu, 12 Sep 2002 16:23:56 +0100,
> > Ian Grant wrote:
> > >
> > > Here is a patch for the toplevel Makefile to remove the $DESTDIR from the path
> > > of the System.map file where we check for its existence. This makes the
> > > exi
> At Thu, 12 Sep 2002 16:23:56 +0100,
> Ian Grant wrote:
> >
> > Here is a patch for the toplevel Makefile to remove the $DESTDIR from the path
> > of the System.map file where we check for its existence. This makes the
> > existence check test the same file location as is used in the subsequen
At Thu, 12 Sep 2002 16:23:56 +0100,
Ian Grant wrote:
>
> Here is a patch for the toplevel Makefile to remove the $DESTDIR from the path
> of the System.map file where we check for its existence. This makes the
> existence check test the same file location as is used in the subsequent -F
> opti
Hello ALSA people
Thanks for making ALSA.
Here is a patch for the toplevel Makefile to remove the $DESTDIR from the path
of the System.map file where we check for its existence. This makes the
existence check test the same file location as is used in the subsequent -F
option to depmod. It wor
>Recently I started to collect some info on how to make a ALSA driver for
>the Digigram VXpocket V2. Digigram decided to provide information
>this PCMCIA card, on condition that a moderator is the single point of
>contact with Digigram.
glad they came to their senses. the existence of the RME Ham
On Mon, Aug 19, 2002 at 09:37:12PM +0200, Fred Jan Kraan wrote:
> Recently I started to collect some info on how to make a ALSA driver for
> the Digigram VXpocket V2. Digigram decided to provide information
> this PCMCIA card, on condition that a moderator is the single point of
> contact with Dig
Recently I started to collect some info on how to make a ALSA driver for
the Digigram VXpocket V2. Digigram decided to provide information
this PCMCIA card, on condition that a moderator is the single point of
contact with Digigram.
A driver for the VXpocket should interface with the PCMCIA module
>Im a User of the 24 I/O-Channel Interface motu2408 for mac and PC.
>I am trying to get startet with sound programs on Linux. The biggest =
>difficulty is,=20
>that there is no support for the mentioned audio interface under linux.
>Mark of the unicorn answered to a real friendly mail of mine the
Hello!
Maybe I've not found the correct Email adress for
this. I'm sorry for that.
Im a User of the 24 I/O-Channel Interface motu2408
for mac and PC.
I am trying to get startet with sound programs on
Linux. The biggest difficulty is,
that there is no support for the mentioned audio
interfac
On Wed, 27 Mar 2002, Mark Cooke wrote:
> Hi everyone,
>
> Just to note that the buildrpm script / cvscompile is currently
> failing on x86 for the uda1341.c (ARM-specific) module.
>
> gcc -E -M -DALSA_BUILD -D__KERNEL__ -DMODULE=1
> -I/var/BUILD/alsa-driver-0.9.0beta12/include
> -I/lib/modul
Hi everyone,
Just to note that the buildrpm script / cvscompile is currently
failing on x86 for the uda1341.c (ARM-specific) module.
gcc -E -M -DALSA_BUILD -D__KERNEL__ -DMODULE=1
-I/var/BUILD/alsa-driver-0.9.0beta12/include
-I/lib/modules/2.4.18-19pre4ac2c1/build/include -O2
-mpreferred-sta
I made the latest CVS and sbawe failed to insmod. Tracking down the
missing definition led me to hwdep.o, which is from alsa-kernel/core
Adding the hwdep.o to the Makefile corrects the insmod failure.
Please let me know if I misunderstand. I am making in alsa-driver which
includes the ../../alsa
I have a twister integrated chipset on a hp zt1180 laptop.
This chipset uses the VIA VT82C686A for the sound but neither the linux
or the alsa driver works.
The mixer seems to works fine but when I try to play sound it just
repeat something that seems to be the really start of the song.
I use lin
On Wed, 28 Nov 2001, [iso-8859-1] Jörn Nettingsmeier wrote:
> it says:
> make: No rule to make target
> /usr/src/linux/include/linux/hostfs_fs_i.h
>
> cvs was pulled yesterday and 5 mins ago, same problem.
> sorry i don't have the time right now to investigate whether this is
> an omission in the
it says:
make: No rule to make target
/usr/src/linux/include/linux/hostfs_fs_i.h
cvs was pulled yesterday and 5 mins ago, same problem.
sorry i don't have the time right now to investigate whether this is
an omission in the kernel tree, so i'm just posting here fyi.
the kernel boots and runs fine
92 matches
Mail list logo
