Andrew Zonenberg
Andrew Zonenberg
That was the first thing I did. It printed out a bunch of XML blobs from the SAML authentication, then nothing. No indication of why it was waiting.
Somewhere on the github.io page maybe?
Refactoring: Rename gp4par to "gpkpar" to reflect planned support for other GreenPAK device families
This applies to gp4prog as well
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...
Good idea but the phrasing is a bit awkward. Maybe something like "verify DDRx DQ/DM signals are assigned to correct DQS"? That doesn't sound quite right either, think about it.
FYI... I'm seeing crashes related to thread safety with this as well. ``` ==2537019==ERROR: AddressSanitizer: heap-use-after-free on address 0x61200000f340 at pc 0x7faadf55d7e1 bp 0x7faa9092a8a0 sp 0x7faa9092a050 READ of size 2...
1. When did I do that? I generally try to keep import and modify separate. 2. Ooh, good call I should look into that. 3. Yeah I should probably add...
I don't have any interrupts that touch the crypto engine at all, the only concern would be if I had preemptive multitasking and you could swap in a separate thread...
1) Not possible. Once the descriptor is bound in a command buffer, you're not allowed to modify or destroy it until the command buffer finishes execution. Avoiding this limitation is...
My nodes are doing custom draw commands in them so perhaps that's related, the sentinel is not being found in the expected state? ``` (gdb) frame 1 p#1 0x0000555555c4a548 in...