sparse warnings

Sascha Hauer s.hauer at
Wed Nov 17 04:11:02 EST 2010

Hi Marek,

On Mon, Nov 15, 2010 at 03:20:47PM +0100, Belisko Marek wrote:
> Hi,
> barebox compilation with C=1 produce a lot of sparse warnings.
> Mainly concerning __iomem problems with readb() and similar functions.
> Make it sense to take care or just could be omitted?

I think it makes sense to work on this. Then we can see the useful
warnings buried under the __iomem warnings.

I had the idea of adding a

#define IOMEM(addr)        ((void __force __iomem *)(addr))

and use it where appropriate.


Pengutronix e.K.                           |                             |
Industrial Linux Solutions                 |  |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0    |
Amtsgericht Hildesheim, HRA 2686           | Fax:   +49-5121-206917-5555 |

More information about the barebox mailing list