All of lore.kernel.org
 help / color / mirror / Atom feed
From: Takashi Iwai <tiwai@suse.de>
To: Karsten Wiese <annabellesgarden@yahoo.de>
Cc: alsa-devel@lists.sourceforge.net
Subject: Re: Fwd: [usb-midi-fw-devel] proposal concerning cooperation of snd-usb-usx2x.o and rbtload
Date: Fri, 29 Aug 2003 18:28:50 +0200	[thread overview]
Message-ID: <s5hoey8qvgd.wl@alsa2.suse.de> (raw)
In-Reply-To: <200308291329.17781.annabellesgarden@yahoo.de>

Hi Karsten,

At Fri, 29 Aug 2003 13:29:17 +0200,
Karsten Wiese wrote:
> 
> [1  <text/plain; us-ascii (7bit)>]
> hi,
> please check the hotplug strategy outlined in the forward.
> If it's ok, i'll prepare a next patch based on what is in the forward.
(snip)
> hi colegas,
> 
> have been trying the 0.1 and yes, the fpga code does it also for us428 !
> concerning cooperation of snd-usb-us428.o and rbtload i've implemented a  
> hack:
> when a hotplug occurs (EZUSB Firmware not being looked at here, works as 
> before), the kernel 
> 1.) asks snd-usb-us428.o, if it wants to have the device. snd-usb-us428.o says 
> 'yes!'. this latest snd-usb-us428.o will not start any ALSA-Activity in this 
> stage. It just owns the interface to the us428 (and implements 2 new 
> ioctl-able entriepoints).

hmm, what would be a gain by using ioctl?


> 2.) starts rbtload (by means of the hotplug-scripts) to download the fpga 
> code. this hacked rbtload does the download by means of standard ioctl() - 
> calls to snd-usb-us428.o. Thus we don't need libusb here anymore. (libusb is 
> still used here for minimizing changing efforts.) if download is finished, 
> snd-usb-us428.o ALSA-Activities are started by another ioctl to 
> snd-usb-us428.o.

you can create a hwdep device in the probe callback of snd-usb-us428,
and later create pcm and mixer devices dynamically after the firmware
is loaded.
this method is used in some other drivers like vx drivers.
you can use own mmap and ioctl for this device, too, if you want.

> 
> Result: us428 works as before.
> 
> What do you think about setting up a 0.2 this way? 
> 
> If you might wonder why snd-usb-us428 is still seperate from snd-usb-audio:
> - us428 (and possibly usx2x) use a non standard way of synching audio in & 
> out.

this is ok, we can merge later.

> - us428 and us224 (don't know about us122) have those knobs & sliders. they 
> are also special.

can't you implement these as standard mixer elements?
then all mixer programs can access them.


thanks,

Takashi


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf

      reply	other threads:[~2003-08-29 16:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-29 11:29 Fwd: [usb-midi-fw-devel] proposal concerning cooperation of snd-usb-usx2x.o and rbtload Karsten Wiese
2003-08-29 16:28 ` Takashi Iwai [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=s5hoey8qvgd.wl@alsa2.suse.de \
    --to=tiwai@suse.de \
    --cc=alsa-devel@lists.sourceforge.net \
    --cc=annabellesgarden@yahoo.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.