This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

New developer guides for AArch64

We (Arm's Support and Content Services teams) have been working on creating a Developer Guide for AArch64.  They're aimed at anyone wanting a bare-metal focused introduction to the Armv8-A architecture.  The first few chapters are now live, with more planed to appear over the next few months.

https://developer.arm.com/architectures/learn-the-architecture

We'd love to know what you like, and don't like, about the guides we've written so far.

Parents
  • My 2cents:

    * The page needs a lot scrolling as the main-headline bars are way to high: The first page just covers three sub-section headline.

    * Please provide it also as single PDF, at least the sub-section which also allow "single-page" view.

      Note: Not everyone is always online!

    * Instead of using a UTF-16 character, why not just use a little icon for opened/closed section

    * Single-Page view: Split the screen to keep the directory at fixed place and/or provide buttons to return to top of page.

    Edit:

    * Formating error (missing spaces): developer.arm.com/.../normal-memory

    * Section: https://developer.arm.com/architectures/learn-the-architecture/memory-model/cacheability-and-shareability-attributes

    "This allows for some complex configuration, which is beyond the scope of this guide."

    Instead of this sentence, point to a guide which at least summarizes the complexity. If something bare-metal provides headaches then it is caching and all the troubles which come with it.

Reply
  • My 2cents:

    * The page needs a lot scrolling as the main-headline bars are way to high: The first page just covers three sub-section headline.

    * Please provide it also as single PDF, at least the sub-section which also allow "single-page" view.

      Note: Not everyone is always online!

    * Instead of using a UTF-16 character, why not just use a little icon for opened/closed section

    * Single-Page view: Split the screen to keep the directory at fixed place and/or provide buttons to return to top of page.

    Edit:

    * Formating error (missing spaces): developer.arm.com/.../normal-memory

    * Section: https://developer.arm.com/architectures/learn-the-architecture/memory-model/cacheability-and-shareability-attributes

    "This allows for some complex configuration, which is beyond the scope of this guide."

    Instead of this sentence, point to a guide which at least summarizes the complexity. If something bare-metal provides headaches then it is caching and all the troubles which come with it.

Children