SoylentNews is people
SoylentNews
https://www.devever.net/~hl/regmap
If you've ever had to write a program which interfaces directly with hardware — perhaps while writing a program for an MCU or embedded system or a kernel driver — you may have noticed a few common patterns in register map behaviour and design. I'm not sure anyone has ever really collected them together, so I decided to make a list of all the ones I can think of.
This discussion was created by janrinok (52) for logged-in users only. Log in and try again!
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
I think that I shall never see
A billboard lovely as a tree.
Indeed, unless the billboards fall
I'll never see a tree at all.
-- Ogden Nash
(Score: 2) by turgid on Monday May 22, @08:44PM (7 children)
The first time I came across this I was stunned. Why did hardware need a /dev/null?
No, that's not what it was for.
Still, it's one of those mysteries how it works or why you wouldn't be able to (or want to) read it back. It's a trivial software change to "remember" the last value written if you really need to (to make the rest of the program simpler).
I refuse to engage in a battle of wits with an unarmed opponent [wikipedia.org].
(Score: 3, Funny) by RS3 on Monday May 22, @09:36PM
The write-only register is used in address dereferencing calculations when working with write only memory [repeater-builder.com].
(for those who might not have grasped it, this is a joke).
(Score: 3, Interesting) by KilroySmith on Monday May 22, @10:07PM
I had to fight the battle over write only registers with our chip designers one time. This was in the age when transistors on a a die were expensive; adding in the read circuitry for all the registers on chip made the die noticeably larger, thus noticeably more expensive. I haven’t seen such a thing in ages, because transistors are now remarkably cheap and that battle never needs to be fought.
(Score: 3, Informative) by owl on Monday May 22, @10:25PM (2 children)
Nor did I, when I first encountered it on the Dec Alpha CPU. One of it's registers was wired up to always read zero, and always consume and throw away a write without complaint (effectively a /dev/null register).
Then I dug in more, and its usefulness was in synthesizing additional addressing modes from the small set of hardware address modes the chip actually provided.
I.e., (and this is largely from memory, so I may be off a bit) the Alpha architecture did not provide a native "load 64-bit word from address X stored in register Rx". Instead it provided a "load word from address stored in Rx indexed by offset stored in Ry" as a native mode. The "load from literal address" mode was synthesized by using R0 (assuming R0 was the "read as zero, consume all writes" register) as Ry in the addressing mod.
So when you wrote: load R5,[R16]
to load R5 from the address in R16, the actual CPU instruction executed was: load R5, [R16+R0]
With R0 providing a "zero", which makes the offset addition a null operation, resulting in a load from address in R16.
In the end, the Alpha had something like only 4 or 8 actual hardware addressing modes, but with creative use of the "zero register" the programmers had something like 16 or 24 different possible "addressing modes" that they could actually use.
(Score: 4, Informative) by sjames on Monday May 22, @11:15PM (1 child)
In addition, a zero register is a good way to initialize an accumulator without having an extra instruction. Writing to the zero register is a cheap to implement NOP. Add that to the inexpensive addressing flexibility and you get a lot of bang for the buck from the zero register.
(Score: 3, Informative) by owl on Tuesday May 23, @02:17AM
Now that you mention it, I think the Alpha's "nop" instruction was actually something like
add r0,r0,r0
(assuming r0 was the "always zero" register), that would add zero to zero and store the answer in the register that was always zero. The result, a "NOP" instruction, without having to explicitly have an actual "NOP" instruction built into the hardware.
(Score: 2) by sjames on Monday May 22, @11:01PM
Sometimes there is no memory behind the register. The address decode and the r/W line together through an AND gate triggert some action. There is nothing to read back.
(Score: 2) by Mojibake Tengu on Monday May 22, @11:05PM
Write-only registers are usually used for controlling such hardware state, where reading back does not have any sense because the state itself is rather ephemeral in time domain (because it serializes, or just strobes some other data).
Some examples are tape or floppy interfaces, or full duplex modem control.
Today, it's still usual as GPIO set in OUT mode.
Another fine example is power-off control. You don't want to read power control to determine the machine is powered off, don't you?
The edge of 太玄 cannot be defined, for it is beyond every aspect of design