At Tue, 20 Aug 2002 10:41:52 +0200,
Clemens Ladisch wrote:
> 
> karsten wiese wrote:
> > Takashi Iwai <[EMAIL PROTECTED]> wrote:
> > > i think we need rather rewrite the top of usb device
> > > management (on
> > > alsa).  there is also another problem in this
> > > regard, for example,
> > > a device with both midi and audio is assigned to two
> > > different cards,
> > > since midi and audio handles it individually.
> > 
> > the patch adresses just that.
> > ...
> > Would it be sufficient to add an extra function like
> > snd_usbmidi_card_attach() instead of overloading
> > snd_usbmidi_card_create()?
> 
> This two-cards problem should be fixed for all USB devices,
> not only for the Tascam. Then it wouldn't be necessary
> to have special code for the MIDI part of the US428 at all.
> 
> I'm looking into this. usbaudio.c needs a function similar to
> snd_usb_create_pcm(), but creating a sequencer device for
> MIDI streaming interfaces. The sequencer device driver would
> still be a separate module, but doesn't need to create
> another card anymore.
 
that's also what i thought of.
we can make a common "base" module for managing the card (according to
the usb_device struct?).


> > > (BTW, could you check the legal condition of
> > > firmware on tascam
> > >  device?  i'd like to put the stuffs but without
> > > this permission it's
> > >  of course unacceptable...)
> > 
> > what exactly do you need? I once tried to get an
> > answer from turtle beach,
> > which did not happen...
> > tascam will most likely not agree to release the
> > firmware under GPL in any form nor object- nor
> > source-code.
> > is it sufficient, if tascam just allows ALSA to use &
> > publish their firmware as it is now?

if it's not allowed from the tascam, we cannot distribute the file nor
(binary) data in our package.  the workaround is to fetch the external
firmware file somehow as well as msnd driver does.


> I don't think they will allow their firmware to be
> distributed with ALSA. (GPL requires to publish the
> source.)
 
it's possible to distribute the binary firmware as it is.
in most cases, the firmware is regarded as "data", not a program.
(otherwise no hardware vendor will give it :)


> The Turtle Beach MultiSound driver uploads DSP code
> from files installed with the Windows driver.
> It may be possible to do the same for the US428.

yes, in the case of usb, it should be more easier than msnd driver,
since the access to usb device is possible from the userspace, too.


ciao,

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=sourceforge1&refcode1=vs3390
_______________________________________________
Alsa-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/alsa-devel

Reply via email to