Just like _FILE_OFFSET_BITS controls off_t

Your code should be ready to accept 32 bit or 64 bit paddr_t - you can test
for _PADDR_BITS
if you need to change behaviour based on this.

Check proc/*/cpu.mk - some of them define _PADDR_BITS to be 64, the
corresponding defines
will be set for startup too.

Mario Charest wrote:
>  > It can be either, depending on _PADDR_BITS
> 
> This is a user config.  I'm free to set it to 32 or 64 with no danger of 
> breaking anything, if my own code ? ;-)  I noticed the _PADDR_BITS this 
> in the header file but because it's prefixed with _ I assumed it was a 
> system symbol and should be left untouched.
> 
> 
> _PADDR_BITS doesn't shoudl
>  >
>  > Colin
>  >
>  > Mario Charest wrote:
>  > >
>  > >
>  > > Shouldn't paddr_t be an unsigned 64bit value instead of 32.  Or did I
>  > > misunderstand the scope of its usage.
>  > >
>  > > _______________________________________________
>  > > OSTech
>  > > http://community.qnx.com/sf/go/post7497
>  > >
>  >
>  > --
>  > cburgess@qnx.com
> 
> 
> 
> 
> _______________________________________________
> OSTech
> http://community.qnx.com/sf/go/post7499
> 

-- 
cburgess@qnx.com