From: "Martin Tufnel" <martin.tufnel@gmail.com>
To: Florian Faber <faber@faberman.de>
Cc: alsa-devel@alsa-project.org
Subject: Re: hdsp rpm support
Date: Tue, 27 May 2008 22:59:26 +1000 [thread overview]
Message-ID: <c62722740805270559q6a47d5fq3e3084a995494e1@mail.gmail.com> (raw)
In-Reply-To: <200805270814.36011.faber@faberman.de>
Hi Flo
On Tue, May 27, 2008 at 4:14 PM, Florian Faber <faber@faberman.de> wrote:
> Martin,
>
> > Just to clarify, given the driver is finished but the user tools are
> > still under development, this means that the unit will basically work
> > but not have its full functionality - is this correct?
>
> You have IO, you can adjust the input levels, switch standby and
> disconnect the box. So everything works as you would expect it.
>
Great!
>
> > Also, did you use the new patched version of the firmware that Karl
> > worked on?
>
> No, it's the original firmware. Why would one want to patch it?
>
My understanding from Roman's previous posts was that there was a problem
loading the firmware from within Linux. If I understood him correctly, he
needed to load the fireware from within a Windows boot and then boot into
Linux (without turning off the machine of course). Perhaps I misunderstood
him.
Clearly, you're not suffering from the same problem!
>
> > And, when do you think the driver will be incorporated into the main
> > Alsa code branch?
>
> The driver itself won't help you since the old user space tools don't
> know the io box. You wouldn't be able to upload the firmware, adjust
> the mixer levels etc. (unless you patch the old user space tools, of
> course).
>
I'm sorry, I'm a bit confused here. You said above that "You have IO, you
can adjust the input levels, switch standby and disconnect the box. So
everything works as you would expect it." I'm assuming here that you're
talking about the driver as you said that that was finished. However, what
you've just said above seems to contradict this as it seems you're saying
that you can't do anything with just the driver - you need the user space
tools??
Thanks again for your efforts, Martin
next prev parent reply other threads:[~2008-05-27 12:59 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-26 7:33 hdsp rpm support Martin Tufnel
2008-05-26 8:19 ` Roman Haefeli
2008-05-26 12:27 ` Martin Tufnel
[not found] ` <47321.137.248.1.11.1211815832.squirrel@webmail.naturestudies.eu>
2008-05-27 3:00 ` Martin Tufnel
2008-05-27 6:14 ` Florian Faber
2008-05-27 12:59 ` Martin Tufnel [this message]
2008-05-27 13:08 ` Florian Faber
2008-05-28 12:58 ` Martin Tufnel
2008-05-27 13:46 ` Roman Haefeli
2008-05-28 13:01 ` Martin Tufnel
2008-05-30 16:15 ` Karl Grill
2008-05-27 11:45 ` Roman Haefeli
2008-05-27 13:02 ` Martin Tufnel
-- strict thread matches above, loose matches on Subject: below --
2012-01-18 9:05 Roman Haefeli
2012-01-18 10:26 ` Fons Adriaensen
2012-01-18 10:54 ` Roman Haefeli
2012-02-13 15:06 ` Adrian Knoth
2012-02-14 23:07 ` Roman Haefeli
2012-05-17 13:21 ` Roman Haefeli
2012-12-30 12:09 ` Adrian Knoth
2013-01-24 23:21 ` Roman Haefeli
2012-09-30 23:04 ` Roman Haefeli
2012-10-01 8:05 ` Florian Faber
2012-10-01 20:00 ` Roman Haefeli
2012-11-18 17:30 ` Karl Grill
2012-11-20 7:57 ` Roman Haefeli
2007-12-11 11:21 kgrill
2007-12-11 17:01 ` Roman Haefeli
2008-02-25 7:45 ` Karl Grill
2008-02-25 15:50 ` Roman Haefeli
2008-02-20 13:54 ` Roman Haefeli
2007-12-10 0:48 Roman Haefeli
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=c62722740805270559q6a47d5fq3e3084a995494e1@mail.gmail.com \
--to=martin.tufnel@gmail.com \
--cc=alsa-devel@alsa-project.org \
--cc=faber@faberman.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).