#zinc

/

      • errordeveloper joined the channel
      • errordeveloper has quit
      • errordeveloper joined the channel
      • errordeveloper has quit
      • errordeveloper joined the channel
      • errordeveloper has quit
      • c74d3 joined the channel
      • c74d3 is now known as
      • c74d3 joined the channel
      • c74d3 is now known as
      • errordeveloper joined the channel
      • errordeveloper has quit
      • c74d joined the channel
      • errordeveloper joined the channel
      • errordeveloper has quit
      • errordeveloper joined the channel
      • errordeveloper has quit
      • c0170 joined the channel
      • errordeveloper joined the channel
      • errordeveloper has quit
      • c0170 has quit
      • errordeveloper joined the channel
      • Lurkin joined the channel
      • Lurkin
        Hey farcaller, I just got my first firmware to work.
      • errordeveloper has quit
      • I mean driver.
      • farcaller
        \o/
      • grats!
      • Lurkin
        Are you going to keep going on zinc?
      • I know it's failing now but it's almost 1.0 time.
      • farcaller
        I made rustup today. rustup made me sad :)
      • at least my non-baremetal code is mostly functional
      • I got the functional test environment (got a new linux box recently), so yes, I'll be going on, but the focus will be to get minimally viable code that is covered by tests
      • Lurkin
        And you were searching for a way to quickly add devices right?
      • Autogenerate code basically?
      • farcaller
        well, that part is working
      • I guess, it's the only part that is working
      • there's an svd parser to ioreg code
      • and ioreg macro that gives a "safe" api to that
      • Lurkin
        I *still* don't know what svd is or does, I had to write the registers and options by hand for the 9685.
      • In fact if I google "svd parser" zinc is the first result
      • Ok found your example svd file
      • Is there a way to take that file and turn it into that svd format?
      • That along with the manual for the chip is how I got my driver to work.
      • farcaller
        well, if you're into lots of manual work
      • but at that point writing ioreg definition directly makes much more sense
      • Lurkin
        I didn't think it was hard, maybe tedious, is this not what you need though?
      • I seriously thought it was a lot of fun.
      • farcaller
        if you don't have svd there is no reason to write it, svd parser only saves you time to generate ioreg
      • Lurkin
        Sweet, I'm one step ahead of the game, basically you point and I'll write drivers.
      • farcaller
        ioreg macro is broken now thanks to new parser interfaces
      • Lurkin
        Which of your test boards do you prefer?
      • farcaller
        lpc1768 at the moment
      • although I hooked up a bare lpc1114 to test machine to see if I can do e2e tests
      • Lurkin
        If I get the ARM chip workign on the RPI2 would you consider switching platforms?
      • The shittiest thing about that board is the video drivers
      • Otherwise I'll order an lpc1768
      • farcaller
        well, rpi2 is cortex-a
      • it's not that much interesting, too powerful
      • Lurkin
        I'm just thinking that a lot of peripherals are built with that board in mind, there's almost an overabundance of documentation.
      • But I will agree with you and order one of these boards.
      • I am easy enough to work with.
      • farcaller
        there's little reason to not use linux on rpi2 I think
      • Lurkin
        Future wise I think hypervisiors and unikernels will end up taking over.
      • No worries though I ordered the other chip.
      • errordeveloper joined the channel
      • errordeveloper has quit
      • errordeveloper joined the channel
      • errordeveloper has quit
      • errordeveloper joined the channel
      • errordeveloper joined the channel