Skip to content

Instantly share code, notes, and snippets.


M:kë X:ä x724

View GitHub Profile

My current questions are specifically around some of the syntax in the systems verilog and vhdl, and just confirming some of my assumptions. As you know, I’ve downloaded a few open source projects, synthesized them on AWS, and run them on their F1 instances. I’ve read through their source code trying to gain a high level understanding of their project, and of SV and VHDL, along with things like overclocking, undervolting, temperature control, max power draw, different boards, etc.

General questions about FPGAs:

  • Compatibility between different boards, same FPGA chip
    • porting designs from one board to another.
      • c program changes
      • verilog and resynth
    • Footprint compatibility

###example response for an anal scene

  "url": "",
  "ref_id": "my-custom-ref"
x724 /
Last active May 16, 2016
"Programs must be written for people to read, and only incidentally for machines to execute."
# this part was really elegantly done, it's readable, easy to understand, commented, concise.
# it was magical but wasn't too out there, just needs a unit test and all is good.
# Get subboxes
sub_areas = self.responsearea_set.all()
sub_areas_draw = map(lambda a: a.drawables(), sub_areas)
# Flatten
View gist:33fad58be5edad64a81e
### Keybase proof
I hereby claim:
* I am xiamike on github.
* I am michaelxia ( on keybase.
* I have a public key whose fingerprint is EB9A 0171 A29F AAC2 2EA1 90DF 76E3 E933 B24B D916
To claim this, I am signing this object:
x724 /
Created Feb 24, 2014
broken file creator - for turning in those assignments that you have yet to finish ...
import sys
import os
import random
if __name__ == '__main__':
if len(sys.argv) != 3:
print "USAGE: python <FILE_NAME> <FILE_SIZE_KB>"
size = sys.argv[2]
name = sys.argv[1]