On Sun, Oct 22, 2006 at 11:44:39PM +0200, Andi Kleen wrote: ... > The /** function arguments can be turned into Documentation. > When you do make pdfdocs you get a .pdf in > Documentation/DocBook/kernel-api.pdf
Ah ok. I haven't look at DocBook in a long time. I'll take a look at it before making references to it. ... > > E.g. lots of SATA/IDE devices are 64-bit DMA capable but it > > looks like generic code is leaving them at 32-bit. > > Not good if the box is > 4GB (and many are now). > > Not a good example imho, usually to get >4GB on those you need to use a > special interface, a standard SATA/IDE driver cannot do it. > It's a lot more than just thinking about it. IDE subsystem is a bad example in that it predates PCI. But IDE is a good example as any. Changes to subsystems often happen when at least two people "think about it": the driver writer and the subsystem maintainer. ide_build_dmatable() follows some standard which dictates (and HW implements) an SG list structure with 32-bit addresses and 16-bit counters. New PCI devices are certainly capable of more than that. So I'm now certain I want to keep references to pci_set_dma_mask() in this document since some SATA (not IDE) could do something different if the SATA device driver would advertise it was 64-bit capable. I know jgarzik is smart and I hope he's already provided some way for libata users to indicate their devices are 64-bit capable. (Maybe Docbook would tell me that - checking :) thanks, grant - To unsubscribe from this list: send the line "unsubscribe linux-arch" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html
