<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd"> <html> <head> <title></title> <link rel="stylesheet" media="screen" type="text/css" href="./style.css" /> <link rel="stylesheet" media="screen" type="text/css" href="./design.css" /> <link rel="stylesheet" media="print" type="text/css" href="./print.css" /> <meta http-equiv="Content-Type" content="text/html; charset=utf-8" /> </head> <body> <h3 class="sectionedit2273"><a name="gtkwave_projects" id="gtkwave_projects">GTKWave projects</a></h3> <div class="level3"> <ul> <li class="level1"><div class="li"> System Verilog and/or VHDL support for RTLBrowse. Currently it's only plain-vanilla verilog from the 1995 <acronym title="specification">spec</acronym>.</div> </li> </ul> <ul> <li class="level1"><div class="li"> More “interesting” integrations with other tools. The new Tcl interface adds a bunch of possibilities. I know one guy is using it to allow remote control from emacs through a bridge server.</div> </li> </ul> <ul> <li class="level1"><div class="li"> Improved analog support. This would also mean being able to read various spice rawfiles, etc.</div> </li> </ul> <ul> <li class="level1"><div class="li"> An open source equivalent to FSDB in terms of speed, file size, and capabilities of the different types of data it can store. This wouldn't necessarily be a gtkwave-only project given that I'd expect a reader/writer <acronym title="Application Programming Interface">API</acronym> that for example, icarus/ghdl and gtkwave can interface to. This is the most challenging of the bunch and would require not only coding, but lots of experimentation + throwing away code + restarting over when it's realized a better way can be used to do something.</div> </li> </ul> </div> </body> </html>
distrib
>
Mageia
>
5
>
x86_64
>
media
>
core-release
>
by-pkgid
>
f2f28f61487f3042d93877451f0a311f
>
files
>
280
