Bug #202249, kernel Oops and ALSA configs
Colin Ian King
colin.king at canonical.com
Thu Mar 27 09:49:04 UTC 2008
I've dug into the bug
and found the cause of the kernel Oops is apparently because the driver
is being built against the wrong alsa header files and not the ones in
the alsa tree. Specifically, it is picking up the wrong pcm.h header
file and there is a mismatch in data structure sizes, causing a pointer
to be referenced incorrectly in the btsco.c driver (it's 3 levels deep
in indirection, so it's not been easy to find).
Anyhow, as I am not an ALSA expert yet, how does one deal with a module
that is built in the lum tree outside of the ALSA tree but depends on
the ALSA headers?
Q. Should the btsco.c driver be moved into the ALSA tree to help resolve
this issue - or does this make life more complex to support ALSA?
Basically I don't want to screw up anything so I'd appreciate some
More information about the kernel-team