> In the Linux case mmio isn't a problem. The rules for mmio in the portable > code require you use architecture dependant macros (readb etc) and that > the mmio space is mapped via ioremap. I haven't done my homework, but I assume the code behind readb use inline assembly and not C on most platforms? May be GNU C could get some of the idea behind the Linux macros to define the needed extension (portable within GNU C architectures wherever possible). -- Laurent Guerby <guerby _at_ acm.org> - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo _at_ vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Follow-Ups:
- Re: [PATCH] C undefined behavior fixAlan Cox <alan _at_ lxorguk.ukuu.org.uk>
- Re: [PATCH] C undefined behavior fixAlan Cox <alan _at_ lxorguk.ukuu.org.uk>
- Prev by Date: Re: [2.4.17/18pre] VM and swap - it's really unusable
- Next by Date: Re: [PATCH] C undefined behavior fix
- Previous by thread: Re: [PATCH] C undefined behavior fix
- Next by thread: Re: [PATCH] C undefined behavior fix
- Indexes:[Main][Thread]