Do you know them by heart or do you use doc?

[kamelito]

Hi
I was wondering if hardware banging coders know all registers by heart in
1) hex values
2) include names
3) No I just use the documentation.

[ross]

4) if I don't remember by hex value or name I check the documents

[kamelito]

3) for me, I don't think my brain is able to store them anyway.

[Galahad/FLT]

If i'm hacking/cracking something, I remember hex values, but if i'm coding in Devpac, I at least try to use includes and stuff so that my code is at least readable when I return to it, whereas something i'm hacking, once its done, i'm unlikely to ever go back to it.

[mcgeezer]

Can probably count better in hex than I do decimal

I use all the current includes, bit names as they are defined in the HRM - but I keep a copy of the HRM next to me just in case and a file with Randy's AGA docs just in case.

[Antiriad_UK]

Apart from color00 (180) I don't know any by heart - but I don't do any reverse engineering/cracking.

[WayneK]

Originally Posted by ross

4) if I don't remember by hex value or name I check the documents

This ^^


Most of the time I remember them, if I don't then I look them up

[Rock'n Roll]

I actually memorised the registers like vocabulary years ago. It's worth it and I can only recommend it,
because otherwise you would have to refer to the documentation too often. Of course, I've forgotten some of them since then and would have to
the list again. The rest is down to practice, but it's particularly useful when working with the debugger.

If I don't know something, I look it up online: http://amiga-dev.wikidot.com/information:hardware
I have created a bookmark for quick access.
I also have a bookmark for this: https://amigafonteditor.ozzyboshi.co...onversion.html

Personally, I don't like includes in the sources either. I prefer to have the value or the register directly in view.
Maybe just the register names, e.g. the blitter registers, but not any bits or flags.
Otherwise I would always have to look in the includes to see what is hidden behind these names. It also bloats the sources of my opinion
unnecessarily. But everyone likes it differently. But of course they also have their advantages and their justification.

What is also very important in addition to the registers, however, is to know (roughly) which bits in the hex values at
which bit positions are set or deleted as nibble, byte, word.

The high school is when you can also name the individual bit positions in the individual control registers from memory!
Here, however, it is sufficient to know which bits are in which register and what they do.

When looking at a copper list, you should immediately see what is going on.
and maybe you should also have some op-codes on it. e.g. 4e75

quite a chaos of numbers... but we have the overview

[junosix]

Hex values instead of include as the include names feel a bit like I'm abstracted from the hardware. Usual reference order: Amiga memory map for initial lookup, then a search on EAB/Google, and finally a scroll through the HRM if needed.

The only one I know off the top of my head is 180 for background colour, 096 and 09a are kind of getting in there too but memory map required to remind myself what each bit sets.