ATAGs .. the when and how?

[rosery]

What is needed to persuade the loader (?) to populate the ATAG and command line structure at 0x100 please?. Is it just blank space at 0x100 in one's image (I use my own 'first32k') or are there some magic bytes needed in the image. I have put in place the AT 1 and AT 2 tags found in args-uncompressed.txt, hoping this would seed things, but to no avail.
it makes no difference whether I have the ignoretags thing in config.txt

[huceke]

IIRC the newer firmwares do not need the magic anymore.

[rosery]

I'm happy not to use it, but it did pass through certain things, such as memory size and mac address etc, which are rather useful to know. Any thoughts on how to find those?
thanks

[rosery]

Got it .. At the present, the atags are loaded at offset 0x100 into the start.elf space.. e.g. if you're using the arm192 start.elf, they will be at offset 0x0c000100, with various other parameters etc at 0x0c000000; memory size + some flags at 0ffset 0x80 into here.

The big Q therefore, is what please are these entrypoints/call points that are at the base of the 'vc side'.. i.e. just above the arm assigned ram. Can anyone point me to the definition of this structure please

[rosery]

resolved- rediscovered with kernel_old=1 form issue 36 .. thanks