Subject: Re: Gigabit Ethernet
To: Chris G. Demetriou <cgd@netbsd.org>
From: Jason Thorpe <thorpej@nas.nasa.gov>
List: port-i386
Date: 09/08/1999 14:00:35
On 08 Sep 1999 13:50:38 -0700 
 cgd@netbsd.org (Chris G. Demetriou) wrote:

 > So, i'm inclined then to say "use char *".  I dunno what standards say
 > about caddr_t, but at least to my mind it's always seemed bogus that
 > on ANSI-friendly systems it's a char *, even.  (If it's just a "core"
 > address, why does it have a specific type?  8-)
 > 
 > Further (and different!), since what's there is memory and only the
 > user knows what type of memory it actually is, it seems unnecessary to
 > tell the user that they have to cast the result.  The bus_space
 > implementation doesn't (or shouldn't 8-) care about what the actual
 > layout of the memory is.
 > 
 > by your argument, modern malloc, memcpy, etc., should all take or
 > return char *, not void *...

I think void * is the way to go, here.... if not void *, then vaddr_t...

        -- Jason R. Thorpe <thorpej@nas.nasa.gov>