[alsa-devel] [PATCH] - Fix Fast Track Ultra series: 44.1/88.1 kHz 1/Fix playback/capture issues and related crashes at 44100 Hz and 88200 Hz for M-Audio Fast Track Ultra series.

[Paul Menzel]

Dear Felix,


Am Dienstag, den 31.08.2010, 08:39 +0200 schrieb Felix Homann:

> almost 2 months ago I send a patch making the M-Audio Fast Track Ultra 
> series audio interfaces work flawlessly in Linux except for missing 
> mixer support:

for people having subscribe later or deleted the last messages, you can
find Felix’s message in the archive [1]. I could not download the
attachment though, so please try [2] instead.

> Am 06.07.2010 10:05, schrieb Felix Homann:
> > This fixes issues with M-Audio's Fast Track Ultra series:
> >
> > * devices now work at 44100 and 88200 Hz
> > * apparently, fixes some crashes, too
> 
> Unfortunately, the patch didn't make it into Alsa so far. Clemens 
> Ladisch seemed reluctant to apply a fixed endpoint quirk since the 
> device should have worked without in his opinion. I gave him all the 
> requested information to see what was happening without the fixed 
> endpoint quirk. I never heard back from him again.
> 
> So, could someone in charge kindly tell me why the patch didn't make it 
> into Alsa? What's missing, what's wrong?
> 
> If it's just the fact that Clemens doesn't like the fixed endpoint quirk 
> please find attached a different patch yielding the same result. 
> (Against Linux 2.6.35. It's again from dhubsith who posted it on the 
> M-Audio forum.

Could you include the link to the forum post.

> He would sign it off if requested - on the other hand it 
> is already derived work of the Alsa sources).

I guess his signed-off-by line additionally to yours (Tested-by: is also
good) would not hurt.

> And please, if it's not going anywhere, please tell us "laymen, 
> volunteer Alsa helpers" about the reasons.
> 
> The current situation is most frustrating: We know how to make the 
> device work (much better than in Windows, btw) but we don't know why we 
> have to patch alsa again and again.

Sorry, unfortunately I cannot tell you why your work has not been
committed yet and I do understand your frustration. The reasons might be
simple, that the developers were caught up by different things and your
patch just fall through the cracks. So it is a good thing, that you come
back and ask for the status.

So to ease work for the developers, could you please resend your patch.
Do you know if it can be split up, so that the controversial parts can
be left out at first?

Please use `git format-patch` with

1. a short commit summary line,
2. links to the respective Web pages where this patch was discussed.

You can just copy the lines from the resulting file into a normal
message (delete the header fields and copy the subject manually marking
it with [RESENT]). Just make sure the lines do not get wrapped.

Then make sure to CC the maintainers (I think Clemens, Takashi,
Jaroslav) too so that they do not miss it.

I hope your patch will be included soon afterward.


Thanks and good luck,

Paul


[1] http://mailman.alsa-project.org/pipermail/alsa-devel/2010-July/thread.html#29193
[2] http://www.spinics.net/lists/alsa-devel/msg35372.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part
Url : http://mailman.alsa-project.org/pipermail/alsa-devel/attachments/20100831/2626bb79/attachment.sig