On 29 November 2010 17:29, Stephen Wille Padnos wrote:
> Of course, we don't have the right to distribute that software anyway,
> so it's a moot point.
That was why I was suggesting doing it the way I described, but it
seems to be impractical.
--
atp
"Torque wrenches are for the obedience of f
Jonathan George wrote:
> Perhaps a live CD that could do the same?
This would have to be a live DVD, since the FPGA software from Xilinx is
several GB in size.
Of course, we don't have the right to distribute that software anyway,
so it's a moot point. The Xilinx software also requires registra
Perhaps a live CD that could do the same?
On Sun, Nov 28, 2010 at 2:57 PM, Andy Pugh wrote:
> On 28 November 2010 21:17, Jeff Epler wrote:
>
> > The wall time to build one firmware is up to 15 CPU minutes
> > (3x20-1/SV24.BIT) and uses upwards of 300MB RAM.
>
> It was looking like a good idea up
On 28 November 2010 21:17, Jeff Epler wrote:
> The wall time to build one firmware is up to 15 CPU minutes
> (3x20-1/SV24.BIT) and uses upwards of 300MB RAM.
It was looking like a good idea up to then. I am guessing The Cloud is
not the answer either.
--
atp
--
In principle it's quite easy. Your web page just has to build a PIN.vhd
file like this one
http://git.linuxcnc.org/gitweb?p=hostmot2-firmware.git;a=blob;f=PIN_SV12_72.vhd;hb=HEAD
list it in the firmwares.txt file as the only entry, invoke make, and
wait for the result.
However
The wall time
I suddenly had this wacky idea:
How automate-able is the Mesa firmware production process?
Would it be possible to create a web form that allowed you to specify
how many of each module you wanted and a few other options (like 7i39
pinout), then have the web server compile a bitfile and email you
