You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2018-09-04 20:06:03 ~japaric we need someone to work on this
19
+
2018-09-04 20:06:10 ~japaric jamesmunns: are you actively working on this one?
20
+
2018-09-04 20:06:36 jamesmunns Not actively on the intro
21
+
2018-09-04 20:06:59 jamesmunns I marked the sections in progress from me ATM
22
+
2018-09-04 20:07:12 ~japaric anyone wants to volunteer to look work on this or look over it?
23
+
2018-09-04 20:07:23 ~japaric volunteer to work on this**
24
+
2018-09-04 20:07:37 @therealprof I'm such a terrible writer but I'd be happy to proof it.
25
+
2018-09-04 20:07:50 jamesmunns Happy to mentor anyone :) This one is partially implemented, but needs some filling out
26
+
2018-09-04 20:07:53 @therealprof What about pinging Nicoretti?
27
+
2018-09-04 20:08:27 ~japaric therealprof: sgtm, could you ping them?
28
+
2018-09-04 20:08:40 ~japaric therealprof: jamesmunns can I assign the issue to you as mentors / reviewers?
29
+
2018-09-04 20:08:48 @therealprof Doing it right away.
30
+
2018-09-04 20:08:59 jamesmunns Yep, thanks!
31
+
2018-09-04 20:09:33 ~japaric alright, thanks
32
+
2018-09-04 20:09:39 @korken89 I can also help proof reading
33
+
2018-09-04 20:09:59 @korken89 I would like to help write as well, but have a bit too much outside this ATM to dare take on something big
34
+
2018-09-04 20:10:07 ~japaric korken89: thanks, I'll add you as a collab so you can review PRs
35
+
2018-09-04 20:10:49 ~japaric ok, the next issue is the second chapter about writing the first program
36
+
2018-09-04 20:11:02 @ithinuel <- terrible writer but up for proof reading as well
37
+
2018-09-04 20:11:04 ~japaric I'll pull in some text from a quickstart PR
38
+
2018-09-04 20:11:19 ~japaric so I think that one is good for now
39
+
2018-09-04 20:11:32 jamesmunns We may want to ping sekineh, he is working on the CI still, and actively looking at QEMU atm
40
+
2018-09-04 20:11:50 ~japaric jamesmunns: +1
41
+
2018-09-04 20:12:12 ~japaric I'll ping them
42
+
2018-09-04 20:12:21 @therealprof I'd be happy to expand on the quickstart examples if needed.
43
+
2018-09-04 20:12:24 jamesmunns Thanks japaric
44
+
2018-09-04 20:12:43 ~japaric therealprof: please knock yourself out :-)
45
+
2018-09-04 20:13:06 ~japaric ok, issue 3 is about the collections chapter
46
+
2018-09-04 20:13:13 ~japaric a draft was merged last week
47
+
2018-09-04 20:13:26 ~japaric we have to decide if we want to add something else to the chapter
48
+
2018-09-04 20:13:33 ~japaric but we can do that on the issue
49
+
2018-09-04 20:13:59 ~japaric next issue (4) is about concurrency
50
+
2018-09-04 20:14:13 ~japaric this one is empty; I planned to write about interrupts and critical sections but haven't had the time
51
+
2018-09-04 20:14:57 @theJPster I'm quite looking forward to this section :)
52
+
2018-09-04 20:15:05 @theJPster It's the bit I've found trickiest about Monotron,.
53
+
2018-09-04 20:15:07 @therealprof What's the foundation for that?
54
+
2018-09-04 20:15:15 @therealprof RT or RTFM?
55
+
2018-09-04 20:15:44 ~japaric unless someone wants to volunteer this probably won't see much progress in the next few weeks
56
+
2018-09-04 20:15:50 cja whoops, late
57
+
2018-09-04 20:16:11 @adamgreig I might be able to help out with that and a few other sections next week but definitely not this week
58
+
2018-09-04 20:16:18 @therealprof Sounds like we have a volunteer. ;)
59
+
2018-09-04 20:16:37 ~japaric therealprof: more general than that. I planned to write about when a critical section is needed and where you can use e.g. a spsc lockless queue
60
+
2018-09-04 20:16:54 @korken89 japaric: If you want help with core parts of RTFM I can help write there, though I currently do not have experience with the Rust version of RTFM.
61
+
2018-09-04 20:16:55 ~japaric I would be writing `unsafe` code that's actually safe
62
+
2018-09-04 20:17:06 @therealprof Ah, cool.
63
+
2018-09-04 20:17:13 @therealprof Oooh. :-D
64
+
2018-09-04 20:17:18 cja Is the issue to work on the doc, or have someone go through it to see if it's consistent/coherent? I recall an issue last week about the OSX side?
65
+
2018-09-04 20:17:22 @theJPster Does that include atomics too?
66
+
2018-09-04 20:17:47 ~japaric theJPster: I had nothing planned about atomics
67
+
2018-09-04 20:17:58 @theJPster I think they're an important part of concurrency
68
+
2018-09-04 20:19:06 jamesmunns brb
69
+
2018-09-04 20:19:11 ~japaric if someone wants to write about atomics that'd be great :-)
2018-09-04 20:19:44 cja apologies, I should have dug in the backlog better
72
+
2018-09-04 20:20:01 ~japaric ok, let's move to issue 7 since jamesmunns is afk
73
+
2018-09-04 20:20:10 ~japaric tips for C devs
74
+
2018-09-04 20:20:12 @korken89 The nice thing about atomics is that they work more or less the same as in normal Rust, only on Cortex-M0 we do not have atomics sadly
75
+
2018-09-04 20:20:44 ~japaric no one's working on this atm. Any volunteers for writing this?
76
+
2018-09-04 20:21:51 ~japaric one of the topics is about cross compiling to embedded Linux; that should be too hard to cover
77
+
2018-09-04 20:21:58 ~japaric shouldn't be**
78
+
2018-09-04 20:21:59 @adamgreig I won't have time this week, but probably next week or after I'd be happy to have a go at this and the next one. if anyone else is interested please go ahead though.
79
+
2018-09-04 20:22:28 ~japaric adamgreig: thanks
80
+
2018-09-04 20:22:36 @therealprof I'm pretty much booked out I'm afraid… (also doing C stuff, grr…)
81
+
2018-09-04 20:22:58 ~japaric ok, let's revisit 7 next week
82
+
2018-09-04 20:23:07 @theJPster likewise, I'm afraid. Too many conferences!
83
+
2018-09-04 20:23:08 jamesmunns (back)
84
+
2018-09-04 20:23:23 ~japaric issue 8 is about mixing C and Rust code
85
+
2018-09-04 20:23:30 ~japaric no one's working on this atm
86
+
2018-09-04 20:23:39 ~japaric adamgreig may be able to work on it starting next week
87
+
2018-09-04 20:23:46 ~japaric any other volunteer for writing this?
88
+
2018-09-04 20:24:02 jamesmunns I will also ping spacekookie about it, who gave a talk at rustconf about this
89
+
2018-09-04 20:24:02 Lumpio- korken89: ...except on Cortex-M3 where LLVM seems to emit incorrect assembly sometimes which I discovered today
90
+
2018-09-04 20:24:06 Lumpio- But I can talk about that later
91
+
2018-09-04 20:24:24 ~japaric jamesmunns: thanks
92
+
2018-09-04 20:24:46 cja japaric: is there a single page with issues for today?
93
+
2018-09-04 20:24:47 @ryankurte I might be able to do a little on 8, though some of it is definitely over my head atm.
2018-09-04 20:25:16 @korken89 Lumpio-: :o Is there an tracking issue for this?
97
+
2018-09-04 20:25:21 cja thank you
98
+
2018-09-04 20:25:51 Lumpio- korken89: https://bugs.llvm.org/show_bug.cgi?id=38828 - I just filed it so it's unconfirmed on there but we went over the problem on #llvm and it seems to be an actual bug
99
+
2018-09-04 20:26:01 ~japaric ryankurte: I'll assign 8 to you so at least you'll be in the loop
100
+
2018-09-04 20:26:21 Lumpio- Might be good to keep in mind while working with atomics on Cortex-M3 for now
101
+
2018-09-04 20:26:21 ~japaric ok, let's move on
102
+
2018-09-04 20:26:35 ~japaric let's go over issue 5 and 6 now that jamesmunns is back
103
+
2018-09-04 20:27:05 ~japaric jamesmunns: I haven't had time to check your PR
104
+
2018-09-04 20:27:14 jamesmunns Issue 5 - I slightly mention embedded hal, and how the portability story works, but not much in depth
105
+
2018-09-04 20:27:22 jamesmunns maybe the intro page - ish
106
+
2018-09-04 20:27:45 awygle I would also like to help review, especially things around portability
107
+
2018-09-04 20:27:55 cja As someone new to rust embedded I'm happy to read anything written and provide feedback (being an intended reader, basically), but I'm not much help for writing the chapters myself tus far
108
+
2018-09-04 20:28:02 ~japaric I'll review the PR later this week. It'd be good if others reviewed it too
109
+
2018-09-04 20:28:21 jamesmunns PR is https://github.com/rust-embedded/book/pull/15 - if anyone wants to take a look :)
110
+
2018-09-04 20:28:53 jamesmunns There also used to be a "singletons" chapter, which I have renamed "peripherals"
2018-09-04 20:30:53 ~japaric korken89: I don't think so
125
+
2018-09-04 20:30:58 jamesmunns oh
126
+
2018-09-04 20:30:59 jamesmunns prs
127
+
2018-09-04 20:31:04 jamesmunns sorry :|
128
+
2018-09-04 20:31:06 ~japaric korken89: you can view the rendered markdown in the PR
129
+
2018-09-04 20:31:16 @korken89 Just hitting "view" in the Github PR seems to work :)
130
+
2018-09-04 20:31:26 ~japaric yeah, that's what I meant
131
+
2018-09-04 20:31:28 @therealprof Yes, most of the times.
132
+
2018-09-04 20:31:54 ~japaric ok, issue 9 is about the outline of the book
133
+
2018-09-04 20:32:14 ~japaric but we need more content to see if we are going to rearrange the chapters or split chapters
134
+
2018-09-04 20:32:17 ~japaric so blocked atm
135
+
2018-09-04 20:32:47 ~japaric issue 10 is about https://github.com/rust-embedded/book/issues/10
136
+
2018-09-04 20:32:54 ~japaric which was not originally planned for the book
137
+
2018-09-04 20:32:58 ~japaric but seems useful
138
+
2018-09-04 20:33:00 ~japaric ryankurte: ^
139
+
2018-09-04 20:33:18 ~japaric in particular I'd like to put OS specific stuff about GDB and OpenOCD there
140
+
2018-09-04 20:33:28 ~japaric to not duplicate it in other resources like the book and discovery
141
+
2018-09-04 20:33:54 ~japaric thoughts?
142
+
2018-09-04 20:34:05 emilgardis I think that's a great idea
143
+
2018-09-04 20:34:14 jamesmunns :+1: and link to the book from discovery?
144
+
2018-09-04 20:34:40 @korken89 Sounds good
145
+
2018-09-04 20:34:43 ~japaric jamesmunns: yes, though I'm not sure if this should go in the book (appendix?) or be a separate mdbook
146
+
2018-09-04 20:34:58 @ryankurte I can't remember where but iirc #10/#112 was deemed too much for the book?
147
+
2018-09-04 20:35:02 @ryankurte Ahh, ^
148
+
2018-09-04 20:35:12 ~japaric I was thinking if more obscure like which OpenOCD .cfg file for this board could live there
149
+
2018-09-04 20:35:20 ~japaric in which case it would essentially be like a wiki
150
+
2018-09-04 20:35:23 ~japaric but edited via PRs
151
+
2018-09-04 20:35:33 ~japaric more obscure stuff**
152
+
2018-09-04 20:35:36 jamesmunns Not opposed to using mdbook as a wiki :)
153
+
2018-09-04 20:36:03 @therealprof Which board? The F3 disco?
154
+
2018-09-04 20:36:53 ~japaric therealprof: I recently worked with a RM42 board (Cortex-R core) OpenOCD didn't work out of the box. Had to look for some "IDs" (DAP_ID, iirc?) online to make it work
155
+
2018-09-04 20:37:16 ~japaric the ID was in the data sheet but the value you had to use depended on which revision of the chip you were using
156
+
2018-09-04 20:37:35 ~japaric that's the kind of obscure stuff I'm referring to
157
+
2018-09-04 20:37:49 @therealprof Ah, yes.
158
+
2018-09-04 20:37:52 @adamgreig sounds not especially rust related so +1 on having it not in the book
159
+
2018-09-04 20:37:55 @ryankurte I still think it'd be excellent to have a flow-chart esque resource for getting code onto board and debug out. Maybe specific board support (and supported boards) could be it's own book/sub-book/subsection?
160
+
2018-09-04 20:37:59 @therealprof Especially since the last release is really old.
161
+
2018-09-04 20:38:44 @ryankurte And then the actual support could refer back to the book for more general openocd/jlink/whatever parts?
162
+
2018-09-04 20:39:32 emilgardis I think a wiki would be more fitting for specific board support @ryankurte
163
+
2018-09-04 20:40:10 ~japaric emilgardis: but this debugging resource would be a wiki in mdbook format
164
+
2018-09-04 20:41:18 emilgardis Aha, I suppose that'd work for me
165
+
2018-09-04 20:42:04 @ryankurte Yeah, whatever works / the wiki proposal didn't get a lot of love last time / I'm happy with either.
166
+
2018-09-04 20:42:04 @ryankurte I'm mostly suggesting that the content here (https://github.com/rust-embedded/book/issues/10#issue-349356813) be separate from specific board support stuff somewhere else.
167
+
2018-09-04 20:42:50 ~japaric let's try to make a decision: who's in favor of an additional mdbook that covers the stuff in the above link ^?
168
+
2018-09-04 20:43:15 jamesmunns generally :+1:, any reason it is limited to just debugging, vs "embedded wiki powered by mdbook"?
169
+
2018-09-04 20:43:28 @korken89 +1
170
+
2018-09-04 20:43:28 @adamgreig I don't think it belongs in the main book, happy for it to be its own mdbook, could also be some sort of wiki
171
+
2018-09-04 20:43:34 emilgardis +1
172
+
2018-09-04 20:43:38 @adamgreig so let's say +1
173
+
2018-09-04 20:44:07 @therealprof +1
174
+
2018-09-04 20:44:42 posborne +1
175
+
2018-09-04 20:44:43 ~japaric jamesmunns: it could be extended into a embedded wiki in the future. I'm trying to get some initial decision right now; we can revisit the wiki idea
176
+
2018-09-04 20:44:44 @nastevens Take my vote with a grain of salt, but +1
177
+
2018-09-04 20:45:19 ~japaric that sounds like the majority of the present
178
+
2018-09-04 20:45:34 ~japaric now, who volunteers for writing this?
179
+
2018-09-04 20:46:36 ~japaric they don't have to write the whole thing at once. Starting with a skeleton (see book) is fine.
180
+
2018-09-04 20:46:43 @ryankurte I'm happy to work on the New Book (and I think there were others in the thread) ^_^
181
+
2018-09-04 20:47:16 @ryankurte What is the status of the debugging section in The Book, then? Separate issue to track what should be included there?
182
+
2018-09-04 20:47:18 @korken89 I can help with filling out, but I am a bit pressed for free time right now (and coming 2 weeks)
183
+
2018-09-04 20:47:38 ~japaric ryankurte: the issue would be moved into the new repo
184
+
2018-09-04 20:48:02 ~japaric ryankurte: I'll make a new repo and add you and /resources as collabs
185
+
2018-09-04 20:48:14 @ryankurte I'd still argue for some mention of programming / debugging etc. in the book, but, works for me!
186
+
2018-09-04 20:48:19 @therealprof Same. But FWIW I do have a lot of the hardware mentioned in the ticket here.
187
+
2018-09-04 20:49:13 DaQue_ I’m really new to rust. Any reason I shouldn’t be able to switch between using Xargo and the new method the nightly is using any time I want. A lot of beginner tutorial stuff still uses Xargo
188
+
2018-09-04 20:50:26 ~japaric DaQue_: short version is that you shouldn't use Xargo or follow material that uses Xargo
189
+
2018-09-04 20:50:35 ~japaric continuing the triage
190
+
2018-09-04 20:50:45 ~japaric next issue is 11, the embedded Rust showcase
191
+
2018-09-04 20:50:53 ~japaric the RFC was approved
192
+
2018-09-04 20:51:00 DaQue_ Thanks
193
+
2018-09-04 20:51:02 ~japaric but still need someone to implement this
194
+
2018-09-04 20:51:13 ~japaric any volunteer?
195
+
2018-09-04 20:51:42 ~japaric I think the hardest part would be finding a template
196
+
2018-09-04 20:51:55 ~japaric or we could start with just a README.md
![bors[bot]](https://avatars.githubusercontent.com/in/1847?v=4&size=40){kind=avatar}
0 commit comments