25 Aug
2004
25 Aug
'04
11:22 a.m.
Why is it so important to load the firmware?
Do they put in an extra light firmware at the factory, in order to keep
shipping weights low? <gr>
Or is it just that they are actually continuously working on it after
product release? (which may be a good thing - unless a product is rushed
out hastily and then requires fixes to make it work at all...)
Chris
BTW - I found a nice overview at http://www.alsa-project.org/alsa-doc/ ,
comparing lots of cards and their Linux driver situation. That list
appears to be more honest than any hardware sales guy could ever be...
THX for all your replies :-)
On Wed, 25 Aug 2004 10:11:10 -0400 Paul Winkler wrote:
On Wed, Aug 25, 2004 at 09:13:05AM +0200, Clemens
Ladisch wrote:
Paul Winkler wrote:
Yes, sorry I forgot to make that distinction.
I had the same experience with my Oxygen - works fine once you've
dug around the net and figured out how to load the #@()% firmware.
--
Paul Winkler
http://www.slinkp.com On Tue, Aug 24, 2004 at 04:23:10PM +0200, Clemens
Ladisch wrote:
The MidiSport MIDI interfaces work just fine (once you have managed to
get the firmware and to install the firmware loader). It's the audio
interfaces that have (rather major) "issues". The snd-usb-audio driver currently supports
multiport USB
interfaces from ESI/Edirol/Roland/M-Audio/Yamaha.
Note that others have reported issues with the M-audio usb devices.