<re_irc>
< (@diondokter:matrix.org)> Ok, not great, but you can set ""git.autoRepositoryDetection": "subFolders""
IlPalazzo-ojiisa has joined #rust-embedded
limpkin has quit [Ping timeout: 256 seconds]
limpkin has joined #rust-embedded
<re_irc>
< (@thejpster:matrix.org)> > tm4c HAL
<re_irc>
There’s a name I haven’t heard in a while
limpkin has quit [Ping timeout: 255 seconds]
<re_irc>
<Ralph> would it be an option for e-h if i'd make a PR to re-add "PwmPin" to 1.0 (it was in 0.x but was dropped for 1.0), this time with a generic "Duty"? see the discussion here: https://github.com/rust-embedded/embedded-hal/issues/358
<re_irc>
this is being used in some drivers, e.g.:
<re_irc>
if this is not present in 1.0 such drivers will be stuck on 0.x which might lead to issues in the future (i guess once 1.x is out the existing HALs will upgrade to that and eventually drop e-h 0.x support and new HALs will only support e-h 1.x from the beginning)
limpkin has joined #rust-embedded
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #rust-embedded
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #rust-embedded
crabbedhaloablut has quit [Remote host closed the connection]
crabbedhaloablut has joined #rust-embedded
<re_irc>
< (@jpc:ejpcmac.net)> Hello all! I’m working at NXP Semiconductors, and will drive a project for evaluating Rust to program our UWB/NFC chips starting in January. For this purpose, I’m currently looking for a contractor to help us develop HALs, protocol layers, and an UWB Application firmware on an existing platform. Our team is located in Caen, France. I’m not sure if it’s the right place to ask, but don’t hesitate to...
<re_irc>
... ping me for more info if you’re interested to participate in this exciting adventure :)
crabbedhaloablut has quit [Write error: Connection reset by peer]
crabbedhaloablut has joined #rust-embedded
<re_irc>
< (@diondokter:matrix.org)> : sent you a DM on matrix :)
<re_irc>
< (@jamesmunns:beeper.com)> I'm likely not available then, so I won't throw my hat in, but nothing but good things to say about and the TweedeGolf folks :D
<re_irc>
< (@ryan-summers:matrix.org)> does "let version - env!("CARGO_PKG_VERSION")" work in embedded i.e. are environment variables embedded at compile time or run time?
<re_irc>
< (@ryan-summers:matrix.org)> * =
<re_irc>
< (@ryan-summers:matrix.org)> I guess would have to be compile time, but I'm not sure
<re_irc>
< (@jamesmunns:beeper.com)> I think the _macro_ is compile time, the std method is runtime
<re_irc>
< (@jamesmunns:beeper.com)> I always have to recheck tho. There's definitely a compile-time one.
<re_irc>
< (@ryan-summers:matrix.org)> The macro indeed appears to be compile-time. I think "std::env::var()" is runtime
<re_irc>
< (@ryan-summers:matrix.org)> Now I see the confusion, thanks for pointing this out :)
<re_irc>
< (@jamesmunns:beeper.com)> > Inspects an environment variable at compile time.
<re_irc>
< (@ryan-summers:matrix.org)> Interesting. Can you even have an environment in a no-std context?
<re_irc>
< (@ryan-summers:matrix.org)> Ah wait that is compile time too
<re_irc>
< (@jamesmunns:beeper.com)> Nope! That's why it's "core::env!()", not "core::env" (the module)
<re_irc>
< (@korken89:matrix.org)> Linker magicians, assemble! Is there a way to add a variable to ".data" via linker script that later can be used via extern static? If I'm "in" the large linker script I could do "_a_var = 123;" but is there a way to add it in an extra linker script?
<re_irc>
< (@korken89:matrix.org)> Large linker script = the one from "cortex-m-rt"
<re_irc>
< (@korken89:matrix.org)> I guess one can use "INSERT AFTER .data" maybe
<re_irc>
< (@korken89:matrix.org)> I see that "cortex-m-rt" has answered that for me 😅
<re_irc>
< (@jaxter184:matrix.org)> not sure what the stance is in here on cryptocurrency, but the rust embedded working group twitter recently retweeted a vocal bitcoin proponent, just wanted to give yall a heads up in case yall are as anti-cryptocurrency as i am
<re_irc>
< (@dirbaio:matrix.org)> I don't think the WG should cancel someone based on their views on crypto...
<re_irc>
< (@dirbaio:matrix.org)> the tweet in question seems relevant to me, and has nothing about crypto in it
<re_irc>
< (@jaxter184:matrix.org)> reasonable
<re_irc>
< (@jaxter184:matrix.org)> just wanted to make sure it wasnt unintentional
<re_irc>
< (@jaxter184:matrix.org)> and id say its not really cancelling, im not asking them to like denounce them or anything like that, i just know that i personally would make sure that im platforming people with a net positive impact in the world, at least to the extent that i can reasonably confirm
<re_irc>
< (@dirbaio:matrix.org)> I didn't RT it, it was probably
<re_irc>
< (@jaxter184:matrix.org)> either way, no biggie, just something i noticed
<re_irc>
< (@jaxter184:matrix.org)> and id say its not really cancelling, im not asking the wg to like denounce them or anything like that, i just know that i personally would make sure that im platforming people with a net positive impact in the world, at least to the extent that i can reasonably confirm
<re_irc>
< (@jamesmunns:beeper.com)> I retweeted it, hasn't looked at the profile tho
<re_irc>
< (@jaxter184:matrix.org)> i mean the tweet itself is neat
<re_irc>
< (@jaxter184:matrix.org)> cool to see more riscv rust stuff
<re_irc>
< (@jaxter184:matrix.org)> and im sure anyone who looks at their profile can make their own judgements
<re_irc>
< (@dirbaio:matrix.org)> retweeting a pic of a hello world is not "platforming"
<re_irc>
< (@dirbaio:matrix.org)> IMO retweeting a pic of a hello world is not platforming
<re_irc>
< (@jaxter184:matrix.org)> also reasonable
<re_irc>
< (@jaxter184:matrix.org)> imo both are platforming, but yeah, the second one is much more significant
causal has joined #rust-embedded
<re_irc>
< (@adamgreig:matrix.org)> we're actually in the middle of writing a short policy on what the social media accounts do, https://github.com/rust-embedded/wg/pull/651, so this might be worth capturing! personally I think that when the tweet itself is entirely on-topic it's fair enough to rt it (or choose not to if the person running the account doesn't want to, it's at their digression), beyond that there are some other interests...
<re_irc>
... the tweeter might have that would warrant deleting the rt but I don't think codifying them beyond "violates the rust coc" is sensible, if someone had a concern then probably asking the resources team in the first instance and the core team in the second instance is the way to go on a case by case basis
<re_irc>
< (@adamgreig:matrix.org)> to be clear, if someone is particularly known for doing things that are obviously against the rust coc i don't think we should be rting them at all, even for tweets that are just rust-embedded related, and I can totally understand someone thinking that associating with crypto is also over that line
<re_irc>
< (@adamgreig:matrix.org)> perhaps we're lucky in that the crypto world seems to have mostly ignored embedded rust afaik?
<re_irc>
< (@adamgreig:matrix.org)> anyway, i'd welcome feedback on this on that pr thread, it probably does make sense to at least include a note about the rust coc and about contact/reporting paths for things you think need a second look
<re_irc>
< (@adamgreig:matrix.org)> ugh, I don't especially like that as-written this would basically say we're fine RTing defence cos advertising that their latest cluster bombs are safer thanks to embedded rust or whatever though, and indeed if the tweet was about specifically crypto on embedded rust we might want to do a bit more soul searching
<re_irc>
< (@dirbaio:matrix.org)> lol
<re_irc>
< (@dirbaio:matrix.org)> I don't think we should try codifying which things that should / shouldn't be retweeted
<re_irc>
< (@adamgreig:matrix.org)> we're actually in the middle of writing a short policy on what the social media accounts do, https://github.com/rust-embedded/wg/pull/651, so this might be worth capturing! personally I think that when the tweet itself is entirely on-topic it's fair enough to rt it (or choose not to if the person running the account doesn't want to, it's at their discretion), beyond that there are some other interests...
<re_irc>
... the tweeter might have that would warrant deleting the rt but I don't think codifying them beyond "violates the rust coc" is sensible, if someone had a concern then probably asking the resources team in the first instance and the core team in the second instance is the way to go on a case by case basis
<re_irc>
< (@adamgreig:matrix.org)> yea, that way lies madness, I think "at the discretion of the person running the account, who isn't obliged to rt anything and can choose not to if they don't like the vibes, but it must be embedded rust related", with "you can ask them to think again if it's bad, and you can ask the core team to think about it too" will hopefully see us through?
<re_irc>
< (@dirbaio:matrix.org)> I'd just leave to the account maintainer's' discretion
<re_irc>
< (@dirbaio:matrix.org)> after all I think we all agree the WG shouldn't tweet about hardware designed to kill people, or about crypto...
<re_irc>
< (@adamgreig:matrix.org)> indeed
<re_irc>
< (@dirbaio:matrix.org)> "not RT someone who's known for willfully/repeatedly violating the Rust CoC" sure
<re_irc>
< (@dirbaio:matrix.org)> but "not RT someone associated with crypto" (if the tweet is not about crypto itself) goes too far IMO
<re_irc>
< (@dirbaio:matrix.org)> how deep does it go? do we also not RT someone who works for a defense co? someone who has worked in the past? someone who works/worked for a co that has the DoD as customer..?
<re_irc>
< (@adamgreig:matrix.org)> yea, I don't think "not RT someone associated with crypto" would belong in the policy
<re_irc>
< (@adamgreig:matrix.org)> do we check the profiles of everyone getting RTd first? I like to hope not and anything that slips through hopefully gets noticed quickly
<re_irc>
< (@adamgreig:matrix.org)> I hope there's not that many people out there tweeting about their embedded rust projects while the rest of the profile is blatant coc violation stuff