nlnet_2019_coriolis2/questions.mdwn

   1 # Questions
   2
   3 Dear Jean-Paul and Luke,
   4
   5 you applied to the 2019-10 open call from NLnet. We have some questions
   6 regarding your project The Libre-RISCV SoC, Coriolis2 ASIC Layout
   7 Collaboration.
   8
   9 Can you provide a breakdown of the amount requested? We understand there
  10 are a number of different tasks you will undertake, but we need to
  11 understand the cost composition of the proposal.
  12
  13 Are Coriolis2 python bindings ready for the upcoming switch to Python3,
  14 as python2 availability is decreasing? The same actually holds for Qt4,
  15 do you plan to upgrade this - or would you be open to others doing that?
  16
  17 nmigen is a tool produced by others, how will this work? Will additional
  18 cost be needed to upstream this effort? Would it not make more sense for
  19 that project to be funded directly?
  20
  21 # Answer (1)
  22
  23 > you applied to the 2019-10 open call from NLnet. We have some questions
  24 > regarding your project The Libre-RISCV SoC, Coriolis2 ASIC Layout
  25 > Collaboration.
  26 >
  27 > Can you provide a breakdown of the amount requested? We understand there
  28 > are a number of different tasks you will undertake, but we need to
  29 > understand the cost composition of the proposal.
  30
  31   I will let that point to Luke...
  32
  33 > Are Coriolis2 python bindings ready for the upcoming switch to Python3,
  34 > as python2 availability is decreasing? The same actually holds for Qt4,
  35 > do you plan to upgrade this - or would you be open to others doing that?
  36
  37   * For Qt 5, the port is already done and working. It was needed to
  38     build for Debian 9 / Ubuntu 18.04 LTS.
  39
  40   * For Python 3, the move has not been done (yet), but I sure feel a
  41     rising pressure to do it.
  42
  43     Long answer is that my "reference build system" is Scientific Linux 7
  44     (a free clone of RHEL 7) which allows me to both run my tool and the
  45     commercial ones as well (Cadence/Mentor/Synospys) and keep me close to
  46     the OSes used in the industry. And this system still uses Python 2.7
  47     as it's primary (RedHat makes very stable systems, but the downside
  48     is that they uses old versions of tools). So, of course I'm aware
  49     that I will need to switch to Python 3 at some point, but it doesn't
  50     feel urgent.
  51       I'm perfectly happy with other people doing the port, I'm just not
  52     very proud about the way the Python bindings are done. As I want to
  53     perform very specific operations, I did develop a bunch of C macros
  54     to do the job. They work well and do exactly what I want and there is
  55     even a tutorial on how to use them, but they are a bit clumsy and
  56     not that easy to understand.
  57       Portability across systems is a dependency nightmare, so I try
  58     to keep to most commonly shared ones.
  59
  60 > nmigen is a tool produced by others, how will this work? Will additional
  61 > cost be needed to upstream this effort? Would it not make more sense for
  62 > that project to be funded directly?
  63
  64   To muddle the point even more (this is an info I wanted to pass on
  65   Luke), we are also investigating on nmigen in the LIP6, with the same
  66   goal of interfacing with Coriolis.
  67