On Mon, May 31, 2004 at 11:26:21PM +0200, JoDaY wrote:
> Martin Langer wrote:
> >On Mon, May 31, 2004 at 05:45:24PM +0200, JoDaY wrote:
> >
> >>Hi all,
> >>
> >>I've 2 install of linux, the first one is the oldest where hotplug
> >>is able to
On Tue, Jun 01, 2004 at 10:39:38AM +0200, Takashi Iwai wrote:
> At Thu, 27 May 2004 21:26:22 +0200,
> Martin Langer wrote:
> >
> >
> > Hi,
> >
> > if someone is interested in a free (I mean GPL) firmware for the Tascam
> > US-X2Y devices I can offer
On Mon, May 31, 2004 at 05:45:24PM +0200, JoDaY wrote:
> Hi all,
>
> I've 2 install of linux, the first one is the oldest where hotplug
> is able to load firmware when I plug a Tascam us-122.
> But if I use snd-usb-usx2y.o (seen in depmod), hotplug is not able to
> load the right firmware... The
Hi,
if someone is interested in a free (I mean GPL) firmware for the Tascam
US-X2Y devices I can offer an open source replacement for the second stage
loader alsa-firmware/usx2yloader/tascam_loader.ihx. All three US-X2Y devices
need this file. But I have only tried it out with an US-122 where it
Hi,
here is a patch with some emu10k1x fixes:
- it adds emu10k1x to the Makefile
- include sound/info.h added
- move snd_iprintf to the right position; it compiles now
- fix typo in snd_iprintf
bye,
martin
--
Living on earth may be expensive,
On Sun, Apr 25, 2004 at 04:21:23PM +0200, Nico Schottelius wrote:
>
> > report here or ALSA BTS.
>
> reported. What is BTS?
ALSA Bug Tracker Sytem:
https://bugtrack.alsa-project.org/alsa-bug/
martin
--
Living on earth may be expensive,
b
This bunch of patches fixes compiler warnings like these one:
pcm_multi.c:646: warning: missing initializer
pcm_multi.c:646: warning: (near initialization for
snd_pcm_multi_ops.poll_revpcm_shm.c:589: warning: missing initializer for
snd_pcm_multi_ops.poll_revents')
But perhaps more interesting v
On Tue, Apr 13, 2004 at 05:41:48PM +0200, Takashi Iwai wrote:
>
> i removed the definitions of PCI_ID_XXX, since they are
> already in the public header. for the 2.4 system we have already a
> local pci-ids.h in alsa-driver/pci/au88x0.
Just noticed that one pci id isn't there...
bye,
martin
I
Index: alsa-firmware/mixartloader/README
===
RCS file: /cvsroot/alsa/alsa-firmware/mixartloader/README,v
retrieving revision 1.1
diff -u -r1.1 README
--- alsa-firmware/mixartloader/README 8 Jan 2004 14:46:20 - 1.1
+++ alsa-
On Mon, Apr 05, 2004 at 06:00:01PM +0200, Clemens Ladisch wrote:
> Patrick Boettcher wrote:
> > I'm using a usbsnoop program to do some basic sniffing. Logs are
> > really big :/.
>
> Try to play some 0.01-seconds wave file, and don't connect any other
> USB devices.
Check the log of the init pha
On Sun, Apr 04, 2004 at 05:46:35PM +0100, Rui Nuno Capela wrote:
> >
> > damned. What's that? A dial-in account for spammers from netcabo.pt???
>
> No dial-in but cable. Netcabo.pt is my ISP, and rncbc.org is just my own
> dynamic DNS domain name, although it's IP address hasn't change for almost
Rui,
damned. What's that? A dial-in account for spammers from netcabo.pt???
Still in hope that you're not the reason for my virus/worm traffic explosion.
Please, don't take it personally. It's only the spam/virus traffic I hate.
The reason, why you are on the IP blacklist is obvious: You are sen
On Thu, Apr 01, 2004 at 11:23:00PM +0200, Jaroslav Kysela wrote:
> On Thu, 1 Apr 2004, Martin Langer wrote:
>
> > It's still there, but this patch will fix it:
> >
> > Index: alsa-driver/usb/Kconfig
> > ===
On Thu, Apr 01, 2004 at 10:12:10AM +0200, Karsten Wiese wrote:
> Am Mittwoch 31 März 2004 20:57 schrieb Martin Langer:
> Yes! rm every file in alsa-driver, re-update from cvs and ./cvscompile.
> There might be a simpler solution though...
Indeed. That solves it :) Thanks.
>
On Wed, Mar 31, 2004 at 09:10:17AM +0200, Jaroslav Kysela wrote:
> On Wed, 31 Mar 2004, Karsten Wiese wrote:
>
> > ..., which is not built.
> > this is for kernel 2.4.
> >
> > /etc/asound/driver_args:
> > --with-cards=via82xx,msnd-pinnacle,usb-audio,usb-usx2y,es1968
> > --with-kernel=/usr/src/li
On Mon, Mar 29, 2004 at 12:34:25PM +0100, Rui Nuno Capela wrote:
>
> My first question goes whether us428control's not recognizing any USx2y
> hardware dependant stuff (hwdep) either on hw:0 or hw:1. I'm almost sure
> that it should be on hw:1 as the US-224 is configured as my second
> soundcard u
Hi,
here are some unimportant README and Kconfig updates for the usb-usx2y driver.
bye,
martin
--
Living on earth may be expensive,
but it includes an annual free trip around the sun.
--- alsa-driver/usb/usx2y/Kconfig.ORIGINAL Fri Mar 19 22:11:10 2004
+++ alsa-driver/usb/usx2y/
Hi,
Tascam has released v3.24 of their windows drivers and the firmware for the
us224 and us428 changed (only EZ-USB), but I found no changes for the us122.
You can find both changed and converted firmware files here:
http://www.langerland.de/us122/usx2y-firmware_v3.24.tar.bz2
Please test!
I h
On Thu, Mar 11, 2004 at 02:27:59PM +0100, Takashi Iwai wrote:
> Hi,
>
> does anyone use the following drivers with a 2.6 kernel successfully?
> if it's confirmed, i'd like to move them to alsa-kernel tree, so that
> they can be submitted to 2.6 linux tree soon.
>
> - snd-usb-usx2y
> - snd-hdspm
>
On Tue, Feb 17, 2004 at 04:34:34PM +0100, Takashi Iwai wrote:
> At Mon, 16 Feb 2004 22:23:52 +0100,
> Martin Langer wrote:
> >
> > I vote for applying both Tascam US-224 patches:
> >
> > http://www.mail-archive.com/[EMAIL PROTECTED]/msg11281.html
> > http://w
Hi,
I vote for applying both Tascam US-224 patches:
http://www.mail-archive.com/[EMAIL PROTECTED]/msg11281.html
http://www.mail-archive.com/[EMAIL PROTECTED]/msg11311.html
David Coulm has reported that the US-224 works now. The US-224 depends
on usx2yloader like the other two guys called us122
On Fri, Feb 06, 2004 at 06:42:15PM +0100, Takashi Iwai wrote:
> At Wed, 28 Jan 2004 19:51:12 -0800 (PST),
> Eliot Blennerhassett wrote:
> >
> > The latest driver for AudioScience cards is available as a patch against ALSA
> > 1.02 from
> >
> > http://www.audioscience.com/internet/download/linux.h
On Tue, Jan 27, 2004 at 12:07:43AM +0100, Martin Langer wrote:
> On Mon, Jan 26, 2004 at 11:20:12AM +0100, Takashi Iwai wrote:
> > At Sat, 24 Jan 2004 01:23:28 +0100,
> > Martin Langer wrote:
> > >
> > > usx2y build by "./configure --with-car
On Sun, Feb 01, 2004 at 01:58:06PM +0100, Karsten Wiese wrote:
> Am Freitag, 30. Januar 2004 21:12 schrieb Martin Langer:
> >
> > I guess it's time to create some official 224 driver/loader patches for
> > Alsa CVS now. Any objections?
>
> You uncommented any se
Hi,
our assumption in the usx2yloader for an US-224 was wrong (the prepad
size differs). I've attached a patch which fix this in alsa-firmware.
Instead of usx2y.prepad (which can be removed now) I've created two new
prepad files for the usx2yloader: us122.prepad, us224.prepad. They should be
cop
On Mon, Jan 26, 2004 at 11:20:12AM +0100, Takashi Iwai wrote:
> At Sat, 24 Jan 2004 01:23:28 +0100,
> Martin Langer wrote:
> >
> > usx2y build by "./configure --with-cards=usb-usx2y" has a dependency problem:
> >
> > depmod: *** Unresolved symbols in
Hi,
usx2y build by "./configure --with-cards=usb-usx2y" has a dependency problem:
depmod: *** Unresolved symbols in
/lib/modules/2.4.23/kernel/sound/usb/usx2y/snd-usb-usx2y.o
depmod: snd_usbmidi_disconnect_Rc1a56322
depmod: snd_hack_usb_set_interface_R5b6905b8
depmod: snd
This will fix a problem with undeclared PCI_DEVICE_ID_VIA_8365_1
Index: alsa-driver/pci/au88x0/au88x0.c
===
RCS file: /cvsroot/alsa/alsa-driver/pci/au88x0/au88x0.c,v
retrieving revision 1.6
diff -u -r1.6 au88x0.c
--- alsa-driver/pci
On Sun, Jan 11, 2004 at 02:49:06PM +0100, Karsten Wiese wrote:
> Am Samstag, 10. Januar 2004 20:27 schrieben Sie:
> >
> > $ ls -l /dev/snd
> > total 0
> > crw-rw1 root audio116, 0 Dec 31 1969 controlC0
> > crw-rw1 root audio116, 32 Dec 31 1969 controlC1
> > crw-
I have two warnings with 2.2. The first one is still not fixed:
pci_compat_22.c: In function snd_pci_compat_release_region':
pci_compat_22.c:384: warning: implicit declaration of function
release_mem_region'
... and the second one needs this fix:
--- pcm_native.c~ Thu Jan 1 22:06:44 20
Hi,
what about removing Config.in and Config.help ?
I saw them in alsa-driver/isa/msnd/ --- Aren't they obsolete since Kconfig?
martin
---
This SF.net email is sponsored by: IBM Linux Tutorials.
Become an expert in LINUX or just sharpen your
Index: alsa-driver/INSTALL
===
RCS file: /cvsroot/alsa/alsa-driver/INSTALL,v
retrieving revision 1.152
diff -u -r1.152 INSTALL
--- alsa-driver/INSTALL 4 Dec 2003 11:51:40 - 1.152
+++ alsa-driver/INSTALL 3 Jan 2004 14:18:40 -0
On Sat, Dec 06, 2003 at 06:15:19PM -0800, Mark Knecht wrote:
>
> Note ADAT3 which do not exist on
> this card.
>
>
> [EMAIL PROTECTED] mark]$ cat /proc/asound/card0/rme9652
[...]
> ADAT Sample rate: 44100Hz
> ADAT1: No Lock
> ADAT2: No Lock
> ADAT3: No Lock
>
This patch will remove the ADAT3
Hi,
in the docs of writing-an-alsa-driver
http://www.alsa-project.org/~iwai/writing-an-alsa-driver/c1396.htm
is snd_info_set_text_ops() used as
snd_info_set_text_ops(entry, chip, my_proc_read);
But the reality of alsa-driver/alsa-kernel/include/info.h says:
static inline void snd_info_set_text_
rename some messages from old us428 names to usX2Y ones.
Index: alsa-driver/usb/usx2y/usX2Yhwdep.c
===
RCS file: /cvsroot/alsa/alsa-driver/usb/usx2y/usX2Yhwdep.c,v
retrieving revision 1.1
diff -u -r1.1 usX2Yhwdep.c
--- alsa-driver/u
Index: alsa-driver/pci/Kconfig
===
RCS file: /cvsroot/alsa/alsa-driver/pci/Kconfig,v
retrieving revision 1.7
diff -u -r1.7 Kconfig
--- alsa-driver/pci/Kconfig 19 Dec 2003 09:19:52 - 1.7
+++ alsa-driver/pci/Kconfig 25 D
On Mon, Dec 22, 2003 at 08:03:39PM +0100, Tim Goetze wrote:
> Martin Langer wrote:
>
> >http://www.evolution.co.uk/products/evo_uc33e.htm
> >
> >BTW: The controller knobs of my Evolution MK-249C are working fine
> >and ALSA has no evolution quirks inside. I don&#x
On Mon, Dec 22, 2003 at 04:12:36PM +0100, Tim Goetze wrote:
> this thing caught my interest:
>
> http://m-audio.com/index.php?do=products.main&ID=2505615704f241ab716639de0db48fef
>
> it's a control surface (faders, knobs etc) and seems to be able to
> act as a MIDI I/O interface when connected vi
On Sun, Dec 21, 2003 at 07:11:17PM +0100, Martin Langer wrote:
>
> Hi,
>
> two small typos in the docs on
> http://www.alsa-project.org/~iwai/writing-an-alsa-driver/x494.htm
>
> There are *playback* labeled functions for open and close:
>
> static snd_pcm_op
Hi,
two small typos in the docs on
http://www.alsa-project.org/~iwai/writing-an-alsa-driver/x494.htm
There are *playback* labeled functions for open and close:
static snd_pcm_ops_t snd_mychip_playback_ops = {
.open =snd_mychip_playback_open,
.close = snd_mychip_playb
On Thu, Dec 18, 2003 at 12:01:24PM -0800, Fernando Pablo Lopez-Lezcano wrote:
> > > I confirm this fact:
> > > with kernel 2.4.23 and alsa 1.0rc2, the module snd-rme9652 can't be loaded
> > > althought the "old" rme digi 9652 is perfectly working with alsa 0.9.6
> >
> > I have found after a lot of
On Sun, Dec 14, 2003 at 06:32:58PM +0900, Patrick Shirkey wrote:
> Could someone send me a list of all the usbmidi devices that require
> firmware to be inserted. I am redesigning the docs for these cards.
>
snd-usb-audio with MidiSport firmware loader:
MidiSport 1x1, 2x2, 4x4, 8x8, KeyStation,
Thank you very much, Patrick for the work you've done until now.
But one point I still miss is some kind of browseable Changelog. And a good
complete changelog history is also good for detecting bugs.
Well, only the users in the mailling lists can know if driver xy has changed
(or maybe improved
On Fri, Dec 05, 2003 at 09:05:53AM +0100, Jaroslav Kysela wrote:
> On Fri, 5 Dec 2003, Karsten Wiese wrote:
>
> > The attached patch against CVS-HEAD does that.
> > Please try it. If us122 works again, ask Jaroslav to commit it, as Takashi is
> > on vacation.
>
> It also slipped to rc2. Thanks.
On Thu, Dec 04, 2003 at 11:02:14PM +0100, Karsten Wiese wrote:
> Am Donnerstag, 4. Dezember 2003 20:30 schrieb Martin Langer:
> >
> > Karsten, your us428 fix breaks us122 support.
> > usX2Y_rate_set(usX2Y_stream, 44100)) isn't possible on us122.
> >
>
> usX
diff -u -r1.1 usbusx2yaudio.c
--- alsa-driver/usb/usx2y/usbusx2yaudio.c 25 Nov 2003 11:21:49 - 1.1
+++ alsa-driver/usb/usx2y/usbusx2yaudio.c 27 Nov 2003 14:32:25 -
@@ -1225,7 +1225,8 @@
sprintf(pcm->name, NAME_ALLCAPS" Audio #%d", usX2Y(card)->chip.pcm_devs);
it would be better to list all prerequisites for usx2yloader somewhere...
martin
--- alsa-tools/usx2yloader/INSTALL.ORIGINAL Wed Dec 3 19:48:55 2003
+++ alsa-tools/usx2yloader/INSTALL Wed Dec 3 19:52:46 2003
@@ -1,3 +1,18 @@
+
+Prerequisites
+-
+
+- a Linux kernel, with U
On Sat, Nov 29, 2003 at 06:10:59PM +0100, JoDaY wrote:
>
> It's ok :) I'm sorry for my bad question ... I should have ask you where
> can I reach the US-122, my problem in fact is that I can't find this
> card in /dev in order to point a sound or midi player to it so that the
> US-122 make nois
On Thu, Nov 27, 2003 at 03:56:36PM +0100, Karsten Wiese wrote:
> Am Donnerstag, 27. November 2003 15:35 schrieb JoDaY:
> >
> > But I can't see it in any mixer: alsamixer return No mixer elems found.
> there is no mixer support yet. but it is certainly implementable ;-)
>
The mixer is implemented
Patrick,
here is a soundcardmatrix patch which creates new Tascam USx2y entries.
bye,
martin
--- matrix.html.ORIGINALWed Nov 26 21:57:55 2003
+++ matrix.html Wed Nov 26 22:24:54 2003
@@ -2790,6 +2790,32 @@
+
+ http://www.tascam.com/";>Tascam
+
+
+ http://www.tascam
On Mon, Nov 24, 2003 at 11:14:02PM +0100, Martin Langer wrote:
> On Mon, Nov 24, 2003 at 09:50:32PM +0100, Werner Schweer wrote:
> > On Monday 24 November 2003 14:37, Karsten Wiese wrote:
> > > Hi,
> > >
> > > would you please give this a try an your us122s?
&
On Mon, Nov 24, 2003 at 09:50:32PM +0100, Werner Schweer wrote:
> On Monday 24 November 2003 14:37, Karsten Wiese wrote:
> > Hi,
> >
> > would you please give this a try an your us122s?
> > I integrated Martins stuff into mine. us428 still works here.
> > besides patching you'll need to copy the at
On Sun, Nov 23, 2003 at 03:45:57PM +0100, Martin Langer wrote:
>
> here is another fix for 2.2 kernels:
>
> --- acore/pci_compat_22.c.ORIGINALSun Nov 23 14:41:21 2003
> +++ acore/pci_compat_22.c.FIX Sun Nov 23 15:38:37 2003
> @@ -371,7 +371,7 @@
> return -EB
here is another fix for 2.2 kernels:
martin
--- acore/pci_compat_22.c.ORIGINAL Sun Nov 23 14:41:21 2003
+++ acore/pci_compat_22.c.FIX Sun Nov 23 15:38:37 2003
@@ -371,7 +371,7 @@
return -EBUSY;
}
-void snd_pci_compat_release_region(struct pci_dev *pci, int bar)
+void snd_pci_c
On Tue, Nov 18, 2003 at 11:09:12AM +0100, Takashi Iwai wrote:
> At Mon, 17 Nov 2003 22:26:54 +0100,
> Martin Langer wrote:
> (snip)
> > > grrr, they don't exist on 2.2 kernels...
> > > we need a wrapper for them.
> > >
> >
> > It's
> >
> > Ok, it's a thing that we would like to eliminate, but when I tried to
> > figure what's going on in the past, I wasn't successful. The best
> > thing to
> > measure if ALSA sends a wrong sample sequence to the output is to use the
> > digital I/O (S/PDIF or profi IEC958) for on playback sid
On Mon, Nov 17, 2003 at 12:08:39PM +0100, Takashi Iwai wrote:
> At Sun, 16 Nov 2003 18:51:17 +0100,
> Martin Langer wrote:
> >
> >
> > Hi,
> >
> > please don't try to build au88x0 on an alpha.
>
> most of problems below are due to 2.2 kernel.
>
On Mon, Nov 17, 2003 at 06:55:29PM +0100, Takashi Iwai wrote:
> At Mon, 17 Nov 2003 12:08:39 +0100,
> I wrote:
> >
> > At Sun, 16 Nov 2003 18:51:17 +0100,
> > Martin Langer wrote:
> > >
> > > gcc -D__KERNEL__ -DMODULE=1 -I/usr/local/src/alsa-cvs/alsa-
Hi,
please don't try to build au88x0 on an alpha. You have to read a lot.
But here is an extract with some quite interesting points about CVS ;-)
martin
gcc -D__KERNEL__ -DMODULE=1 -I/usr/local/src/alsa-cvs/alsa-driver/include
-I/lib/modules/2.2.19/build/include -O2 -mno-fp-regs -ffixed-8 -Wa
On Wed, Nov 12, 2003 at 02:13:34AM -0500, Apostolos Dimitromanolakis wrote:
>
> My mistake.. fixed!
Yes, it's fixed. But I think this patch is better.
martin
--- ../alsa-cvs/alsa-kernel/pci/ice1712/prodigy.c Mon Nov 10 19:00:50 2003
+++ alsa-kernel/pci/ice1712/prodigy.c Wed Nov 12 19
On Sat, Nov 08, 2003 at 08:32:55PM +0100, Jaroslav Kysela wrote:
> On Sat, 8 Nov 2003, Martin Langer wrote:
>
> > On Sat, Nov 08, 2003 at 08:04:43PM +0100, Jaroslav Kysela wrote:
> > > >
> > > > aplay/arecord doesn't work at the moment:
> > > >
On Sat, Nov 08, 2003 at 08:04:43PM +0100, Jaroslav Kysela wrote:
> >
> > aplay/arecord doesn't work at the moment:
> >
> > Playing WAVE '/tmp/test.wav' : Signed 16 bit Little Endian, Rate 44100 Hz,
> > Stereo
> > aplay: set_params:874: Unable to install hw params:
> > ACCESS: RW_INTERLEAVED
>
> C
On Wed, Nov 05, 2003 at 11:47:58AM +0100, Jaroslav Kysela wrote:
>
> I decided to switch to new PCM API (values are returned using an
> indirect pointer rather as return value, so error codes are not mixed with
> values). The binary compatibility is kept. So, you can use old
> applications w
On Mon, Oct 27, 2003 at 12:33:46PM +0100, Takashi Iwai wrote:
> At Tue, 21 Oct 2003 23:52:55 +0200,
> Martin Langer wrote:
> >
> > ... at http://www.langerland.de/us122/driver.html
>
> any chance to merge us122 driver with us428 driver?
> they look quite similar...
On Tue, Oct 21, 2003 at 11:38:36AM +0200, Werner Schweer wrote:
> On Monday 20 October 2003 22:31, you wrote:
> >
> > Nevertheless I will invite other us122 owners: Please try it out!
> >
> > The Tascam US-122 driver v0.12 is available here:
> > http://www.langerland.de/us122/driver.html
>
> funkt
On Fri, Sep 26, 2003 at 11:41:38AM +0200, Takashi Iwai wrote:
> At Thu, 25 Sep 2003 22:46:37 +0200,
> Werner Schweer wrote:
> >
> > Meanwhile i checked the us122 alsa patch from martin-langer
> > (http://www.langerland.de/us122/driver.html) with no effect.
>
Hi,
t
Hi,
fix for us428 plus the prehistoric 2.4.19 kernel.
martin
PS: time for holidays now
--- usbus428.h.ORIGINAL Mon Sep 15 20:43:37 2003
+++ usbus428.h Mon Sep 15 20:49:59 2003
@@ -7,8 +7,10 @@
#define NRURBS 2 /* */
#define NRPACKS1 /* usb-frames/ms
Hi,
gcc -E -C -D__KERNEL__ -DMODULE=1
-I/usr/local/src/alsa-cvs/alsa-driver/include
-I/lib/modules/2.4.19-rc1/build/include -O2 -mpreferred-stack-boundary=2
-march=i686 -malign-functions=4 -DLINUX -Wall -Wstrict-prototypes
-fomit-frame-pointer -Wno-trigraphs -O2 -fno-strict-aliasing -fno-common
-
On Wed, Aug 20, 2003 at 08:29:12PM +0200, Karsten Wiese wrote:
> would you try the us428 audio part on the us122?
Yes, I've tried it out and capturing runs perfect. Playback is ok if you do it
not longer than 5 seconds or so. Then speed becomes slower and sloooweeer
and it sounds terrible croaky
On Sun, Aug 31, 2003 at 12:27:42AM +0200, Pedro Lopez-Cabanillas wrote:
>
> Yes, but it is easier to use the vendor and product id instead of usb dev full
> path. Something like this:
> pre-install snd-usb-us122 /usr/sbin/rbtload -P0x8007 -V0x1604 -p71 -Ius122.rbt
> See the attached patch (untest
On Fri, Aug 29, 2003 at 09:59:13PM +0200, Pedro Lopez-Cabanillas wrote:
>
> We can use something like this for Tascam USB devices:
> pre-install snd-usb-us428 /usr/sbin/rbtload [...]
>
> In this way we can be sure that rbtload is executed *before* the module is
> installed. Of course, we s
Firmware loaders for Midiman and Tascam USB MIDI devices
These packages allow you to use Midiman's MidiSport USB MIDI interfaces and
Tascam's USB Audio interfaces with Linux. These devices require a firmware
download before an operating system driver (e.g. ALSA's snd-usb-audio) can
access them.
On Wed, Aug 20, 2003 at 08:29:12PM +0200, Karsten Wiese wrote:
> Am Mittwoch 20 August 2003 19:58 schrieb Martin Langer:
> >
> > Stupid question: Why do we need synchronisation??
> to avoid crackles in Audio Out. goal: feeding Audio Out exactly as many frames
> as
On Thu, Aug 07, 2003 at 04:44:08PM +0200, Takashi Iwai wrote:
> At Wed, 30 Jul 2003 21:33:37 +0200,
> Karsten Wiese wrote:
> >
> > i agree that its a reasonable goal to integrate the us428 audio part into ALSA
> > usb-audio. is there such a mechanism to syncronize the playback-pipe by the
> > ca
On Sun, Aug 17, 2003 at 12:47:02PM +0200, Thomas Charbonnel wrote:
> >
> > Any documents available about downloading bitstreams into XILINX FPGA's?
> >
> > - vxloader uses it. Which XILINX chip is it?
> > - RME uses XILINX FPGA's since years. I suppose hdsploader is for
> > loading
> > bits into
Any documents available about downloading bitstreams into XILINX FPGA's?
- vxloader uses it. Which XILINX chip is it?
- RME uses XILINX FPGA's since years. I suppose hdsploader is for loading
bits into such a Xilinx FPGA.
Anybody there who saw a Xilinx FPGA on/in his hdsp card?
Which chip
On Thu, Aug 07, 2003 at 04:44:08PM +0200, Takashi Iwai wrote:
> At Wed, 30 Jul 2003 21:33:37 +0200,
> Karsten Wiese wrote:
> >
> > new here is:
> > - both firmware-downloads are handled now by the snd-usb-us428-dl module (this
> > functionality should move further on into userspace via libusb ? v
On Tue, Aug 12, 2003 at 06:38:22PM +0200, Takashi Iwai wrote:
> At Mon, 11 Aug 2003 01:26:09 +0200,
> Martin Langer wrote:
> >
> > I've looked into my US122 and there I've found an EZUSB chip. The US428
> > might be the same.
> >
> > I think the fir
On Wed, Jul 30, 2003 at 09:58:18AM +0200, Clemens Ladisch wrote:
> Martin Langer wrote:
> > looking into usbquirks.h I saw that audio endpoints follow the rule:
> > 0x0... for output
> > 0x8... for input
> > I think that's absolutely ok!
>
>
Hi,
looking into usbquirks.h I saw that audio endpoints follow the rule:
0x0... for output
0x8... for input
I think that's absolutely ok!
And now: If I jump into the usb-midi world and try a similar quirk:
.out_ep = 0x06,
.in_ep = 0x86,
it will end with an "usb_su
On Mon, Jul 28, 2003 at 11:26:59AM +0200, Takashi Iwai wrote:
> At Mon, 28 Jul 2003 10:16:03 +0200,
> Markus Bollinger wrote:
> >
> > [1 ]
> > Sorry,
> > I didnt know that compilers can get angry with [].
>
> i didn't get error with gcc-3.3. perhaps gcc-2.x only...?
>
it's gcc 2.95.4 from deb
Sorry to say,
but CVS doesn't compile! Building the mixart driver fails:
make[3]: Entering directory /usr/local/src/alsa-cvs/alsa-driver/pci/mixart'
gcc -D__KERNEL__ -DMODULE=1 -I/usr/local/src/alsa-cvs/alsa-driver/include
-I/lib/modules/2.4.19-rc1/build/include -O2 -mpreferred-stack-boundary=2
On Sat, Jul 05, 2003 at 12:44:52PM -0600, ljp wrote:
> >
> > - The US-122 was developed by Frontier Design, not Tascam. But for releasing
> > their information they need an ok from Tascam. Don't know what will happen
> > in this point. In the meantime I've taken an USB sniffer and check my postbox
Hi,
anybody interested in an USB firmware loader patch for the Tascam US-122?...
http://langerland.de/us122/alsacvs-us122-0.6.patch.gz
some remarks:
- The US-122 was developed by Frontier Design, not Tascam. But for releasing
their information they need an ok from Tascam. Don't know what will
On Wed, Jul 02, 2003 at 12:57:05PM +0200, Takashi Iwai wrote:
>
> hdspconf is tagged as version 1.0, and rmedigicontrol 0.3.5a.
> if you have newer versions, please let me know.
correct! rmedigicontrol 0.3.5a is the newest one.
martin
---
Th
On Tue, Jun 10, 2003 at 01:56:55PM -0400, Paul Davis wrote:
> >Is this is a design flaw? How to tell the input frequency? Need some
> >additionnal hardware?
>
> the ALSA h/w parameters are things set by an application (and
> perhaps later read by the same or a different application).
>
> what A
On Tue, Jun 10, 2003 at 12:24:21PM -0400, Paul Davis wrote:
> >I'm using a digital Hammerfall audio card and was wondering how to
>
> which hammerfall? digi9652 or hdsp9652?
>
> >figure out the sample rate of the ADAT input pcm stream (which can vary
> >from 32kHZ to 96kHZ). I tried functions l
On Fri, Jun 06, 2003 at 12:06:33PM +0200, Gorm David Lai wrote:
> On Thu, 2003-06-05 at 21:03, Martin Langer wrote:
> > On Thu, Jun 05, 2003 at 12:17:32PM +0200, Gorm David Lai wrote:
> > >
> > > We have recently bought a RME Digi96/8 card. This connects via ada
On Thu, Jun 05, 2003 at 12:17:32PM +0200, Gorm David Lai wrote:
> Hi, I really hope somebody can help me.
>
> We have recently bought a RME Digi96/8 card. This connects via adat to a
> mixing console.
> I have implemented the code in the ALSA 0.9.0 HOWTO for playback. This
> works fine on a sound
On Sun, Jun 01, 2003 at 12:27:11PM +0200, Clemens Ladisch wrote:
>
> on Slackware 8.0:
>
> $ gcc --version
> 2.95.3
> $ ./configure
> ...
> checking for GCC version... Kernel compiler: gcc 2.95.3 20010315 (release) Used
> compiler: 2.95.3
> Fatal error: Compiler type does not match
> Decoded ker
On Sun, Mar 23, 2003 at 04:05:30PM +0100, PIETER PALMERS wrote:
> The best starting point is gathering info. Without good info, developement isn't
> easy. But you seem to be lucky, because I found the following on the website of
> Marian (www.marian.de):
> "Developers of drivers can obtain all info
On Wed, Mar 19, 2003 at 01:10:02PM -0500, Paul Davis wrote:
> there still appears to be a bug in the trident driver. i have been
> running jack with a period size of 1024, and it works fine. when i
> change that to 4096 frames, the kernel does a hard oops, with the oops
> occuring in enable_hlt().
On Mon, Mar 17, 2003 at 02:15:14PM +0200, Andrei Boros wrote:
>
> checking for kenrel linux/spinlock.h... yes
> ^^
--- alsa-driver/configure.in.ORIGINAL Mon Mar 17 14:01:44 2003
+++ alsa-driver/configure.inMon Mar 17 14:02:17 2003
@@ -151,7 +151,7 @@
AC_MSG_RESULT($kaversi
On Tue, Mar 11, 2003 at 02:02:51PM +0100, Takashi Iwai wrote:
> > On Tue, Mar 11, 2003 at 11:14:43AM +0100, Takashi Iwai wrote:
> > >
> > > IIRC, the -falign-xxx is a new option and the older compiler had
> > > -malign-xxx instead. could you check the attached patch whether it
> > > works?
>
> m
On Tue, Mar 11, 2003 at 11:14:43AM +0100, Takashi Iwai wrote:
> At Sat, 8 Mar 2003 23:44:27 +0100,
> Martin Langer wrote:
> >
> > On Sat, Mar 08, 2003 at 10:40:52AM +0100, Martin Langer wrote:
> > > On Sat, Mar 08, 2003 at 10:11:24AM +0100, Martin Langer wrote:
> &g
On Sat, Mar 08, 2003 at 10:40:52AM +0100, Martin Langer wrote:
> On Sat, Mar 08, 2003 at 10:11:24AM +0100, Martin Langer wrote:
> > On Sat, Mar 08, 2003 at 10:51:29AM +0200, Panagiotis Papadakos wrote:
> >
> > > cc1: Invalid option `-falign-functions=4'
Removing t
On Sat, Mar 08, 2003 at 10:11:24AM +0100, Martin Langer wrote:
> On Sat, Mar 08, 2003 at 10:51:29AM +0200, Panagiotis Papadakos wrote:
>
> same with gcc 2.95.4!
> >
> > gcc -M -D__KERNEL__ -DMODULE=1
> > -I/mnt/disk/CVS/ALSA-CVS/alsa-driver/include
> > -I/lib/modu
On Sat, Mar 08, 2003 at 10:51:29AM +0200, Panagiotis Papadakos wrote:
> I get the following error:
same with gcc 2.95.4!
martin
>
> gcc -M -D__KERNEL__ -DMODULE=1
> -I/mnt/disk/CVS/ALSA-CVS/alsa-driver/include
> -I/lib/modules/2.4.21-pre5-ac2/build/include -O2
> -mpreferred-stack-boundary=2 -m
On Fri, Mar 07, 2003 at 04:44:55PM +0100, Clemens Ladisch wrote:
> Jaroslav Kysela wrote:
> > [...]
> > The whole idea is that the jack module should not be built by default.
> > Unfortunately, it seems difficult to redirect the build targets from
> > automake for different versions.
>
> The autom
Hi,
using latest CVS on a jack-free system produces a lot of output. I've never
saw that before during "make build". For me it looks like a consequence of
moving jack plugin to a new directory.
martin
make[4]: Entering directory /usr/local/src/alsa-cvs/alsa-lib/src/pcm/ext'
/bin/sh ../../../li
1 - 100 of 158 matches
Mail list logo
