First Newsletter #66
First Newsletter #66
Conversation
|
Closes #58 |
newsletters/2018-03-15.md
Outdated
|
|
||
| > 2018-03-15 | ||
|
|
||
| This is the first newsletter of the [Embedded WG]! We will be releasing this newsletter on a bi-weekly basis, and looking to highlight new progress, cool project, thanking the community, and advertising projects that need help! |
There was a problem hiding this comment.
The second sentence reads a bit off; I think it should be something like: "and (we?) are looking to highlight new progress and cool projects, thanking the community, and advertising projects that need help!"
newsletters/2018-03-15.md
Outdated
| * [pcein] has released the third weekly driver for the [`adc-mcp3008`], an 8-channel 10-bit ADC. | ||
| * [dvc94ch] has created the [riscv-rust] organization for all your embedded RISCV needs! | ||
| * [dylanmckay] has begun [rebasing][avr-rust-rebase] the avr-rust/rust fork onto a recent rust-lang/rust version, bringing in LLVM 6.0 support. | ||
| * [japaric] has released the fourth weekly driver for the enc28j60, an Ethernet controller with SPI interface. |
There was a problem hiding this comment.
the link to the blog post seems to have been lost during copy-editing
newsletters/2018-03-15.md
Outdated
| * [dvc94ch] has created the [riscv-rust] organization for all your embedded RISCV needs! | ||
| * [dylanmckay] has begun [rebasing][avr-rust-rebase] the avr-rust/rust fork onto a recent rust-lang/rust version, bringing in LLVM 6.0 support. | ||
| * [japaric] has released the fourth weekly driver for the enc28j60, an Ethernet controller with SPI interface. | ||
| * [dbrgn] has released the fifth weekly driver for the mcp3425, a 16-bit ADC with I2C interface. |
|
@jamesmunns Thanks for putting this together. It looks good to me. I'm wondering if it may be a good idea to batch the weekly driver stuff under its own section and have that as a recurrent topic? In that section we could mention the drivers that are currently WIP so people don't end working on the same thing in isolation but instead collaborate. That section could also be used to have more people join the initiative by pointing them to #39. |
|
@japaric Are the requirements for a driver to be considered released instead of WIP mentioned somewhere? I also think it would be a good thing to mention drivers which are WIP somewhere more prominently as #39 is becoming rather unwieldy and I the information seems to be spread/duplicated over a few places now. |
#39 says:
But if you want me to put your driver in the released bucket just let me know. As long as it's on crates.io it's fine.
We could put a snapshot of the WIP list in the newsletter.
I update the WIP / released list in #39 at least once a week. I think that's the most extensive list at the moment. |
Some drivers are so simple or similar that I don't think we'll see a lot dedicated posts explaining every one them. I'd tie the WIP state to the usability, i.e. is there some (inline) documentation, are most (if not all) of the hardware capabilities covered, do examples exist? I always try to validate my code with at least two different
It sure is, but it's getting rather long and there're lots of posts and it's also not that easy to find if you don't happen to stumble over a link to it. I think it would be great if there was a dedicated page capturing more information about the platforms and drivers allowing to present the current state, the plans and also a wishlist in a more comprehensible and searchable way to connect interested people together for collaboration and gain the interest of newcomers. I'd be happy to put some time into that, for instance I have a boatload (best guess 300) of sensors and actors which could use drivers (=> wishlist) and I'd be also happy to help out and test. Similarly I have around 60 MCUs from 8 different versions here (some of which one few know that they do exist like On Semiconductor, Infineon and Maxim) which could use HAL implementations. I am somewhat time constrained so I think we should multiply wherever possible... |
|
@japaric back at you. Rendered: https://github.com/jamesmunns/embedded-wg/blob/first-newsletter/newsletters/2018-03-15.md @therealprof I support having a central index somewhere (#39 is probably the best index so far), we may want a separate issue to track that (not just for drivers, but also for svd2rust crates, |
newsletters/2018-03-15.md
Outdated
|
|
||
| ### `embedded-hal` drivers | ||
|
|
||
| * [japaric] has [released][enc-blog] the fourth weekly driver for the [`enc28j60`], an Ethernet controller with SPI interface. |
There was a problem hiding this comment.
It seems that pcein (weekly driver 3) went missing in the latest edit
There was a problem hiding this comment.
Also caught the link to the blog in a second commit
|
|
||
| If you have an embedded project or blog post you would like to have featured in the Embedded WG Newsletter, make sure to mention it on the tracking issue for [the next newsletter], we would love to show it off! | ||
|
|
||
| ### `embedded-hal` drivers |
There was a problem hiding this comment.
I think it would be good to link to #39 before the list and mention that this is part of the weekly driver initiative and that (at the time of writing) there are 10+ drivers in WIP state.
Here is a first draft of the first newsletter styled after the old Impl period newsletters.
In the future we should have a list of projects to watch for updates :)