lkml.org 
[lkml]   [2005]   [Apr]   [2]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    SubjectRe: iomapping a big endian area
    From
    Date
    On Sat, 2005-04-02 at 20:08 -0800, David S. Miller wrote:
    > > Did anyone have a preference for the API? I was thinking
    > > ioread32_native, but ioread32be is fine too.
    >
    > I think doing foo{be,le}{8,16,32}() would be consistent with
    > our byteorder.h interface names.

    Thinking about this some more, I know of no case of a BE bus connected
    to a LE system, nor do I think anyone would ever create such a beast, so
    our only missing interface is for a BE bus on a BE system.

    Thus, I think io{read,write}{16,32}_native are better interfaces ...
    they basically mean pass memory operations without byte swaps, so
    they're well defined on both BE and LE systems and correspond exactly to
    our existing _raw_{read,write}{w,l} calls (principle of least surprise).

    James


    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-04-06 13:31    [W:0.018 / U:59.660 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site