For loading programs on the Prop 1, most loaders require a contiguous 32K physical file storage area for the binary file. The easiest way to do this is to use a 32K cluster. For applications where there's no other compelling reason to choose one cluster size over another, this may trump other reasons for a particular cluster size. It would be possible to write the loader to work with smaller cluster sizes, maybe building a table of clusters to be loaded along with their physical addresses and sizes before turning control over to the cog-resident loader, but I don't think this has been done yet.
For loading programs on the Prop 1, most loaders require a contiguous 32K physical file storage area for the binary file. The easiest way to do this is to use a 32K cluster. For applications where there's no other compelling reason to choose one cluster size over another, this may trump other reasons for a particular cluster size. It would be possible to write the loader to work with smaller cluster sizes, maybe building a table of clusters to be loaded along with their physical addresses and sizes before turning control over to the cog-resident loader, but I don't think this has been done yet.
My driver does this Mike. Other loaders do not however.
For loading programs on the Prop 1, most loaders require a contiguous 32K physical file storage area for the binary file. The easiest way to do this is to use a 32K cluster. For applications where there's no other compelling reason to choose one cluster size over another, this may trump other reasons for a particular cluster size. It would be possible to write the loader to work with smaller cluster sizes, maybe building a table of clusters to be loaded along with their physical addresses and sizes before turning control over to the cog-resident loader, but I don't think this has been done yet.
The PropGCC SD cache driver does this for running XMM programs directly off of the SD card using a hub cache.
Comments
For loading programs on the Prop 1, most loaders require a contiguous 32K physical file storage area for the binary file. The easiest way to do this is to use a 32K cluster. For applications where there's no other compelling reason to choose one cluster size over another, this may trump other reasons for a particular cluster size. It would be possible to write the loader to work with smaller cluster sizes, maybe building a table of clusters to be loaded along with their physical addresses and sizes before turning control over to the cog-resident loader, but I don't think this has been done yet.
My driver does this Mike. Other loaders do not however.
Thanks,
The PropGCC SD cache driver does this for running XMM programs directly off of the SD card using a hub cache.