<azonenberg>
it's intended for embedded, not apps processing
<azonenberg>
the GPU is meant to run a HMI or something
<azonenberg>
not a desktop
<azonenberg>
and you can get the chip with and without the gpu (prob just fused but w/e)
<cyrozap>
azonenberg: I guess it's ok for embedded. I'm more interested in AP SoCs that can be used for desktop/laptop stuff, i.e., all the shiny new aarch64 chips coming out.
<azonenberg>
yeah
<azonenberg>
if i do anything arm in the near future
<azonenberg>
i think it'll likely be a zynq
<azonenberg>
as that fits my use case better
<rqou>
I have a tegra x1 dev board, but I never got around to the "unf*ck the shitty distribution" step
<rqou>
nvidia ships it with a reasonably-up-to-date Ubuntu userspace with an ancient kernel
<rqou>
but depending on the version of Linux4Tegra either it's not an aarch64 userspace or something else is wrong with the GPU drivers
<rqou>
also, supposedly tegra x1 works with an upstream kernel now, so I don't know why nvidia still has their ancient version
scrts has quit [Ping timeout: 268 seconds]
scrts has joined ##openfpga
doomlord has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<openfpga-github>
[openfpga] azonenberg pushed 1 new commit to master: https://git.io/vXLHm
<openfpga-github>
openfpga/master e5e3107 Andrew Zonenberg: gpdevboard: Replaced stupid file locking with a much cleaner version that just detects LIBUSB_ERROR_BUSY
<openfpga-github>
[openfpga] azonenberg opened issue #56: gp4prog --lock times out after releasing the lock and leaves blue LED stuck on https://git.io/vXLH3
<azonenberg>
incidentally, this new lock is cleaner as it only locks one board at a time (using the usb device internally via libusb)
<azonenberg>
So it allows two people to concurrently use different boards without conflicting
<azonenberg>
however a build typically depends on all boards so it may block in that situation
scrts has quit [Ping timeout: 252 seconds]
<openfpga-github>
[openfpga] azonenberg pushed 1 new commit to master: https://git.io/vXLHo
<openfpga-github>
openfpga/master 90f731d Andrew Zonenberg: tests: Massive restructuring of directories. All non-HiL tests now run during build instead of during test.
<openfpga-github>
[openfpga] azonenberg pushed 1 new commit to master: https://git.io/vXLHx
<openfpga-github>
openfpga/master 086810c Andrew Zonenberg: tests: Added placeholder comments to build scripts
<openfpga-github>
[openfpga] azonenberg pushed 1 new commit to master: https://git.io/vXLQ9
<openfpga-github>
openfpga/master de9f7fe Andrew Zonenberg: tests: Refactored test naming so that we can disambiguate use of the same test case name for different devices
<openfpga-github>
[openfpga] azonenberg opened issue #57: Better documentation for libgpdevboard so it can be used by third-party code https://git.io/vXL7U
<openfpga-github>
[openfpga] azonenberg commented on issue #57: This seems like something that would be nice for end users to rig up their own unit testing apparatus. We should probably tidy up the headers and comment more thoroughly... https://git.io/vXL7T
<azonenberg>
whitequark: re twitter handle
<azonenberg>
nickname*
<azonenberg>
given how much mercury is in some tuna these day
<azonenberg>
days*
<azonenberg>
some of them might fail rohs :p
<openfpga-github>
[openfpga] azonenberg pushed 1 new commit to master: https://git.io/vXL7u
<openfpga-github>
openfpga/master 91551ad Andrew Zonenberg: tests: Added Bargraph as a HiL test
<whitequark>
tl;dr it cannot fail rohs by definition as rohs only applies to electronics
<whitequark>
re travis: yes absolutely :D
<whitequark>
azonenberg: kinda unhappy about 90f731d
Bike has quit [Quit: drain (collector)]
scrts has quit [Ping timeout: 260 seconds]
scrts has joined ##openfpga
scrts has quit [Ping timeout: 250 seconds]
scrts has joined ##openfpga
doomlord has joined ##openfpga
Bike has joined ##openfpga
scrts has quit [Ping timeout: 260 seconds]
scrts has joined ##openfpga
doomlord has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
<azonenberg>
whitequark: sec
<azonenberg>
whitequark: so there is a specific reason for that
<azonenberg>
in the longer term i wanted to be able to have "shared" tests
<azonenberg>
where i build one source file for multiple devices
<azonenberg>
and then the stuff in the test directory is target specific
<azonenberg>
We can discuss if you have strong feelings on why you think this is a bad idea, though
doomlord has joined ##openfpga
doomlord has quit [Quit: My MacBook Pro has gone to sleep. ZZZzzz…]
digshadow has quit [Quit: Leaving.]
doomlord has joined ##openfpga
digshadow has joined ##openfpga
digshadow has quit [Client Quit]
digshadow has joined ##openfpga
nonlinear has joined ##openfpga
<rqou>
azonenberg: when you were trying to create a systemwide mutex, why couldn't you just use "presence/absence of a file in /tmp"? why would you need flock?
digshadow has quit [Ping timeout: 265 seconds]
maaku has quit [Ping timeout: 260 seconds]
maaku has joined ##openfpga
maaku has quit [Ping timeout: 260 seconds]
maaku has joined ##openfpga
<azonenberg>
rqou: because if a process terminates unexpectedly (segfault etc)
<azonenberg>
it wont clean up the file
<azonenberg>
i needed something managed by the OS
<rqou>
ah ok
digshadow has joined ##openfpga
<azonenberg>
rqou: and for a CI server
<azonenberg>
it's kinda expected that processes will segfault here and there :p