hdl.github.io/awesome/items/poc

Self-explanatory :p

hdl.github.io/awesome/items/openocd

hdl.github.io/awesome/items/symbiyosys

hdl.github.io/awesome/items/xyce

Hi @eine

Here, the provided example about cocotb:

---
title: "Coroutine Co-simulation Test Bench (cocotb)"
description: "A coroutine based cosimulation library for writing VHDL and Verilog testbenches in Python"
author: ["author"]
links:
  gh: "https://github.com/cocotb/cocotb"
  docs: "https://cocotb.rtfd.io"
tags: [
  "verification",
  "vhdl",
  "verilog",
  "systemverilog",
]
categories: [
  "Frameworks"
]
---

*"cocotb is a coroutine based cosimulation library for writing VHDL and Verilog testbenches in Python."*

<!--more-->

- Licence: [Revised BSD License](https://github.com/cocotb/cocotb/blob/master/LICENSE)
- Implemented in: Python
- Write Testbeches In: Python

• I think that License must be in the mandatory part.
• Something related to the longevity and status of the project? First and last year of existence?
• Statics such as Starts, forks, and so could be useful for repositories.

We can create some helpers to check periodically, with a cron, status info and generate an alarm. Maybe ranges could be useful (thinking about info such as starts and forks).

hdl.github.io/awesome/items/mistral

hdl.github.io/awesome/items/uhdm

https://hdl.github.io/awesome/items/superprove

hdl.github.io/awesome/items/nvc

hdl.github.io/awesome/items/migen

hdl.github.io/awesome/items/wavedrom

hdl.github.io/awesome/items/netlistsvg

hdl.github.io/awesome/items/ghdl

hdl.github.io/awesome/items/surelog

hdl.github.io/awesome/items/osvvm

hdl.github.io/awesome/items/iverilog

hdl.github.io/awesome/items/icestorm

hdl.github.io/awesome/items/vpr

hdl.github.io/awesome/items/tsfpga

hdl.github.io/awesome/items/litex

hdl.github.io/awesome/items/chisel

hdl.github.io/awesome/items/prjoxide

hdl.github.io/awesome/items/pyvhdlparser

hdl.github.io/awesome/items/graphviz

hdl.github.io/awesome/items/openroad

hdl.github.io/awesome/items/openfpgaloader

Goes to https://github.com/hdl/swesome/actions?query=workflow%3Asite

https://hdl.github.io/awesome/items/fritzing

hdl.github.io/awesome/items/gtkwave

hdl.github.io/awesome/items/yosys

hdl.github.io/awesome/items/magic

hdl.github.io/awesome/items/ghdl-yosys-plugin

hdl.github.io/awesome/items/verilator

hdl.github.io/awesome/items/prjxray

hdl.github.io/awesome/items/fasm

hdl.github.io/awesome/items/nextpnr

Hi @eine. I was checking the categories and they seem ok from a high abstraction level. I mean, they catch almost any possibility in the first part of the category. Maybe we will need to add more sub-categories (the second and third parts). Some comments/ideas:

  categories:
    "Libraries": ""
    "Libraries:IP Core Libraries": "libraries containing multiple IP cores"
    "Libraries:IP Core Collections": "collections containing multiple IP cores"
    "IP Cores": "single IP cores"

Maybe the last one could be changed by "Libraries:Single IP Core" (I know, it is not exactly a library). Or instead, all could be changed to:

"IP Core:Single"
"IP Core:Library"
"IP Core:Collection"

    "Frameworks": ""
    "Frameworks:Verification": "frameworks for verification"
    "Verification": ""
    "Verification:Models": "single verification models"
    "Verification:Models:Memory": "verification model for Memories"
    "Verification:Models:Interface": "verification model for Interfaces"

Maybe, the last four could be included in "Frameworks:Verification" Or instead to have a "Verification:Framework" category.

    "Tools": ""
    "Tools:Grammars": ""
    "Tools:Parsers": ""
    "Tools:Simulators": ""
    "Tools:Package Managers": ""
    "Tools:Waveform Viewer": ""
    "Tools:Verification": ""

What about synthesizers, p&r, bitstream generators, programmers, complete workflow (thinking on something like SymbiFlow or IceStorm). Project/tools managers? (edalize, hdlmake, PyFPGA, etc). "Tools:Doc generatos", "Tools:Doc helpers" or similar?

    "Resources": ""
    "Resources:Books": ""
    "Resources:Twitter": ""
    "Resources:Websites": ""
    "Resources:Weekly": ""
    "Conferences": ""

Maybe "Resources:Conference"? Instead of "Resources:Twitter", "Resources:Social media"? Probably we will ned something like "Resources:Wiki" and more.

That is all for now, and of course, we always can add a needed category but is good to start with a good main categorization.

hdl.github.io/awesome/items/vtr

@eine how will we continue?

• gohugo theme modification.
• collecting a TODO list from the four suggested awesome lists.
• creating the entry for each project.

A doubt that I have: is only related to free and open-source projects/material? (which is what I am more interested in), or all the related with HDL in general? (must all the FPGA vendors be in the list? each board in the market? all the available conferences?).

And, of course, we need to define when is exactly considered awesome? :P

https://hdl.github.io/awesome/items/ngspice

hdl.github.io/awesome/items/klayout

hdl.github.io/awesome/items/dfu-util

hdl.github.io/awesome/items/vunit

https://hdl.github.io/awesome/items/prjuray

hdl.github.io/awesome/items/verible

https://hdl.github.io/awesome/items/kicad

hdl.github.io/awesome/items/cocotb

hdl.github.io/awesome/items/prjtrellis

hdl.github.io/awesome/items/renode