Re: ice1724: from 1.0.4 to 1.0.5a upgrading problem

[Andrew Gaydenko <a@etver.com>]

Takashi,

Inspired with successfull resolving of "build error in pcm_native.c"
problem I have become rather brave to ask some additional questions
concerning this message subject:

- am I understand well, there were attempts to supply 96k earlier,
  but old code has not supplied a working of 96k for wide range of
  users, and code was redone to be more democratic but less functional
  (at least for me)?

- what does it mean: "special handling" for 96k? Who is handler?
  User? Further driver version?

- are there some development patches to try 96k on current CVS base?

Thanks in advance,
Andrew

======= On Wednesday 14 July 2004 17:57, Takashi Iwai wrote: =======
At Wed, 14 Jul 2004 17:49:42 +0400,
Andrew Gaydenko wrote:
> 
> Takashi,
> 
> To tell the truth, have not understood the word "yet": just now (with 1.0.4)
> my receiver (as qjackctl) shows 96KHz (alsaplayer-jack-alsadriver-hw:0,1-spdif).
> Does it mean some redesign was done for this driver since 1.0.4?

The spdif doesn't support 96kHz without a special handling.
It was a bug that 96kHz was accepted for that interface.


Takashi





-------------------------------------------------------
This SF.Net email is sponsored by BEA Weblogic Workshop
FREE Java Enterprise J2EE developer tools!
Get your free copy of BEA WebLogic Workshop 8.1 today.
http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click