[Open-graphics] Documenting Hardware Design Process
John Griessen
john at foseda.com
Wed Nov 28 12:44:35 EST 2007
There's this:
http://research.cs.berkeley.edu/project/slipway/
http://www.megacz.com/research/megacz-fccm07.pdf
He uses icarus, then some code of his to do finer than possible with Atmel tools
FPGA P&R. Could be a starting point for open tools...but uses odd devel tools, (darcs Haskell).
He claims to have a project in the works for a more mainstream FPGA, but won't say yet.
John Griessen
Attila Kinali wrote:
i was astonished that people accept
> that level of quality of software and support.
>
> It is really time that we replace those comercial packages
> with something OSS... then we can at least fix the bugs
> ourselves.
----------------------
>> What can the really expensive tools do that Icarus can't?
>
> They can actually synthesize our HDL code. There is currently no
> OSS solution for either FPGA or ASIC synthesis.
>
> Attila Kinali
----------------------
> With some attention, we could probably get Icarus to synthesize to a
> target architecture or at least to an intermediate netlist that we can
> map. (We could write our own Verilog parser, but let's see if we can
> avoid reinventing the wheel.)
>
> As for P&R, I had been conversing from someone who has posted to
> gEDA-dev about this. He had some kind of background knowledge about
> P&R tools, and with my AI (read: search and optimization) background,
> I figure we can do this. We just need to get people involved.
More information about the Open-graphics
mailing list