![]() | |||||||||||||
Messages in this thread |
Alan wrote: >> Confused. As in, once the bcm43xx module initcall happens? Or without bcm43xx >> at all? If the former, is the behavior different when built as a module versus >> built-in? (ie, are there ordering problems.) > > The pci_dma code on the x86_64 platform is broken for the case of PCI > devices with < 32bit DMA. Has been forever, this is a problem with > various devices, although most of the others are obsolete except for the > bcm43xx and b44 (the latter has hacks to work around the x86-64 > brokenness). > > At the very least the pci_set_dma_mask should error in this situation or > switch to using GFP_DMA (24bit) memory spaces. Having it error isn't the > whole solution as you still need some way to handle the "what do I do > next". I agree that pci_set_dma_mask should at least return an error. That will protect the ignorant! Thanks for the pointer to the b44 code. I'll try to fix bcm43xx the same way. Larry - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||||
| Last update: 2006-11-21 16:39 [from the cache] ©2003-2008 | |||||||||||||