-
Notifications
You must be signed in to change notification settings - Fork 0
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
Draft/wsl2 firmware development #1
base: master
Are you sure you want to change the base?
Conversation
@JPHutchins this is awesome!! 👍 👍 👍 . Thank you for taking the initiative! Is there a way to view the rendered post? |
I went through the process defined in the README to get it running. At
first I ignored that they had locked the Ruby version so I had to backtrack
and install rbenv to get the specific Ruby. I also had to do some funny
business to use a ruby build of openssl.
I should have just used the docker thing they recommended!
…On Mon, Jul 29, 2024 at 3:13 PM Dave Desrochers ***@***.***> wrote:
@JPHutchins <https://github.com/JPHutchins> this is awesome!! 👍 👍 👍 .
Thank you for taking the initiative!
Is there a way to view the rendered post?
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AIESQLVB3LMV6IYKLSG7QPDZO25B7AVCNFSM6AAAAABLVCRKIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENJXGA4TSOJWGE>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
I cloned it to windows to test the docker setup. It didn't go to well since it also seems to have grabbed the wrong Ruby:
You'll get this error
And if you look at the docker pull it's getting Ruby 3.2.4 when it should get 2.7.7:
IDK |
I got it working by changing the top of the Dockerfile:
So, I will recommend the docker approach. |
Adding the --incremental flag speeds things up a bit
|
@JPHutchins is it possible to save the HTML and assets and send it in zip via slack or GDrive? |
I think this worked, attached here: This was created with Chrome "save as". Unzip it and open the "WSL2 for Firmware Development _ Interrupt.html" file. |
@JPHutchins this is great! Can you put the "intercreate" string to a hyperlink to https://www.intercreate.io ? Also, you should do the same for "Framework 16" :) Maybe could add a few more too.. .like "Zephyr" and "VMWare Workstation" and even "WSL2" More hyperlinks should provide more hits to the article, right? |
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 have a few minor comments. In general, I love it. Is there a way you can have your author name and possibly link to your Github somewhere in there?
_drafts/wsl2-firmware-development.md
Outdated
|
||
The performance differences between WSL2 and bare metal | ||
Linux are [small](https://www.phoronix.com/review/windows11-wsl2-zen4/5), | ||
[will continue shrinking](https://www.phoronix.com/news/Microsoft-WSL2-Linux-6.6-Kernel) |
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.
there is a space here in between "shrinking" and the ","
_drafts/wsl2-firmware-development.md
Outdated
|
||
A benchmark shouldn't take too long, yet it should be long enough that it | ||
smooths over some run-to-run issues you might see—_what are | ||
Windows Defender and Windows Update up to during the run🔍?_. A build-only twister |
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.
LOL
@JPHutchins @robhelvestine a thought. The article is long enough to be split up into 2 or 3 articles
Not sure if that's an option.. just thinking about it 'cause people's attention span to online articles are too short.. also could maybe help with SEO by referring articles? |
Yea not a bad idea. I would say split into two articles: 1 pre-tutorial, and 1 tutorial |
I like this idea and I think it makes it more likely to get approved by the editors. Leaves me tempted to flesh out the article with VMWare benchmarks, but man, it would require
Optimistically like 2 hours of work. Similarly, tempted to benchmark my partner's M3 MacBook... |
dunno about you, but I'm certainly curious of the differences :) It
certainly 'feels' similar in performance for me
Dave Desrochers
intercreate
415-944-9987
…On Fri, Aug 2, 2024 at 1:06 PM JP Hutchins ***@***.***> wrote:
Yea not a bad idea. I would say split into two articles: 1 pre-tutorial,
and 1 tutorial
I like this idea and I think it makes it more likely to get approved by
the editors.
Leaves me tempted to flesh out the article with VMWare benchmarks, but
man, it would require
1. download VMWare
2. Install linux
3. setup the environment
4. run the benchmarks
5. record results and add to article
Optimistically like 2 hours of work.
Similarly, tempted to benchmark my partner's M3 MacBook...
—
Reply to this email directly, view it on GitHub
<#1 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAFVCRNKUYAOQM2AQ3TXKN3ZPPRF7AVCNFSM6AAAAABLVCRKIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENRWGA3DMMBYGA>
.
You are receiving this because your review was requested.Message ID:
***@***.***>
|
I could run something on a M2 MacBook if needed |
It would be great! Hopefully it's clear enough how it was done from the Fixture section. |
@davedesro Thanks for the review! Updates are pushed and I've attached new previews. |
Real PR here: memfault#515 |
Draft PR showing what our PR article submission to Memfault / Interrupt would look like. I'd really appreciate proof reading and review, I know there's still lots to clean up. Lightweight promoting Intercreate but I don't know if it's too blatant or too subtle.
Have a hard time switching between fact and opinion sometimes.