The Lynxtwo firmware is based on a 2008 release ever since they came out 
with the Lynx AES16. Unfortunately newer versions of the firmware 
required a complete rewrite and frankly it's just too much work for too 
little revenue from the sales of OSS licenses.

We have approached Lynx to open source the drivers - they don't want it 
opensourced.  We have no problems opensourcing our work....so if you're 
a developer with the LynxTwo, you might be able to get the HAL from Lynx 
and then we can send you the source and you do the port.

regards
Dev Mazumdar


J. Lauer wrote:
> I am a user with a question about the lynxtwo module.  On the Open Sound 
> System
> forum, cesium suggested sending a note to the
> developer's mailing list, because he did not
> know the answer.
>
> Could someone please tell me which version
> of Lynx Studio's AES 16 driver the current
> OSS lynxtwo module is based on?
> The reason I ask is that I would like to know
> whether the OSS module is compatible with the
> newest version of the firmware for the AES16.
>
> Lynx Studio made an important improvement in the firmware in Firmware Build 
> 24, 5 August 2010. This version of the firmware improves the operation of the 
> hardware clock and reduces jitter.
> Build 24 of the firmware requires Version
> 2.0 Build 14 of the Windows driver, or newer,
> to function correctly.  So, I would appreciate knowing whether the lynxtwo 
> module is based
> on Version 2.0 Build 14 driver or newer.
>
> Thank you,
>   Steven German
>
> _______________________________________________
> oss-devel mailing list
> oss-devel@mailman.opensound.com
> http://mailman.opensound.com/mailman/listinfo/oss-devel
>

-- 
----------------------------------------
4Front Technologies, Inc.
9826 Beverlywood Street
Los Angeles, CA 90064

Tel: (310) 202 8530 Fax: (310) 202 0496
----------------------------------------

_______________________________________________
oss-devel mailing list
oss-devel@mailman.opensound.com
http://mailman.opensound.com/mailman/listinfo/oss-devel

Reply via email to