Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add design docs #50

Open
wants to merge 2 commits into
base: master
Choose a base branch
from
Open

Add design docs #50

wants to merge 2 commits into from

Conversation

ericonr
Copy link
Member

@ericonr ericonr commented Sep 6, 2024

No description provided.

@ericonr
Copy link
Member Author

ericonr commented Sep 6, 2024

Comment on lines 3 to 4
A primer on the hardware with which this project interfaces should be useful in
understanding the design choices made.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
A primer on the hardware with which this project interfaces should be useful in
understanding the design choices made.
A primer on the hardware that this project interfaces with should be helpful in understanding the design choices made.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

documentation/design.md Outdated Show resolved Hide resolved
documentation/design.md Outdated Show resolved Hide resolved
documentation/design.md Outdated Show resolved Hide resolved
documentation/design.md Outdated Show resolved Hide resolved
documentation/design.md Outdated Show resolved Hide resolved

#### Addressing oddity

Accessing the registers in `BAR4` requires manipulation of their addresses,

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
Accessing the registers in `BAR4` requires manipulation of their addresses,
Accessing the registers in `BAR4` requires manipulation of their addresses

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It seems a bit awkward to me because the second clause is tightly connected to the first. I don't think that it's grammatically incorrect, though.

implementation detail) using the functions defined in `util/pcie.h`.

`BAR2` can also be accessed when `struct pcie_bars` points to a serial port,
which is used when debugging boards outside of a MTCA crate.

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
which is used when debugging boards outside of a MTCA crate.
which is used when debugging boards outside of a µTCA crate.

or

Suggested change
which is used when debugging boards outside of a MTCA crate.
which is used when debugging boards outside of a uTCA crate.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The workshop seems to prefer MTCA. Do you have a reason for preferring the u version?

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the way that it's referenced on the PICMG page and in the Wikipedia. Also, it seems more direct to use the micro representation for this.

Copy link
Member Author

@ericonr ericonr Dec 4, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The PICMG page also has some instances of MTCA D:

The reason I'm mostly using MTCA nowadays is because it's easier to type, and I don't like pretending "uTCA" is "µTCA".

@augustofg do you have any preference?

The interface provided by the gateware was what guided the library
design, so we should document that first.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants