On the other hand the current ac97.c implementation is a closely coupled
combination of a PCI/ACLink bridge (Intel 82801AA) with a generic AC97
codec. This has prevent me to easily reuse this code.
The milkymist-ac97 implementation is another case. It looks like a basic
implementation with
Paul Brook wrote:
On the other hand the current ac97.c implementation is a closely coupled
combination of a PCI/ACLink bridge (Intel 82801AA) with a generic AC97
codec. This has prevent me to easily reuse this code.
The milkymist-ac97 implementation is another case. It looks like a basic
The PL041 driver provides an interface to an ACLink bus.
The LM4549 driver emulates a DAC connected on the ACLink bus.
Only audio playback is implemented.
Shouldn't this be shared with the other AC97 devices?
Paul
Paul Brook wrote:
The PL041 driver provides an interface to an ACLink bus.
The LM4549 driver emulates a DAC connected on the ACLink bus.
Only audio playback is implemented.
Shouldn't this be shared with the other AC97 devices?
Paul
I organized the code in 3 different drivers (PL041 = ACLink
The PL041 driver provides an interface to an ACLink bus.
The LM4549 driver emulates a DAC connected on the ACLink bus.
Only audio playback is implemented.
Versatile/PB test build:
linux-2.6.38.5
buildroot-2010.11
alsa-lib-1.0.22
alsa-utils-1.0.22
mpg123-0.66
Qemu host: Ubuntu 10.04 in Vmware/OS
On Tue, 10 May 2011, Mathieu Sonet wrote:
The PL041 driver provides an interface to an ACLink bus.
The LM4549 driver emulates a DAC connected on the ACLink bus.
Only audio playback is implemented.
Versatile/PB test build:
linux-2.6.38.5
buildroot-2010.11
alsa-lib-1.0.22
