<re_irc>
<@thebutlah:matrix.org> I'm trying to use usbd-serial to implement the log::Logger trait on a USB serial connection. The SerialPort object does not implement core::fmt::Write, and instead it has a flushable port that can have bytes written/read from. The confusing part however is that separately according to the examples from the library, you are supposed to create a USB device via usb-device and poll that device, passing the...
<re_irc>
... SerialPort as one of the objects to dispatch the polled events to.
<re_irc>
<@thebutlah:matrix.org> I find that API a bit confusing since it means that if I pass a SerialPort object to some other struct (for example my logger implementation), when it writes to the SerialPort, nothing is actually written until the usb device has `device.poll(&[my_serial])` invoked. I'm not sure what exactly is supposed to own the SerialPort object and the USB device - is it the Logger, some polling loop of my main...
<re_irc>
... function, or something else? Furthermore if the USB device needs to be polled in as often as possible, this implies that I can't have things like delays in the rest of the application because it will delay the polling mechanism as well.
<re_irc>
<@thebutlah:matrix.org> Any insight on the decisions behind why the poll operation is separate, how to avoid delays/polling blocking timers and other things, and who should own the serial logger?
starblue has quit [Ping timeout: 240 seconds]
starblue has joined #rust-embedded
<re_irc>
<@dngrs:matrix.org> jamesmunns:beeper.com: ah so I was mainly wondering how to reference/handle those things, not the actual storage; for now that is handled rather crudely by `cortex_m::singleton!` which I guess is ok for the time being but may get revisited for polishing - usually I struggle to turn these POCs I build into crates or modules which you could "plug in" to RTIC for example (I guess the problem is because you have a...
<re_irc>
... few different topics like interrupt handling, resources, locking, yadda yadda)
<re_irc>
<@dngrs:matrix.org> anyway, got temporal LED DMA dithering to work and it's *pretty nice*! Needs a bit of sanding around the edges but the visual quality is definitely there
<re_irc>
<@dngrs:matrix.org> still not sure 100% how to best unify the light energy and perception models of internal LED pwm vs temporal dithering PWM vs gamma correction
<re_irc>
<@dngrs:matrix.org> maybe I will actually need to measure the photon output somehow for a given RGB input
<re_irc>
<@dngrs:matrix.org> also lol tired brain word salad, I should go to bed
<re_irc>
<@luojia65:matrix.org> Wu Wei: At the end of 2022, I don't know if I can get a RISC-V notebook based on Xiangshan. (Thinking about it makes me happy)
<re_irc>
<@adamgreig:matrix.org> one spare pogo pin is brave lol
<re_irc>
<@adamgreig:matrix.org> clever to use upside down pogo pins for the locating studs, and the 0.1" pin headers both to hold the two PCBs together and as a second set of SWD pins for jumper wires
<re_irc>
<@thejpster:matrix.org> Can I get bors to stop emailing me?
<re_irc>
<@adamgreig:matrix.org> that's because it was delivered to you through the rust-embedded.org mailing list, which isn't itself allowed to send from github.com
<re_irc>
<@adamgreig:matrix.org> but it's an email from github
<re_irc>
<@thejpster:matrix.org> Yes but is our remailer at teams.rust-embedded.org ok?
<re_irc>
<@thejpster:matrix.org> I'd expect to get these a lot, or not at all
<re_irc>
<@thejpster:matrix.org> Not randomly
<re_irc>
<@adamgreig:matrix.org> have you checked your spam? I find they mostly go to spam
<re_irc>
<@adamgreig:matrix.org> and I seem to get them for every bors commit to staging/merge to master on cortex-m repo, rather than randomly
<re_irc>
<@adamgreig:matrix.org> (but I don't know why they started recently)
<re_irc>
<@thejpster:matrix.org> I have few but not as many as you might expect
<re_irc>
<@thejpster:matrix.org> Ok, I'll filter them out for now
<re_irc>
<@adamgreig:matrix.org> I'd love to know what causes them, heh. afaik github doesn't know about that email address via the github org team, so dunno where it's getting it from exactly
<re_irc>
<@adamgreig:matrix.org> oh, it was set up repo settings -> notifications for all push events
<re_irc>
<@adamgreig:matrix.org> I've disabled that now
hifi has quit [Remote host closed the connection]
hifi has joined #rust-embedded
hwj has joined #rust-embedded
hwj has quit [Client Quit]
edm has quit [Quit: Updating details, brb]
edm has joined #rust-embedded
radens has quit [Quit: Connection closed for inactivity]