On Mon, Nov 7, 2011 at 2:57 PM, Sylwester Nawrocki <snjw23@xxxxxxxxx> wrote: > My knowledge about this driver is rather limited, in case of any issues I > guess it's best to ask Devin directly. Part of the problem here is that the as102 chip is a fully programmable part, and as a result the firmware may differ on a product-by-product basis. In fact, the engineer at Abilis told me outright that the firmware provided for the PCTV device isn't appropriate for the Elgato board, but it worked "good enough" for the user. In other words, users are free to try the firmware prepared for PCTV against other devices, but be prepared for it to not be optimized properly for that hardware design (meaning tuning quality issues or perhaps not working at all), and if it destroys your board then don't come crying to me. The only way to know if the same firmware is being used would be to do a USB capture, write a decoder which allows you to extract the firmware being uploaded, and compare it against the PCTV blob. And if it doesn't match, there's no real way of knowing whether the delta is significant. Also worth noting that the only firmware we have the legal right to freely redistribute is the one needed by the PCTV device. Even if somebody extracts another firmware blob from a USB trace, there are no legal rights to redistribute it (meaning a firmware extract script written to work against the Windows driver binary would be required). Devin -- Devin J. Heitmueller - Kernel Labs http://www.kernellabs.com -- To unsubscribe from this list: send the line "unsubscribe linux-media" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
