At 04:13 PM 4/12/2005, Wolfgang Denk wrote:
>i2s.c is not really a driver, but a (very OLD) test version of one
>used to demonstrate certain BestComm related problems. Don't try
>using it as a real driver ;-)
Humm, any pointers on writing our own driver then then? Digging through
the source for other drivers, bestcomm seems to be a real house of
cards. We just want simple audio output capability. No need to make it
work with the standard Linux/OSS sound API.
Where can we keep track of the eratta/bugs in bestcomm? Browsing through
the mailing list, I've found references that:
IDE and Ethernet DMA can't work at the same time
I2S TX and RX DMA can't work at the same time
AC-97 is terminally broken (no way to handle the slot tags properly
for variable sampling rates)
Are these all still true?
We've tried asking our local Freescale rep, but they seem to think that
Linux==Metrowerks, and they are looking into the bestcomm question, but
official responses from Freescale tend to take >1 week.
This is for a custom MPC5200 board, heavily based on IceCube with a single
I2S DAC on PSC2 running in "CODEC with MCLK" mode.
Sorry about the null subject line previously: fingers were working faster
than brain...
Thanks
Eric
------------------------------------
Eric Johnson, Electrical Engineer
Advanced Communication Design
7901 12th Avenue South
Bloomington, MN 55425
Ph: 952-854-4000 Fax: 952-854-5774
