Stories
Slash Boxes
Comments

SoylentNews is people

Patterns in Register Map Design

posted by janrinok on Monday May 22, @05:31PM   Printer-friendly

owl writes:

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.

Original Submission

 
This discussion was created by janrinok (52) for logged-in users only. Log in and try again!
Patterns in Register Map Design | Log In/Create an Account | Top | 11 comments | Search Discussion
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.

  • (Score: 2) by sjames on Monday May 22, @11:01PM

    by sjames (2882) on Monday May 22, @11:01PM (#1307496) Journal

    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.

    Starting Score:    1  point
    Karma-Bonus Modifier   +1  
    Total Score:   2