Index: usb/usbmidi.c
===
RCS file: /cvsroot/alsa/alsa-kernel/usb/usbmidi.c,v
retrieving revision 1.1
diff -u -r1.1 usbmidi.c
--- usb/usbmidi.c 14 Aug 2002 17:22:18 - 1.1
+++ usb/usbmidi.c 15 Aug 2002 07:48:59
Eric Griffis wrote:
Hello, people. I've been lurking on this list for a few months and, now
that I have a local linux machine to develop on, am going to horn in and
ask silly questions from time to time.
A month or two ago, I recall a thread regarding attempts to get driver
specs for
Pedro Lopez-Cabanillas wrote:
El Mar 13 Ago 2002 17:01, Patrick Shirkey escribió:
Clemens Ladisch wrote:
I didn't bother to report USB MIDI devices - until now:
Thanks. I'm collecting them for now until I or Dan get the energy to add
them to the matrix.
The usb generic instructions for
Clemens Ladisch wrote:
Patrick Shirkey wrote:
Thanks. I'm collecting them for now until I or Dan get the energy to add
them to the matrix.
Wouldn't it be helpful to make the matrix Open Source(TM) in order to
be able to submit a patch/SQL script/whatever?
The matrix page is html
hey,
on http://hal9000.drehmoment.org/tascam/ you can download a patch against
cvs of august 14.
it contains:
- snd-usb-us428
downloads firmware to endpoint 2.
creates 2 midi devices through the patched snd-usb-midi
and 2 input + 1 output pcm devices.
- snd-usb-midi with exports
same
Pedro Lopez-Cabanillas wrote:
I would like to insist again about including EZ-USB in the chipset column
for these devices:
Midiman Midisport NxN
Midiman USB Keystations:
http://www.midiman.net/products/midiman/keystations.php
Steinberg USB-MIDI-2 adaptor:
Hi,
applied now. thanks.
Takashi
---
This sf.net email is sponsored by: OSDN - Tired of that same old
cell phone? Get a new here for FREE!
https://www.inphonic.com/r.asp?r=sourceforge1refcode1=vs3390
At Thu, 15 Aug 2002 17:38:55 +0900,
Patrick Shirkey wrote:
Eric Griffis wrote:
Hello, people. I've been lurking on this list for a few months and, now
that I have a local linux machine to develop on, am going to horn in and
ask silly questions from time to time.
A month or two
At Tue, 13 Aug 2002 16:24:07 +0800,
Richard Liu wrote:
Hi.
We don't announce this driver to end user. So you cannot download it
from our website.
Here is patch file, thank for your help.
thanks, now it's on cvs, so will be included in the next tarball
release.
Takashi
Patrick Shirkey wrote:
Clemens Ladisch wrote:
Wouldn't it be helpful to make the matrix Open Source(TM) in order to
be able to submit a patch/SQL script/whatever?
The matrix page is html (apart from the edit date) so you can just view
the source and make a patch from that which I will add
At Wed, 14 Aug 2002 18:02:08 +0200 (CEST),
Jaroslav wrote:
I'll finish C99 struct initializers in the meantime.
i finished the rest of drivers on alsa-driver.
still anything missing?
Takashi
---
This sf.net email is sponsored by: OSDN -
Hi Karsten,
i didn't still take a deep look at the patch, so below is just a short
impression:
At Thu, 15 Aug 2002 11:17:37 +0200,
Karsten Wiese wrote:
hey,
on http://hal9000.drehmoment.org/tascam/ you can download a patch against
cvs of august 14.
the usb stuff was moved to alsa-kernel
Hi,
how about to gather the bugs of the current driver and list them as
known bugs on the web?
it would be nice to see such things on alsa or wiki's card page,
so that users can know that you are not alone :)
known bugs i know of (and am working on) are:
OSS emulation
- Wine OSS (mmap) is not
El Jue 15 Ago 2002 10:56, Patrick Shirkey escribió:
Currently I am trying to maintain as few pages as possible so the
generic instructions access exactly the same data as ezusb devices.
However I have made the ezusb instructions more recognisable.
If this is still too confusing then I will
Takashi Iwai wrote:
Hi,
how about to gather the bugs of the current driver and list them as
known bugs on the web?
it would be nice to see such things on alsa or wiki's card page,
so that users can know that you are not alone :)
Done. There is a link ot hte page in the matrix and any
known bugs i know of (and am working on) are:
hdsp
- cold+warm boot required to get output working
- 96kHz and 88.2kHz not accessible via PCM interface
rme9652
- 96kHz and 88.2kHz not accessible via PCM interface
wavefront
- cs4232 PCM output does not work at all (produces white
At Fri, 16 Aug 2002 00:46:02 +0900,
Patrick Shirkey wrote:
Takashi Iwai wrote:
Hi,
how about to gather the bugs of the current driver and list them as
known bugs on the web?
it would be nice to see such things on alsa or wiki's card page,
so that users can know that you are not
Hello All,
I have a small problem that I cant figure out. Basically, on startup I'm
having
my sequencer run through the alsa clients with snd_seq_query_next_client()
and
snd_seq_query_next_port(). I look for clients with
SND_SEQ_PORT_CAP_SUBS_WRITE for
output and SND_SEQ_PORT_CAP_SUBS_READ
gcc -DALSA_BUILD -D__KERNEL__ -DMODULE=1 -I/usr/src/alsa-driver-0.9.0rc3/include
-I/lib/modules/2.4.19-lowlatency/build/include -O2 -mpreferred-stack-boundary=2
-march=i686 -malign-functions=4 -DLINUX -Wall -Wstrict-prototypes -fomit-frame-pointer
-pipe -DKBUILD_BASENAME=als100 -c -o
Clemens Ladisch wrote:
Patrick Shirkey wrote:
Clemens Ladisch wrote:
Wouldn't it be helpful to make the matrix Open Source(TM) in order to
be able to submit a patch/SQL script/whatever?
The matrix page is html (apart from the edit date) so you can just view
the source and make a patch from
The start of my .asoundrc file is as follows:
pcm.rme9652 {
type hw
card 0
device 0
}
ctl.rme9652 {
type hw
card 0
}
What is the purpose of the ctl.rme9652 declaration? My plugin devices
seem to work without it.
Regards
Kris Modrak
---
Takashi Iwai wrote:
At Fri, 16 Aug 2002 00:46:02 +0900,
Patrick Shirkey wrote:
Takashi Iwai wrote:
Hi,
how about to gather the bugs of the current driver and list them as
known bugs on the web?
it would be nice to see such things on alsa or wiki's card page,
so that users can know that you
Kris Modrak wrote:
The start of my .asoundrc file is as follows:
pcm.rme9652 {
type hw
card 0
device 0
}
ctl.rme9652 {
type hw
card 0
}
What is the purpose of the ctl.rme9652 declaration? My plugin devices
seem to work without it.
It is a configuration for the onboard mixer.
Patrick Shirkey wrote:
Kris Modrak wrote:
The start of my .asoundrc file is as follows:
pcm.rme9652 {
type hw
card 0
device 0
}
ctl.rme9652 {
type hw
card 0
}
What is the purpose of the ctl.rme9652 declaration? My plugin devices
seem to work without it.
It is
sorry for the bandwidth, I just solved my problem.
I didnt realize that you had to call snd_seq_connect_from().
In case anyone was wondering :)
.rob
Hello All,
I have a small problem that I cant figure out. Basically, on startup
I'm having
my sequencer run through the alsa clients
At Wed, 14 Aug 2002 21:13:36 -0700,
Jim wrote:
Unfortunately the i810 driver is one of the undisclosed code family. I
haven't used the nforce so I don't know about it.
I went out looking for information - being from Intel - SURELY it's
documented, and such information is publicly
26 matches
Mail list logo
