From: Martin Langer <martin-langer@gmx.de>
To: Martin Shepherd <mcs@astro.caltech.edu>
Cc: Karsten Wiese <annabellesgarden@yahoo.de>, alsa-devel@alsa-project.org
Subject: Re: Using the usx2y driver under Fedora Core 5.
Date: Tue, 16 May 2006 14:42:52 +0200 [thread overview]
Message-ID: <20060516124252.GA5210@tuba> (raw)
In-Reply-To: <Pine.LNX.4.63.0605160318130.13214@goblin.caltech.edu>
On Tue, May 16, 2006 at 03:39:20AM -0700, Martin Shepherd wrote:
> I'm not sure if you are the appropriate person to send this to. If
> not, could you please tell me whom I should contact.
I think alsa-devel is a good choice. Well, let's knock at the doors of
the alsa headquarter now :)
> I've just got my Tascam US-122 box working with the us2xy driver,
> under Fedora Core 5. Since FC5 doesn't come with /sbin/hotplug etc,
> and the installation procedure of the alsa-firmware package from
> alsa-project.org, incorrectly assumes that hotplug is there, I decided
> to try to figure out how to configure udev to auto-load both the first
> and second stage firmware of the US-122, without needing to install
> the obsolete hotplug facility. This worked, and having done so, I now
> don't have to do anything except plug in the USB cable of the US-122
> into my latop, and wait a few seconds for the USB LED on the US-122 to
> light, before I can use the box.
>
> In case you are interested, I have documented everything that I did,
> at the following URL.
>
> http://www.astro.caltech.edu/~mcs/tascam_us122/index.html
>
> Obviously it would be nice to get the UDEV configuration into the
> standard ALSA build procedure (to be used when /sbin/hotplug is
> absent, and /etc/udev/rules.d is present). Is this something that you
> would like to do, or is there somebody else that I should contact? If
> the best thing would be for me to put together a patch against the
> alsa code, could you tell me how I should go about submitting this?
Please send further questions/patches to the alsa-devel mailling list.
( I'm a little bit out of sync with the latest alsa development at the
moment, especially UDEV. )
For me it's a nice idea. We should add some US-224/428 support, too.
Which means to add some ID's and an us428control command. But
unfortunately I have no 224/428 for testing, only a 122 and I just read
that it's already known to work.
Martin
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
parent reply other threads:[~2006-05-16 12:38 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <Pine.LNX.4.63.0605160318130.13214@goblin.caltech.edu>]
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=20060516124252.GA5210@tuba \
--to=martin-langer@gmx.de \
--cc=alsa-devel@alsa-project.org \
--cc=annabellesgarden@yahoo.de \
--cc=mcs@astro.caltech.edu \
/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.