Skip to content

Migration: New porting guide from Cloud team #619

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

Closed

Conversation

theotherjimmy
Copy link
Contributor

Original text from @jen3andruska:

New porting guide for porting Mbed OS before porting Mbed Cloud

@theotherjimmy
Copy link
Contributor Author

I can at least rebase/filter-branch out the directory capitalization for you

@theotherjimmy theotherjimmy force-pushed the new-porting-guide branch 2 times, most recently from 7f7299b to a2ba887 Compare July 2, 2018 16:59
@theotherjimmy
Copy link
Contributor Author

Alright, I have updated the engineering content, removed passive vioce where possible and re-did the formatting to match other documents in this repo. Now: how can we merge this with the other tutorial in this repo.

@iriark01
Copy link
Contributor

iriark01 commented Jul 2, 2018

I suggest we wait for Amanda. She's back on Monday.

Thank you for all your help!

@ashok-rao
Copy link
Contributor

@AnotherButler .. ping (hoping you are back in office)!

@AnotherButler
Copy link
Contributor

@ashok-rao I'm reviewing this, and then I may move it into our porting section. I hope to have my edits complete tomorrow morning my time.

Make initial edits for active voice, spacing and style.
@@ -0,0 +1,225 @@
## Mbed OS porting guide
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't see any of the images on this page. Do we want to include them here or delete them?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The last commit replaced all of them with the single tree structure at the bottom of the document.

- Requires the macro `CPU_DEVICE_1` to compile the vendor-provided HAL for the device mounted on the board.
- Requires the macro `FAMILY_MY_FAMILY` to compile the vendor-provided HAL for the family of the device.

All of these requirements directly map to relevant tags in the `targets.json` entry for our target. This is shown in step 3 below.
Copy link
Contributor

Choose a reason for hiding this comment

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

Note: We don't have a step 3 anymore. What does this reference?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The following step.

@theotherjimmy
Copy link
Contributor Author

@AnotherButler I think we can remove the "Amanda is on holiday. please hold." label (which I incidentally find funny).

@iriark01
Copy link
Contributor

Oh I put that there...

AnotherButler pushed a commit that referenced this pull request Jul 10, 2018
Add content to this page, so all porting target content is in one place.
@AnotherButler
Copy link
Contributor

Closing in favor of #625

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.

5 participants