-
Notifications
You must be signed in to change notification settings - Fork 5
Add initial documentation, including contributing guidelines #13
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
Conversation
Add link to the main README.md file, which is the entrypoint for our documentation. Signed-off-by: Ricardo Salveti <[email protected]>
21cfe09 to
62d65de
Compare
angolini
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great doc!
I add a comment regarding mentioning the Qualcomm Linux version, but it looks like it's inevitable to explicitly add the version, so maybe it can be ignored.
|
|
||
| ### 4.1 Expected Contribution Types | ||
|
|
||
| - Machine configuration files |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Does it mean new machines are accepted in the "latest LTS based" branch, and it must only be supported by 1.4 or latter qualcomm linux version, in other words, in the latest LTS we can have new machines being included supporting not the latest qualcomm linux? (it it's higher or equal than 1.4, even thought the latest today is 1.6?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is more about the version series, we do say >= 1.4 because they ended up updating the LTS baseline, but we don't expect this to happen in newer releases.
But we do want to support new machines in the 'latest LTS' series.
docs/contributing.md
Outdated
| - Firmware recipes referencing vendor-hosted binaries | ||
| - Partition configuration defined through `qcom-ptool` | ||
| - Kernel support via `linux-qcom-next` `.bbappend` | ||
| - CI job validating `core-image-minimal` build and boot on target |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I understand core-image-minimal does not include non-vital firmware, which can be binaries hosted on an vendor mirror. It means (I believe) that building only core-image-minimal will not detect missing closed firmware files. If this is the intended, so ok
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Right, we do test core-image-base actually (will update), but modules are not included by default there, which is ok as we also have the base module list available in the bsp layer.
kprosise
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No grammar/style issues that pop out, and Markdown appears to be properly formatted. Approved!
quaresmajose
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Not yet complete due missing arduino references, to be added once we include support for uno-q. Co-authored-by: Daiane Angolini <[email protected]> Signed-off-by: Ricardo Salveti <[email protected]>
|
Thanks for the reviews everyone! |
No description provided.