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-10-16 20:17:28 ~japaric next issue, #6, static guarantees
45
+
2018-10-16 20:17:42 @jamesmunns https://github.com/rust-embedded/book/pull/35 is written (woo!) and waiting for reviews
46
+
2018-10-16 20:17:51 @jamesmunns that at least covers the type-state programming stuff
47
+
2018-10-16 20:18:16 ~japaric \o/
48
+
2018-10-16 20:18:20 thenewwazoo I'll check that out too - I've been writing a bunch of that also
49
+
2018-10-16 20:18:41 @jamesmunns very open to PRs, either on theory, ways to refactor the sample code, soundness of examples, etc
50
+
2018-10-16 20:18:53 thenewwazoo +1
51
+
2018-10-16 20:19:08 @jamesmunns (PRs or just comments)
52
+
2018-10-16 20:19:52 @theJPster Can flag up that I'd like to return to issue #2 and PR 42 when we get to a good point. I have a clarifying question I'd like to ask.
53
+
2018-10-16 20:21:14 ~japaric theJPster: sure, after we have gone through the milestone issues
54
+
2018-10-16 20:21:26 ~japaric issue #7 is C/C++ tips
55
+
2018-10-16 20:21:35 ~japaric adamgreig: any news on this one?
56
+
2018-10-16 20:22:11 ~japaric iirc, korken89 was offline last week
57
+
2018-10-16 20:22:17 @adamgreig working on it, haven't chatted to korken89 yet
58
+
2018-10-16 20:22:22 @adamgreig open to tip suggestions from anyone
59
+
2018-10-16 20:22:31 @adamgreig suspect this will be more of a grab-bag chapter
60
+
2018-10-16 20:22:34 thenewwazoo got an issue or anything with notes?
61
+
2018-10-16 20:22:42 thenewwazoo yeah, somewhere to drop "one time I tried to ..."
62
+
2018-10-16 20:22:48 @adamgreig not up... will try and sort something after meeting
2018-10-16 20:23:22 @therealprof thenewwazoo: You mean the FAQ?
65
+
2018-10-16 20:23:41 @adamgreig therealprof: this is specifically tips for embedded c developers coming to rust
66
+
2018-10-16 20:23:43 thenewwazoo no, i think #9 is what I'm asking for
67
+
2018-10-16 20:23:45 @jamesmunns I think this chapter was "no, iterators are not expensive, we promise"
68
+
2018-10-16 20:23:57 @adamgreig "except.. sometimes... best check the assembler"
69
+
2018-10-16 20:23:57 @jamesmunns and the like
70
+
2018-10-16 20:24:09 @therealprof :-D
71
+
2018-10-16 20:24:13 ~japaric thenewwazoo: requested topics so far are in this comment https://github.com/rust-embedded/book/issues/9#issuecomment-414668903
72
+
2018-10-16 20:24:17 thenewwazoo +1
73
+
2018-10-16 20:25:18 ~japaric adamgreig: (and the disassembly shows 100+ instructions thanks to loop unrolling ...)
74
+
2018-10-16 20:25:24 @adamgreig haha yea...
75
+
2018-10-16 20:25:26 @jamesmunns putting this down now so I don't forget: after the issues I'd like to talk about the travisci situation
2018-10-16 20:26:13 ~japaric moving on, issue #8 C / Rust interop
80
+
2018-10-16 20:26:21 @adamgreig https://github.com/rust-embedded/book/pull/23 was merged
81
+
2018-10-16 20:26:28 @jamesmunns PRs 23 and 45 have landed
82
+
2018-10-16 20:26:34 @jamesmunns 51 is on its way
83
+
2018-10-16 20:26:45 @jamesmunns so we have a first pass at this chapter landed :)
84
+
2018-10-16 20:26:55 ~japaric nice
85
+
2018-10-16 20:27:47 hannobraun (have to go, be right back)
86
+
2018-10-16 20:27:49 ~japaric what's left to cover after this?
87
+
2018-10-16 20:28:02 * japaric hasn't look at the diffs
88
+
2018-10-16 20:28:08 @jamesmunns for C/C++ interop? we initially talked about stuff like working with FreeRTOS
89
+
2018-10-16 20:28:27 @jamesmunns but this covers the "a little C with your rust" and "a little rust with your C" completely, if not minimally
90
+
2018-10-16 20:28:57 @ryankurte I still haven't PRd anything build system interop related, but iirc from last time we were not sure it'd go there.
91
+
2018-10-16 20:28:59 @jamesmunns always could be more verbose, open to PRs extending this
92
+
2018-10-16 20:29:08 @ryankurte 👍
93
+
2018-10-16 20:29:28 @jamesmunns I think it makes sense there, not sure what the previous discussion was
94
+
2018-10-16 20:30:40 ~japaric I saw https://github.com/rust-embedded/wg/issues/238 in my inbox is it related to this chapter?
95
+
2018-10-16 20:31:14 @ryankurte I think so, maybe we need examples of what works rn and what is in progress.
96
+
2018-10-16 20:31:25 @jamesmunns yes IMO
97
+
2018-10-16 20:33:03 hannobraun (I'm back)
98
+
2018-10-16 20:33:23 ~japaric should we block the interop chapter issue on solving #238?
99
+
2018-10-16 20:33:32 @jamesmunns well, maybe. I need to see what exists in core::raw for thumb* targets
100
+
2018-10-16 20:34:11 ~japaric there are no c types in core, iirc
101
+
2018-10-16 20:34:37 @jamesmunns huh.
102
+
2018-10-16 20:34:48 @jamesmunns Yeah, I'd say we need to revisit this
103
+
2018-10-16 20:35:14 ~japaric jamesmunns: can you add a comment to the interop chapter issue?
104
+
2018-10-16 20:35:23 @jamesmunns will do
105
+
2018-10-16 20:35:24 ~japaric I'll add looking at this issue to my todo list
106
+
2018-10-16 20:35:55 @jamesmunns looks like gbip possibly volunteered to address in https://github.com/rust-lang/libc/issues/375
107
+
2018-10-16 20:36:59 ~japaric moving on, issue #9, outline
108
+
2018-10-16 20:38:03 @therealprof I'm wondering where we're going to link to the FAQ.
109
+
2018-10-16 20:38:24 ~japaric jamesmunns: related to this and the webpage do you think we should freeze some chapter names / links in the book for the public beta of the website?
110
+
2018-10-16 20:38:52 @jamesmunns sgtm
111
+
2018-10-16 20:39:13 @therealprof We have a lot of feedback here on IRC the last week and I intend to turn it into FAQ items so we can just point to them. However the FAQ is not easy to find ATM.
112
+
2018-10-16 20:39:13 @jamesmunns Do you want me to make an issue listing the linked sections, and get a final approval from @resources?
2018-10-16 20:40:09 ~japaric therealprof: any suggestion on where to put the faq link?
115
+
2018-10-16 20:40:14 @jamesmunns japaric: will do
116
+
2018-10-16 20:40:16 ~japaric I can add it to this channel topic
117
+
2018-10-16 20:41:16 @therealprof People where reading "the" book and the discovery book. I was hoping we could add further reading suggesting and FAQ as the last section in each of them.
118
+
2018-10-16 20:41:41 @jamesmunns I'd go so far and at least mention it on the landing/starting page of each too
119
+
2018-10-16 20:42:06 @therealprof The channel topic is very long already, it's already cropped on my client.
120
+
2018-10-16 20:42:41 ~japaric linking the faq from the landing page of the books sgtm
121
+
2018-10-16 20:42:53 ~japaric they could also link back to docs.r-e.o
122
+
2018-10-16 20:43:15 @adamgreig sounds good
123
+
2018-10-16 20:43:37 @therealprof +1
124
+
2018-10-16 20:43:45 @adamgreig the new intro chapter in the book already has links to the bookshelf (in #40)
125
+
2018-10-16 20:43:49 cr1901 +1
126
+
2018-10-16 20:44:00 ~japaric +1 to which option?
127
+
2018-10-16 20:44:09 @adamgreig so just include the faq there, and put something similar in the other landing pages
128
+
2018-10-16 20:44:11 cr1901 "linking the faq from the landing page of the books"
129
+
2018-10-16 20:44:37 @therealprof That one.
130
+
2018-10-16 20:45:32 ~japaric therealprof: adamgreig could one of you make issues about adding links to the bookshelf / faq on the book repos that don't have them?
131
+
2018-10-16 20:46:04 ~japaric if you tag them with help-wanted / hacktoberfest they should get done relatively quickly
132
+
2018-10-16 20:46:12 ~japaric or you directly make PRs
2018-10-16 20:47:31 ~japaric ryankurte: any update on the other book
139
+
2018-10-16 20:47:35 ~japaric moving on to issue #10
140
+
2018-10-16 20:48:26 @ryankurte A little more work but no more PRs yet
141
+
2018-10-16 20:48:50 ~japaric ryankurte: ok, thanks for the update
142
+
2018-10-16 20:48:59 @ryankurte I've gotta find an example of all the tools I have and make sure the instructions are right / write the ones that aren't there yet.
143
+
2018-10-16 20:49:37 ~japaric ryankurte: +1, thanks for working on this
144
+
2018-10-16 20:50:10 ~japaric re issue #11, the showcase. I'll probably take a stab at it this weekend
145
+
2018-10-16 20:50:18 cr1901 I'm tagged in the open issue for the embedded showcase; I'm still eager to add AT2XT to the showcase. The reason I haven't yet is, well... it still doesn't compile due to the LLVM atomics issue :)
146
+
2018-10-16 20:50:26 ~japaric if no one is working on it
147
+
2018-10-16 20:50:43 cr1901 Last I checked, awygle and I agreed on the fix, just hasn't been impl'd yet.
148
+
2018-10-16 20:50:54 @therealprof That'd be great. I'm so bad at starting such things. :/
149
+
2018-10-16 20:51:19 ~japaric cr1901: I'll try to make a PR for that this weekend or next week
150
+
2018-10-16 20:51:49 cr1901 japaric: Okay to remind you next week if I don't see anything and/or I haven't done it myself?
151
+
2018-10-16 20:51:58 cr1901 Tyvm, btw
152
+
2018-10-16 20:52:01 ~japaric cr1901: sure
153
+
2018-10-16 20:52:25 ~japaric re issue #12, I need to check back on sekineh's PR; will likely do that during the weekend
154
+
2018-10-16 20:52:47 ~japaric issue #19, ryankurte do you have access to the dns records?
155
+
2018-10-16 20:53:41 ~japaric issue #20, webpage should be mostly done. any other updated on that jamesmunns?
156
+
2018-10-16 20:53:44 @ryankurte not at the moment, I can maybe get my aws account added for the interim where we don't have any automation tho.
157
+
2018-10-16 20:54:03 @therealprof NB: There were a lot of strange issues the last few days.
158
+
2018-10-16 20:54:33 ~japaric ryankurte: could you contact nastevens to see if they can give you access?
159
+
2018-10-16 20:54:39 @therealprof Certificate mismatches, etc. and the images are partially broken (again).
160
+
2018-10-16 20:54:46 @ryankurte yep yep
161
+
2018-10-16 20:55:03 ~japaric ryankurte: thanks
162
+
2018-10-16 20:55:25 @ryankurte therealprof: coercing github into hosting things is sometimes more wonky than I would hope, once we've got it right it should be stable.
163
+
2018-10-16 20:55:31 ~japaric theJPster: jamesmunns you had some topics you wanted to discuss
164
+
2018-10-16 20:55:40 ~japaric we have 5 mins left though
165
+
2018-10-16 20:55:46 @theJPster Last week I picked up an issue to write something on "registers and semihosting"
166
+
2018-10-16 20:56:15 @theJPster Can anyone remember what was meant by "registers"? I did a section on memory mapped peripheral registers, but that seems to duplicate text elsewhere.
167
+
2018-10-16 20:56:45 @jamesmunns re: travis ci, svd2rust and cross take a long time to build, and rust-embedded shares a single runner across all project. This is annoying as it blocks little PRs that take 5s to build for up to 12 hours, or causes bors timeouts
168
+
2018-10-16 20:57:00 @theJPster jamesmunns, can we add more runners?
169
+
2018-10-16 20:57:15 @jamesmunns theJPster: it costs money, probably. not sure what the pay scale is for open source
170
+
2018-10-16 20:57:38 @adamgreig we might be able to just ask for more runners
171
+
2018-10-16 20:58:05 ~japaric theJPster: sorry, I probably wasn't clear. chapter 2 is more practical so "registers" was about the existing API in cortex-m / svd2rust
172
+
2018-10-16 20:58:17 @jamesmunns I wanted to volunteer to at least help pay for a second runner, if thats what we decide the best solution is (either as me, or as ferrous).
173
+
2018-10-16 20:58:34 @jamesmunns if we can just ask nicely, thats cool too though :)
174
+
2018-10-16 20:59:55 @theJPster japaric, hmm. We probably need to chat on https://github.com/rust-embedded/book/issues/46 because I'm a bit confused. Sorry.
175
+
2018-10-16 21:00:17 ~japaric jamesmunns: we can probably shrink the build time of svd2rust by commenting out some device crates, but would be hard to do so for cross
176
+
2018-10-16 21:00:37 @jamesmunns theJPster: I think the page you wrote would fit really well in the Peripherals section, and theres basically a placeholder waiting for it already
177
+
2018-10-16 21:00:52 @adamgreig their commercial rates are $130/mo for 2 runners, so I definitely think asking nicely first is a worthwhile shot
178
+
2018-10-16 21:01:35 @theJPster jamesmunns, which is fine. But I'm not sure what needs to go in the hole that leaves.
179
+
2018-10-16 21:01:46 cr1901 Can someone add my name to the Attendance on my behalf (I give permission)? I keep forgetting to sort out Dropbox issues...
180
+
2018-10-16 21:02:12 @theJPster Oh, in other news. I'm at the Engineering Design Show in Coventry, UK tomorrow, then flying to Detroit for Rust Belt Rust.
181
+
2018-10-16 21:02:13 @adamgreig done
182
+
2018-10-16 21:02:15 ~japaric idea: we could move cross to one of the WG members account (or to a new rust-embedded-nursery account) to not have it stall other repos
183
+
2018-10-16 21:02:19 cr1901 adamgreig: tyvm
184
+
2018-10-16 21:02:27 @theJPster Then next week I am giving some Rust training to colleagues, so I won't be at the meeting.
185
+
2018-10-16 21:02:45 @theJPster I wrote an Embedded Rust workshop. It looks kind fun, if I do say so myself.
186
+
2018-10-16 21:02:45 @jamesmunns japaric: do you want to send an email to [email protected], and include my ferrous email on CC?
187
+
2018-10-16 21:02:52 @jamesmunns theJPster: nice!
188
+
2018-10-16 21:03:19 @jamesmunns (I can also send the email, but you are the owner of the account)
189
+
2018-10-16 21:03:25 thenewwazoo adamgreig (concurrency) and jamesmunns (HAL/portability) - I have to run but will be back in an ~hourish
2018-10-16 21:03:45 @jamesmunns thenewwazoo: no problem, I have to go cook dinner too. Chat on the issue?
192
+
2018-10-16 21:03:55 @theJPster It's four hours of a) install the tools, b) clone the quickstart repo, c) blink an LED with an svd2rust generated chip crate, d) do some serial with a chip-hal crate.
193
+
2018-10-16 21:04:22 thenewwazoo jamesmunns: "chat on the issue"?
194
+
2018-10-16 21:04:42 @jamesmunns I just mean talk about this on the github issue, rather than IRC
195
+
2018-10-16 21:04:43 @theJPster Then I've got a Seeed studio grove starter kit full of random sensors and bits and bobs they can play with. Like an I2C LCD and a stepper motor.
196
+
2018-10-16 21:04:49 @jamesmunns I may not be available in 1 hour
197
+
2018-10-16 21:05:01 @ryankurte oh, is everyone ok with / anyone opposed to adding octobox.io as an app on the rust-embedded org? Means we'd get state information there. I can do it, just figured it'd be worth checking.
198
+
2018-10-16 21:05:09 thenewwazoo jamesmunns: works for me
199
+
2018-10-16 21:05:13 @jamesmunns +10 from me ryankurte
200
+
2018-10-16 21:05:22 @adamgreig yea +1 octobox
201
+
2018-10-16 21:05:26 @jamesmunns my poor inbox is so sad with github notifications
202
+
2018-10-16 21:05:46 @ryankurte jamesmunns: yeah I have just written off that tab in gmail
203
+
2018-10-16 21:05:54 hannobraun ryankurte: I don't mind
204
+
2018-10-16 21:06:01 thenewwazoo that tells me I should poke people in IRC about PRs :-p
205
+
2018-10-16 21:06:08 ~japaric I'm going to officially end this meeting. Thanks everyone for attending!
![bors[bot]](https://avatars.githubusercontent.com/in/1847?v=4&size=40){kind=avatar}
0 commit comments