[lkml]   [2003]   [Apr]   [29]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Patch] DMA mapping API for Alpha
>>>>> "Ivan" == Ivan Kokshaysky <> writes:

Ivan> Agreed, but what if your EISA-PCI bridge has only 30 address
Ivan> lines wired to PCI? Yes, we can check this for EISA device
Ivan> because it has *real* PCI parent (thanks, Marc :-), but what
Ivan> about ISA/legacy/whatever drivers? I doubt that all of them
Ivan> bother to set dma_mask pointer (so you can have an oops there).

If the driver is not ported to the device API, than we pass NULL as a
device pointer, and then we fallback to the old behaviour, aka
dma_mask=0x00ffffff. If the driver supplies a dev pointer, but fails
to set its dma_mask pointer, than it is a driver bug that should be

And yes, the EISA subsystem should properly report the dma_mask to
attached devices (patches for that are in mm tree, and sent to Linus).

Places change, faces change. Life is so very strange.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:35    [W:0.053 / U:5.788 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site