[lkml]   [2002]   [Feb]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [Linux-ia64] Proper fix for sym53c8xx_2 driver and dma64_addr_t

On Wed, 6 Feb 2002, David Mosberger wrote:

> >>>>> On Wed, 6 Feb 2002 18:10:42 +0100, Christoph Hellwig <> said:
> Christoph> On Wed, Feb 06, 2002 at 12:45:03AM -0800, David S. Miller
> Christoph> wrote:
> >> It is not using the DMA apis correctly then, it should be using
> >> dma_addr_t which may or may not be 64-bits on a given platform.
> Christoph> When the sym2 driver is configured with
> Christoph> SYM_CONF_DMA_ADDRESSING_MOD > 1 it uses DAC accessing and
> Christoph> needs dma64_addr_t. It doesn't use it when using the
> Christoph> default addressing mode.
> The driver never uses the pci_dac* interface, hence it should not use
> dma64_addr_t. If the driver needs a 64-bit wide type, u64 will do
> fine.

The driver was ready for PCI DAC months before the Linux way to do DAC was
stabilized to the current one. Given the discussion on the harmless way
the sym2 driver is using dma64_addr_t, it seems to me that this interface
may still move.

This let me think that the real problem is not the sym2 driver here, but
rather the Linux IO interfaces saga that lasts from years.

For now just replacing all occurrences (in fact only 1) of the offending
dma64 thing in sym_glue.c by the corresponding dma thing should do the
trick and close this thread as a result.

If you want to discuss about either PCI DAC under Linux or Linux-i64 arch
(that btw seems to be dead prior to have born) then, please, change the
subject of this thread.


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:24    [W:0.058 / U:4.432 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site