0:33 AM
errordeveloper joined the channel
0:37 AM
errordeveloper has quit
1:00 AM
errordeveloper joined the channel
1:04 AM
errordeveloper has quit
2:20 AM
errordeveloper joined the channel
2:24 AM
errordeveloper has quit
2:38 AM
c74d3 joined the channel
2:39 AM
c74d3 is now known as
3:02 AM
c74d3 joined the channel
3:03 AM
c74d3 is now known as
4:09 AM
errordeveloper joined the channel
4:13 AM
errordeveloper has quit
4:31 AM
c74d joined the channel
5:10 AM
errordeveloper joined the channel
5:14 AM
errordeveloper has quit
6:11 AM
errordeveloper joined the channel
6:15 AM
errordeveloper has quit
6:50 AM
c0170 joined the channel
7:51 AM
errordeveloper joined the channel
12:02 PM
errordeveloper has quit
13:07 PM
c0170 has quit
13:44 PM
errordeveloper joined the channel
14:33 PM
Lurkin joined the channel
14:34 PM
Lurkin
Hey farcaller, I just got my first firmware to work.
14:34 PM
errordeveloper has quit
14:37 PM
I mean driver.
15:28 PM
farcaller
\o/
15:28 PM
grats!
15:30 PM
Lurkin
Are you going to keep going on zinc?
15:30 PM
I know it's failing now but it's almost 1.0 time.
15:32 PM
farcaller
I made rustup today. rustup made me sad :)
15:32 PM
at least my non-baremetal code is mostly functional
15:34 PM
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
15:38 PM
Lurkin
And you were searching for a way to quickly add devices right?
15:38 PM
Autogenerate code basically?
15:39 PM
farcaller
well, that part is working
15:39 PM
I guess, it's the only part that is working
15:39 PM
there's an svd parser to ioreg code
15:39 PM
and ioreg macro that gives a "safe" api to that
15:40 PM
Lurkin
I *still* don't know what svd is or does, I had to write the registers and options by hand for the 9685.
15:42 PM
In fact if I google "svd parser" zinc is the first result
15:43 PM
Ok found your example svd file
15:45 PM
15:45 PM
Is there a way to take that file and turn it into that svd format?
15:46 PM
That along with the manual for the chip is how I got my driver to work.
15:46 PM
farcaller
well, if you're into lots of manual work
15:46 PM
but at that point writing ioreg definition directly makes much more sense
15:47 PM
Lurkin
I didn't think it was hard, maybe tedious, is this not what you need though?
15:48 PM
I seriously thought it was a lot of fun.
15:48 PM
farcaller
if you don't have svd there is no reason to write it, svd parser only saves you time to generate ioreg
15:49 PM
Lurkin
Sweet, I'm one step ahead of the game, basically you point and I'll write drivers.
15:51 PM
farcaller
ioreg macro is broken now thanks to new parser interfaces
15:53 PM
Lurkin
Which of your test boards do you prefer?
15:54 PM
farcaller
lpc1768 at the moment
15:54 PM
although I hooked up a bare lpc1114 to test machine to see if I can do e2e tests
15:56 PM
Lurkin
If I get the ARM chip workign on the RPI2 would you consider switching platforms?
15:57 PM
The shittiest thing about that board is the video drivers
15:57 PM
Otherwise I'll order an lpc1768
15:58 PM
farcaller
well, rpi2 is cortex-a
15:58 PM
it's not that much interesting, too powerful
16:00 PM
Lurkin
I'm just thinking that a lot of peripherals are built with that board in mind, there's almost an overabundance of documentation.
16:00 PM
But I will agree with you and order one of these boards.
16:01 PM
I am easy enough to work with.
16:01 PM
farcaller
there's little reason to not use linux on rpi2 I think
16:02 PM
Lurkin
Future wise I think hypervisiors and unikernels will end up taking over.
16:03 PM
No worries though I ordered the other chip.
16:06 PM
errordeveloper joined the channel
22:18 PM
errordeveloper has quit
22:26 PM
errordeveloper joined the channel
22:39 PM
errordeveloper has quit
22:41 PM
errordeveloper joined the channel
23:21 PM
errordeveloper joined the channel