On 27/11/13 15:07, Christopher Covington wrote:
Hi Ryan,
On 11/27/2013 01:49 AM, Ryan Harkin wrote:
On 26 November 2013 21:51, Michael Hudson-Doyle <michael.hudson@linaro.org mailto:michael.hudson@linaro.org> wrote:
Hi all, Do we have, or do we have plans for, an image that's based on Ubuntu that's usable with the foundation model? The only part I don't know how to do for myself is build the .axf fileAXF is sooo unfashionable these days ;-) It's all ARM Trusted Firmware, UEFI and a proper Image file.
By how much does this increase the number and variety of storage media a simulator must implement? By how much does this increase the number of instructions that must executed prior to running the kernel? Why would one prefer these more heavy-handed boot methods if one's primary interest is running the Linux kernel, Linux userspace processes, or both in a simulator? Are there instructions for running this stuff on QEMU?
By the way I find the terminology of "AXF" very confusing. As far as I understand it, AXF is essentially synonymous with the ARM ELF file format. What's really being discussed, though, is the boot-wrapper, right?
Thanks, Christopher
AXF is a filename extension and its origins are historical. It dates to the pre-elf days when ARM's internal toolchain used proprietary object and executable file formats. AOF was the extension used for linkable Object files and AXF for eXecutable files. When the switch to ELF occurred, the extension AXF was maintained as it helped users know that the file was firstly executable, and secondly not a windows executable (windows works by mapping file extensions onto programs that can operate on them, like the ARM debugger).
R.