News for hackers. Stuff that matters.
Re:Lisp CPU by scott_wilson46 on Tuesday June 24, 2014 @03:08PM (#7939817)
It's not going to limit clock speed, its just not going to work. To write multiple values to different ram locations (considering a ram has at most two ports) would require you to stay in the INIT state for 9 cycles and do something like:

  INIT:
    begin
    if (count == 9) begin
      next_count == 0;
      nextState = `EVALUATE;
    end
    else 
      next_count == count + 1;
    case (count)
      0: begin ram_wr_addr = count; ram_wr_data = `CMD_LED_ON; ram_wr_en = 1; end
      1: begin ram_wr_addr = count; ram_wr_data = `CMD_LOAD_NEXT_TO_ACCU; ram_wr_en = 1; end
      etc....
    end
usually you have a ram module that takes an address and some write_data, wr_en, etc rather than accessing the array directly.
Re:Lisp CPU by jff on Tuesday June 24, 2014 @06:14PM (#7940995)
I think we've come back to "original author doesn't actually know how to write logic, thinks he's writing sequential code" as the core problem