Subject: Re: bus.h style question
To: Jonathan Stone <jonathan@dsg.stanford.edu>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: tech-kern
Date: 08/21/1997 11:29:02
On Thu, 21 Aug 1997 11:23:26 -0700
Jonathan Stone <jonathan@DSG.Stanford.EDU> wrote:
> > (new entry points)
> > bus_space_stream_{read,write}* - value is read from/written to bus
> > space. The values are treated as octet streams, thus bypassing
> > any byte swapping mechanisms. Useful for e.g. 16-bit PIO access
> > to NE-2000 ethernet cards, manipulating VGA frame buffer data, etc.
>
> Fine with me. The "byteswap" name you (rightly) object
> to was for uh, expositional purposes.
>
> But what names do you propose for the bytestream-oriented _multi_ and
> _region_ methods?? Those are what I think are most likely to be
> useful, and I can't follow the logic that decides whether adjectives
> like multi/region/stream are prefixes {read, write}, or suffixes ...
bus_space_stream_{read,write}* matches bus_space_stream_read_multi_* and
bus_space_stream_read_region_* :-)
(How about a contest - who can come up with the longest function name? :-)
Jason R. Thorpe thorpej@nas.nasa.gov
NASA Ames Research Center Home: +1 408 866 1912
NAS: M/S 258-6 Work: +1 415 604 0935
Moffett Field, CA 94035 Pager: +1 415 428 6939