Re: [alsa-devel] hdsp rpm support
Hi Flo
That's great news! Unfortunately, I don't have the unit yet so I'm unable to test it for you. However, I'm sure Roman would be very happy to give it a go. Roman?
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?
Also, did you use the new patched version of the firmware that Karl worked on?
And, when do you think the driver will be incorporated into the main Alsa code branch?
Thanks for your work!
Regards, Martin
On Tue, May 27, 2008 at 1:30 AM, faber@faberman.de wrote:
Martin,
Nice to hear from you. I saw your other posts and had wondered if you
had
chucked in the towel. I would really like to see the RPM supported as it suits my needs exactly.
RPM support is finished, I just need more time for the new userspace tools (new totalmix etc.).
If you want to test the new driver, drop me a note.
Flo
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.
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?
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).
Flo
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
Martin,
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."
With the hdsp*-tools that are currently part of the alsa-tools suite, you cannot control the RPM. Neither can you control a lot of the other RME cards. That's going to change with a whole new set of userspace tools.
So, if you are curious, I can give you the new driver and a small command line program that enables the RPM io box (which is on bypass mode by default). Or you wait until I finished the new user space tools..
Flo
Hi Flo
On Tue, May 27, 2008 at 11:08 PM, Florian Faber faber@faberman.de wrote:
Martin,
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."
With the hdsp*-tools that are currently part of the alsa-tools suite, you cannot control the RPM. Neither can you control a lot of the other RME cards. That's going to change with a whole new set of userspace tools.
So, if you are curious, I can give you the new driver and a small command line program that enables the RPM io box (which is on bypass mode by default). Or you wait until I finished the new user space tools..
Thanks for the clarification and, yes, I'd be interested in having a look at the new driver - if you don't mind sending it to me that would be great.
Karl seemed to be patching the firmware for some reason - I don't know why. As Roman points out, the firmware is operating system independent.
I'm still a little unclear as to what actually can be done with the box at the moment. If the firmware loader (under Linux) is not ready, I'm unclear as to what the RPM can do without the firmware.
At the risk of wasting your time with my questions (and drawing you away from your work), when you say a "small command line program that enables the RPM io box (which is on bypass mode by default)", does this mean that you can plug in a mic/headphone and get them both amplified and sent/received to/from the RME PCI board? But if that's the case, I thought that was really all the RPM box did anyway??
So, when you say "everything works as you would expect it", I'm a little unclear how that would be the case without any firmware loaded??
Sorry, but it would be nice to know what can actually be done/not done as it stands at the moment.
Regards, Martin
On Tue, 2008-05-27 at 22:59 +1000, Martin Tufnel wrote:
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.
this is exactly what i do. it's no problem, though, to turn off the computer after having sent the firmware from within windows, but as soon as i power off the rpm, i need to do the process again. this works well for me, since most of the time the rpm is sitting home powered on, so i can plug it to the laptop and it works.
correct me if i am wrong, but i thought the problem is not the firmware itself, or the fact that it is missing, but the (old) version of the hdsploader i used to use only knows about the multiface and the digiface, but not about the rpm, AFAIK. from what i know, the very same firmware, that is used in windows, can be used in linux as well (since its card specific and not os-specific), but as flo suggested, the userspace tools need to be adapted.
with the old hdsp* stuff, it technically works, but the hdspmixer looks like i'd be using a multiface (it shows more channels than the rpm actually has) and also the hdspconf shows the switches for the mutliface. some card settings can be changed anyway, but you need to guess, what is what, since the labels are bogus (for use with the rpm).
i hope i didn't confuse anyone with my old posts. those describe only the kludges, i am using with old alsa-drives, until the final driver and userspace tools are written.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Hi Roman
On Tue, May 27, 2008 at 11:46 PM, Roman Haefeli reduzierer@yahoo.de wrote:
On Tue, 2008-05-27 at 22:59 +1000, Martin Tufnel wrote:
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.
this is exactly what i do. it's no problem, though, to turn off the computer after having sent the firmware from within windows, but as soon as i power off the rpm, i need to do the process again. this works well for me, since most of the time the rpm is sitting home powered on, so i can plug it to the laptop and it works.
correct me if i am wrong, but i thought the problem is not the firmware itself, or the fact that it is missing, but the (old) version of the hdsploader i used to use only knows about the multiface and the digiface, but not about the rpm, AFAIK. from what i know, the very same firmware, that is used in windows, can be used in linux as well (since its card specific and not os-specific), but as flo suggested, the userspace tools need to be adapted.
with the old hdsp* stuff, it technically works, but the hdspmixer looks like i'd be using a multiface (it shows more channels than the rpm actually has) and also the hdspconf shows the switches for the mutliface. some card settings can be changed anyway, but you need to guess, what is what, since the labels are bogus (for use with the rpm).
i hope i didn't confuse anyone with my old posts. those describe only the kludges, i am using with old alsa-drives, until the final driver and userspace tools are written.
roman
Thanks for the clarification. This information is important to me because, as I've said previously, I don't have a Windows box, so I can't use your work-around.
Regards, Martin
Hi, just a word of clarification:
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?
I didn't patch the firmware - I just copied the firmware from a Win2k driver (ver. 1.1) from the rme website - the linux firmware is the one that came with the win 98 drivers, and there is no firmware for the rpm. My hope was that someone might be able to verify that these firmware files work with the multiface/digiface and the current linux drivers (if this had been the case, it would have made things a bit easier for me, but now that Florian is doing things that I only could dream of, there's no need for me to continue my inferior efforts).
Looking forward... Karl
On Tue, 2008-05-27 at 13:00 +1000, Martin Tufnel wrote:
Hi Flo
That's great news! Unfortunately, I don't have the unit yet so I'm unable to test it for you. However, I'm sure Roman would be very happy to give it a go. Roman?
i will be quite busy, until i will have finished my studies during the first week of june. but then i will be happy to update my old ubuntu dapper box and try the new alsa drivers. i'll give you a report, as soon as i am ready.
roman
___________________________________________________________ Telefonate ohne weitere Kosten vom PC zum PC: http://messenger.yahoo.de
Great Roman - thanks very much! Look forward to it.
Regards, Martin
On Tue, May 27, 2008 at 9:45 PM, Roman Haefeli reduzierer@yahoo.de wrote:
On Tue, 2008-05-27 at 13:00 +1000, Martin Tufnel wrote:
Hi Flo
That's great news! Unfortunately, I don't have the unit yet so I'm
unable
to test it for you. However, I'm sure Roman would be very happy to give
it
a go. Roman?
i will be quite busy, until i will have finished my studies during the first week of june. but then i will be happy to update my old ubuntu dapper box and try the new alsa drivers. i'll give you a report, as soon as i am ready.
roman
participants (4)
-
Florian Faber -
Karl Grill -
Martin Tufnel -
Roman Haefeli