Re: [PATCH]: Fix compiler warning in drivers/scsi/dpt_i2o.c

[Russell King <rmk+lkml@arm.linux.org.uk>]

On Mon, Mar 14, 2005 at 09:06:26PM +0100, Stefan Roas wrote:
> On Mon Mar 14, 2005 at 18:24:44, Ben Dooks wrote:
> 
> > This patch looks suspiciously like it is sweeping the problem
> > `under the carpet`. Does bus_to_virt() return an `void __iomem *`?
> > 
> > reply should really be an `void __iomem *` 
> 
> bus_to_virt returns void *.
> 
> adpt_isr casts the return value to ulong though and adpt_i2o_to_scsi
> takes an ulong as its first argument and passes it to readl without a
> cast then.
> 
> But I agree, the patch just silences the compiler warning. Maybe it
> would be a better solution to change the types of reply and msg in
> adpt_isr as well as the first argument to adpt_i2o_to_scsi to void
> __iomem *.

However, bus_to_virt() can only be used on addresses which correspond
with system RAM.  readl and friends should not be used on such a memory
space.  So, this driver is doing lots of bogus stuff.

The warnings are perfectly valid and should therefore stay.

If "reply" is actually referring to some system memory, the readl/writel
shouldn't be there, and we should be accessing system memory directly
via a bona-fide structure.  If it isn't, then the bus_to_virt() is
completely bogus and unportable, and that's where we _must_ raise a
warning.

However, I do agree with changing "msg" to be void __iomem *, and
removing the (ulong) cast, since pHba->msg_addr_virt is already
void __iomem *.

(note: I'm just taking a passing interest in this thread, from the
point of view of an architecture maintainer who wants these types of
things to be Correct(tm)...)

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core