vrinsd

9 ms·

61.
by vrinsd 3y ago
Sadly (as much of a cynic as this makes me seem) I kinda figured this is exactly what would happen when the Pine people decided to partner/use MediaTek or name any other vendor who doesn't truly embrace or care about open-source.
62.
by vrinsd 3y ago
Jumping on the bandwagon of this is a pretty ridiculous "article". If the advice is "learn how things work before using some kind of automation" that's valid guidance but this article seems to assume using an IDE or
63.
by vrinsd 3y ago
Really cool to see this I hope you're able to continue this work. As others have said, CalDAV / CardDAV are complex standards and getting the nuances right without using some tried/true libraries (sabre-dav) might be a chall
64.
by vrinsd 3y ago
I think this is a good thing in the long-run. Relying on WiFi access points to geolocation was always a bit of a hack and in my experience it's allowed phone manufacturers to roll back on the quality of their satellite-based GPS implem
65.
by vrinsd 3y ago
This might be a US-centric experience so I'm prefacing... Basic cost of living is : rent, food, utilities. Those three have gone up astronomically, especially in the past 3-years. A graduate stipend is probably $22K/year, maybe m
66.
by vrinsd 3y ago
LLVM/GCC target fixed ISA devices. Even GPUs can be represented in this paradigm of having a core set of instructions and registers for SIMD/SMT. What FPGA or random ASIC could LLVM front-end? How do you go from LLVM-IR to some
67.
by vrinsd 3y ago
Your example about Bjarne says it all -- it was financially more in his interest to leave academia / standards comittee / "hardcore work" for something more financially lucarative. There's maybe another bigger point
68.
by vrinsd 3y ago
I won't get into a debate about semantics, but even your employer is a prime example -- Xilinx profit margin per device is staggering by semiconductor standards but they won't pay what they could. The market doesn't always m
69.
by vrinsd 3y ago
So many insightful comments, I don't know this adds much but "basic cost of living" or "living reasonably" has gone up fairly exponentially in the last 10-15 years. Most people in academia, if they were on the fenc
70.
by vrinsd 3y ago
That's because in order to turn your "design" into an ASIC or an FPGA, you need to go from whatever high-level language (insert new-HDL-du-jour) into a netlist compatible with your physical part. The only scalable/vendor
71.
by vrinsd 3y ago
This is a pretty heavy handed statement -- there are plenty of "hardware engineers" who know plenty about compiler theory and/or have contributed significantly to it. A similarly flippant comment might be "if software e
72.
by vrinsd 3y ago
This "announcement" is basically a no-op. It's very likely not a new device but taking something like an Artix and just re-branding it and then limiting access to device features via software(Vivado). The same was done for
73.
by vrinsd 3y ago
It has little to do with 'ROI' and much more with the way hardware gets made. Touchpad, touch screens and input devices are actually VERY difficult to get all the details right because you're dealing with material properties,
74.
by vrinsd 3y ago
Hey Jeff, Can you share what your experience has been like with Nim on embedded targets? Both Nim and Zig are on my wishlist to try out for embedded but I'm doing C and RTOSes for the next few projects. Ada with Ravenscar seems like a
75.
by vrinsd 3y ago
The GoboLinux guys really did "intelligently" come up with a filesystem layout that's humanly understandable. I personally find the old-school UNIX conventions we use fairly arcane given we no longer have 8.3 type limits imp
76.
by vrinsd 3y ago
This is great to hear. It might be nice to bubble those examples up to your Github page along with some diagrams and logic/resource results after synthesis (i.e. how many LUTs, BRAM, etc). It's easy for people to do a lot of nays
77.
by vrinsd 3y ago
Tim Westcott is a great author and this is a solid article. I'll add, I've been meaning to write up my own "realities of PID", one day I'll get around to it. What is NOT readily apparent when you look all these trea
78.
by vrinsd 3y ago
I'm always interested in new hardware-oriented DSLs, so great to see effort and work here. rachitnigam, do you have any example designs of "significant" complexity? I looked over the paper and saw your 2x2 array example -- I
79.
by vrinsd 3y ago
Background: Have worked at a large number of big-tech hardware / software companies in senior roles. My observation is that doing a 'good job' is not really measurable the way most companies think about it (it actually is if
80.
by vrinsd 3y ago
No, Irongate was very much internally developed by AMD. AMD was well aware of the "sketchy" nature of ALI/VLI/ULI/SiS and knew it was giving them a really bad rep so they undertook their own designs. AMD chipsets w
81.
by vrinsd 3y ago
1 point by vrinsd 14 minutes ago | root | parent | next | edit | delete [–] I won't be as snide as bsder, but I will say Expedition and Allegro let you handle some crazy complex designs, which are much more of a challenge with Altium.
82.
by vrinsd 3y ago
Which is weird because modern Zuken tools look really intelligent designed. I haven't tried them since they ran on Sun workstations but CR-8000 looks impressive.
83.
by vrinsd 3y ago
The step backwards you see Altium regarding not being able to freely export/import is the result of a nut job named Henry Potts, who also formerly ruled Mentor with an iron fist. He did not bring about positive change, quite the oppos
84.
by vrinsd 3y ago
Cadence bought OrCAD and kept the schematic editor but the layout is Allegro, not the layout tool that historically was part of OrCAD. Allegro IMO does have a pretty steep learning curve, I think it's UI is quite archaic, it really has
85.
by vrinsd 3y ago
The PCI chipsets of this time were really really buggy, that's why. They got better as time went on but it really took a number of years before people could get reasonably high-performance, reliable PCI implementations. For x86, aside
86.
by vrinsd 3y ago
The issue is not lack of raw bandwidth, it's getting the hardware, software, drivers and OS "to do the right thing". PCIe gives you the building blocks of posted transactions and non-posted transactions but doesn't help
87.
by vrinsd 3y ago
Intel also had quite a few issues (as usual) getting their own PCI standard working. Almost all of the early Intel PCI chipsets (i.e. Mercury, Neptune ) had serious bugs. Intel actually used DEC PCI chipsets or licensed their designs to ac
88.
by vrinsd 3y ago
I agree with every comment robomartin has posted on this thread. I'll add: I HAVE worked on schematic designs with 10-20 people working on an overall schematic design at the same time. Usually one or more engineers own some sub-sectio
89.
by vrinsd 3y ago
Glad you're open to feedback. I don't know if your regulator response was directed at me or someone else, but using that as an example, if you take something like an LM7805/LM317 I think the 'parameterization' you&#
90.
by vrinsd 3y ago
At the risk of sounding pretty negative to someone who wants to make the world of EDA better, this really seems like a re-discovery of a text netlist with the idea of making it 'easier' to create schematics but I feel like it&#x27

More ›