Tuesday, 2022-03-15

*** tpb <[email protected]> has joined #f4pga00:00
F4PGASlackBridge<kenneth.wilke> lkcl: Thanks for sharing, I appreciate hearing that personal perspective.  My experience is mostly based on being a self taught Linux practitioner and software engineer, with attempts to branch out into hardware here and there. I had several attempts to learn HDL but the tooling was usually pretty overwhelming. I did finally start to gain some ground when I was playing with FPGAs and CAPI while working on the00:08
F4PGASlackBridgeOpenPOWER Barreleye servers at Rackspace and could ask my random noob questions to folks from IBM and Xilinx. Overall though I think it's safe to say I have barely a clue what I'm doing when it comes to hardware, but I'm stubborn enough to keep trying anyway!00:08
F4PGASlackBridge<kenneth.wilke> The wild west side of HDL certainly appeals to me though, with FPGAs having the appeal of running my janky designs in a much more ephemeral way. Though I would consider taking a crack at open source ASIC designs if my skills reach the point where that's a practical enough choice00:17
*** SiddhRamanPant[m <SiddhRamanPant[m!~siddhpant@2001:470:69fc:105::1:d8cb> has quit IRC (Ping timeout: 240 seconds)00:37
*** SiddhRamanPant[m <SiddhRamanPant[m!~siddhpant@2001:470:69fc:105::1:d8cb> has joined #f4pga00:53
*** bl0x <bl0x!~bastii@p200300d7a70d7f00fb2130b0eb28bf7d.dip0.t-ipconnect.de> has quit IRC (Ping timeout: 240 seconds)02:34
*** bl0x <bl0x!~bastii@p200300d7a71be500209d1f45c6cb21d9.dip0.t-ipconnect.de> has joined #f4pga02:36
F4PGASlackBridge<as85> @kenneth.wilke On top of that, wouldn't the cost of fabrication for ASIC designs be astronomical, even for low volume solutions? From what I understand (which is not very much) it seems like there are few options for getting ICs made, and even with older processes the costs seem to discourage smaller groups from experimenting.04:10
F4PGASlackBridge<kenneth.wilke> @as85 I share that same view, the only way it seems like it would be feasible for most small groups would be if your design makes it into the Multi-Project Wafer thing that Google  sponsors: https://efabless.com/open_shuttle_program/04:47
tpbTitle: Open Source Shuttle MPW-5 | Efabless (at efabless.com)04:47
*** cr1901_ <cr1901_!~cr1901@2601:8d:8600:911:88b7:e735:e17c:e37f> has joined #f4pga07:56
*** cr1901 <cr1901!~cr1901@2601:8d:8600:911:4c40:72d2:6947:5aae> has quit IRC (Ping timeout: 240 seconds)07:56
*** indy <[email protected]> has quit IRC (Ping timeout: 240 seconds)09:05
lkclkenneth: yes i'm a software engineer as well, who tinkered with 74 logic gates and also did A-Level maths when younger09:14
lkcli couldn't "grok" HDL at all until i started consistently, persistently, and religiously looking at yosys "show top" diagrams after each and every single modification to the HDL09:15
lkclfor six months straight (!)09:15
lkcllike this: https://libre-soc.org/3d_gpu/priority_picker_16_yosys.png09:16
lkclis the output from this: https://git.libre-soc.org/?p=nmutil.git;a=blob;f=src/nmutil/picker.py;h=0babc074a9eeb9663793bcc4fd1bfdb259d631bc;hb=7a3ab7ecce390b2003ff61befca59cd4ad6b7428#l3209:17
tpbTitle: git.libre-soc.org Git - nmutil.git/blob - src/nmutil/picker.py (at git.libre-soc.org)09:17
lkclthe other thing: i very deliberately picked nmigen (which is Trademarked btw - and still an Open Source Project, like how Mozilla trademarks Firefox) *precisely* because i'm trained as a Software Engineer09:19
lkclas85: sky130 google-sponsored designs, up to 10mm^2, are entirely free.  no charge.  no money. zip. nada.09:20
lkclcaveat: your entire design *must* be Open Source Licensed.09:20
lkclefabless ChipIgnite is only USD 8.5k09:21
lkclif you're thinking "holy crap that's expensive", you'd be dead wrong.  any other MPW - if you can even get access to one these days - is 5 to 10x that price09:22
lkcleFabless negotiated the price down by taking responsibility for many of the tasks normally covered (laboriously, manually) by the Foundry, and (surpriise) automating them, by applying intelligent Software Engineering / IT practices09:23
lkclalso, again, if you have an entirely Libre/Open VLSI design and use coriolis2, there is a Foundry in Japan that is i think 2 micron (200 nm, close to the usual 180nm) in a small town09:24
lkclthat is used for "training" of its employees. i can make an indirect introduction (point you in the right direction) and you won't have to pay for that, at all, either09:25
lkclsorry, 2 micron is 2,000 nm.  BIG :)10:03
lkcli need to check on that10:03
*** indy <[email protected]> has joined #f4pga11:15
*** cr1901_ is now known as cr190114:05
F4PGASlackBridge<as85> @ikcl I have no issues with open sourcing designs (I would do it anyway) but from my understanding the skywater program by Google requires your project to be selected, that is, there is no guarantee that your design will be made. Is the foundry in japan similar, or will they fabricate most reasonable designs?15:41
*** lopsided98 <[email protected]> has joined #f4pga16:31
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga18:04
F4PGASlackBridge<kenneth.wilke> @as85 I think I view this similarly as well. I'd prefer my designs to be open source to share with other tinkerers and maybe get useful feedback from more experienced engineers. I think you're correct that there is no guarantee of acceptance. Admittedly that does affect my willingness to spend personal time exploring that path but I still see it as a pretty awesome and generous opportunity. I really enjoy the18:14
F4PGASlackBridgeidea of aspirational CompSci students or other tinkerers having that chance, but for now I'm focused on areas that I feel more confident could yield (pun intended) results for the kinds of projects I work on18:14
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Quit: ec)18:33
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga19:07
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Client Quit)19:10
mithrohttps://dl.acm.org/doi/abs/10.1145/3519599 - An Optimized GIB Routing Architecture with Bent Wires for FPGA -- The experimental results show that the GIB architecture with length-4 wires can achieve 9.5% improvement on the critical path delay and 11.1% improvement on the area-delay product compared to the VTR CB-SB architecture with length-4 wires. After exploring mixed wire types, the optimized GIB architecture can further improve the 19:52
mithrodelay by 16.4% and area-delay product by 17.1% compared to the CB-SB architecture with length-4 wires.19:52
tpbTitle: An Optimized GIB Routing Architecture with Bent Wires for FPGA | ACM Transactions on Reconfigurable Technology and Systems (at dl.acm.org)19:52
nimheveryone seen this? https://pygears.org/19:53
mithroThere website is all new and fancy!19:59
*** ec <ec!~ec@gateway/tor-sasl/ec> has joined #f4pga20:19
*** ec <ec!~ec@gateway/tor-sasl/ec> has quit IRC (Ping timeout: 240 seconds)22:47

Generated by irclog2html.py 2.17.2 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!