Brian Feldman bf5ab950e3 The new contigmalloc code is exposing a lot of misuses of busdma memory ... allocation. Notably, in this case, the driver tries to allocate several pieces of memory and then fails if the pieces allocated after the first do not come after it physically, and within a specific range (8MB I believe). Of course, this could just as easily fail for any number of reasons, but it almost always fails now that contiguous allocations start at the end of possible specified memory locations rather than the beginning. Allocate all the possibly-needed memory up front, even though it's a waste, to get around this. The least bogus solution would be to take the physical address from the first allocation and create a new tag that specified that further allocations must follow it within that 8MB window, then use that when allocating new channels, but that's left for anyone else that really feels like doing it. Tested by: Erwin Lansing <erwin@lansing.dk>		2004-08-22 18:57:40 +00:00
..
isa	Rename the sound device drivers:	2004-07-16 04:00:08 +00:00
pci	The new contigmalloc code is exposing a lot of misuses of busdma memory	2004-08-22 18:57:40 +00:00
pcm	Rename the sound device drivers:	2004-07-16 04:00:08 +00:00
usb	Rename the sound device drivers:	2004-07-16 04:00:08 +00:00
chip.h
driver.c	Do a pass over all modules in the kernel and make them return EOPNOTSUPP	2004-07-15 08:26:07 +00:00