Looking at the code, it would seem that for ARM9 targets arm9glob
defaults to 1 and if noglob option is specified then arm9glob is set
back to 0.
Using 'noglob' for non-ARM9 targets appears to have no effect as
arm9glob is initialized to 0 (by calloc) and then set to 0 again by the
noglob option. 
 
Also, arm1136 is ARMv6 so ISARM9 is false for this target

-----Original Message-----
From: Kevin Mar [mailto:community-noreply@qnx.com] 
Sent: Wednesday, March 10, 2010 1:59 PM
To: general-multimedia
Subject: RE: io-fs-media -dtmp noglob and min/max size options

The cpuflags are checked in services/io-fs/fsys/tmp/devio.c to determine
if it's ARM9.

-----Original Message-----
From: Andrew Sherk [mailto:community-noreply@qnx.com] 
Sent: March 10, 2010 1:40 PM
To: general-multimedia
Subject: io-fs-media -dtmp noglob and min/max size options

The docs say, "The noglob option is for ARM9 targets only." and, "With
ARM9 targets, behavior varies from that described above: at start up,
memory is allocated contiguously up to the value specified by the
maxsize option. "

Do the ARM9 specific comments apply to arm1136 (imx35) targets?
How does io-fs-media -dtmp know which arm version is running?







_______________________________________________

General
http://community.qnx.com/sf/go/post49208




_______________________________________________

General
http://community.qnx.com/sf/go/post49218