Fix a long-standing bug in alpha's implementation of busdma.  We need to OR the physical address with alpha_XXX_dmamap_or to get the DMA address, like the name of the variable suggests.  However, while we were doing this correctly in the alpha_XXX_dmamap() macro, the busdma code added the variable to the physical address instead of or'ing it.  Fortunately and if my math is not entirely wrong, you would need more than 128GB of RAM and a device able to do DMA in 64bits to experience the bug.
Fix a long-standing bug in alpha's implementation of busdma.  We need to
OR the physical address with alpha_XXX_dmamap_or to get the DMA address,
like the name of the variable suggests.  However, while we were doing
this correctly in the alpha_XXX_dmamap() macro, the busdma code added
the variable to the physical address instead of or'ing it.  Fortunately
and if my math is not entirely wrong, you would need more than 128GB of
RAM and a device able to do DMA in 64bits to experience the bug.

Spotted by:	cognet

jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase,jrobhoward/SCADAbase