78/a41a0fd5f242813ffec9fb4eaea0a209d75b4b

   1 Return-path: <libre-riscv-dev-bounces@lists.libre-riscv.org>
   2 Envelope-to: publicinbox@libre-riscv.org
   3 Delivery-date: Tue, 31 Mar 2020 15:11:51 +0100
   4 Received: from localhost ([::1] helo=libre-riscv.org)
   5         by libre-riscv.org with esmtp (Exim 4.89)
   6         (envelope-from <libre-riscv-dev-bounces@lists.libre-riscv.org>)
   7         id 1jJHcL-0007AV-Rb; Tue, 31 Mar 2020 15:11:49 +0100
   8 Received: from isis.lip6.fr ([132.227.60.2])
   9  by libre-riscv.org with esmtps (TLS1.2:ECDHE_RSA_AES_256_GCM_SHA384:256)
  10  (Exim 4.89) (envelope-from <Jean-Paul.Chaput@lip6.fr>)
  11  id 1jJHcJ-0007AP-Up
  12  for libre-riscv-dev@lists.libre-riscv.org; Tue, 31 Mar 2020 15:11:47 +0100
  13 Received: from asim.lip6.fr (asim.lip6.fr [132.227.86.2])
  14  by isis.lip6.fr (8.15.2/8.15.2) with ESMTPS id 02VEBkNm008538
  15  (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
  16  Tue, 31 Mar 2020 16:11:46 +0200 (CEST)
  17 Received: from localhost (melon [132.227.103.13])
  18  by asim.lip6.fr (8.15.2/8.14.4) with ESMTP id 02VEBkqJ021742;
  19  Tue, 31 Mar 2020 16:11:46 +0200 (MEST)
  20 Message-ID: <e01a01fb87d745f34fa4b8e71445fb1777f308c6.camel@lip6.fr>
  21 From: Jean-Paul Chaput <Jean-Paul.Chaput@lip6.fr>
  22 To: "lkcl ." <luke.leighton@gmail.com>, Libre-RISCV General Development
  23  <libre-riscv-dev@lists.libre-riscv.org>, Marie-Minerve
  24  =?ISO-8859-1?Q?Lou=EBrat?= <Marie-Minerve.Louerat@lip6.fr>
  25 Date: Tue, 31 Mar 2020 16:11:35 +0200
  26 In-Reply-To: <CAPweEDx=aGvp8KbhdipG5Lt=Uo9p7L2miEmP88FcAPFvQnnryw@mail.gmail.com>
  27 References: <CAPweEDw_h8VQ3JJFF3FXph7Eg0ucVknuvMk=Xc0jSp0WP13=UQ@mail.gmail.com>
  28  <8fb9dbcc812d3d7050c6e336dc9bf68f88536888.camel@gmail.com>
  29  <de619dbb67b22514be18f4a8e4282d90de502cf6.camel@lip6.fr>
  30  <CAPweEDyJKoUdHeDrQTHLWj7S42T=FDwj6bsnvCPoFHaf7bGy-Q@mail.gmail.com>
  31  <752371e7a9de77d78305af838989817bfec4fda8.camel@lip6.fr>
  32  <CAPweEDzGM3KEeMQWh5_wvePa4bHJvDZJExdLCVjmaMije5Jzrg@mail.gmail.com>
  33  <CAPweEDwz3n_jMS2NFFU=FJe4m82QqvG9XU2e9N474s7ZKj-VcA@mail.gmail.com>
  34  <CAPweEDzxhDpfv8hH5nJnJn=RCMdVkk5RZAndxvo1z1jd2AQw5Q@mail.gmail.com>
  35  <CAPweEDx=aGvp8KbhdipG5Lt=Uo9p7L2miEmP88FcAPFvQnnryw@mail.gmail.com>
  36 Organization: UPMC
  37 X-Mailer: Evolution 3.28.5 (3.28.5-5.el7)
  38 Mime-Version: 1.0
  39 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.4.3
  40  (isis.lip6.fr [132.227.60.2]); Tue, 31 Mar 2020 16:11:46 +0200 (CEST)
  41 X-Scanned-By: MIMEDefang 2.78 on 132.227.60.2
  42 X-Content-Filtered-By: Mailman/MimeDel 2.1.23
  43 Subject: Re: [libre-riscv-dev] pyobjc, gnu objective-c and gnustep
  44 X-BeenThere: libre-riscv-dev@lists.libre-riscv.org
  45 X-Mailman-Version: 2.1.23
  46 Precedence: list
  47 List-Id: Libre-RISCV General Development
  48  <libre-riscv-dev.lists.libre-riscv.org>
  49 List-Unsubscribe: <http://lists.libre-riscv.org/mailman/options/libre-riscv-dev>,
  50  <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=unsubscribe>
  51 List-Archive: <http://lists.libre-riscv.org/pipermail/libre-riscv-dev/>
  52 List-Post: <mailto:libre-riscv-dev@lists.libre-riscv.org>
  53 List-Help: <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=help>
  54 List-Subscribe: <http://lists.libre-riscv.org/mailman/listinfo/libre-riscv-dev>,
  55  <mailto:libre-riscv-dev-request@lists.libre-riscv.org?subject=subscribe>
  56 Reply-To: Libre-RISCV General Development
  57  <libre-riscv-dev@lists.libre-riscv.org>
  58 Content-Type: multipart/mixed; boundary="===============9156565726221374067=="
  59 Errors-To: libre-riscv-dev-bounces@lists.libre-riscv.org
  60 Sender: "libre-riscv-dev" <libre-riscv-dev-bounces@lists.libre-riscv.org>
  61
  62
  63 --===============9156565726221374067==
  64 Content-Type: multipart/signed; micalg="pgp-sha1"; protocol="application/pgp-signature";
  65         boundary="=-1xMN/UKcAW4fqZhcLB9V"
  66
  67
  68 --=-1xMN/UKcAW4fqZhcLB9V
  69 Content-Type: text/plain; charset="UTF-8"
  70 Content-Transfer-Encoding: quoted-printable
  71
  72
  73 On Tue, 2020-03-31 at 11:42 +0000, lkcl . wrote:
  74 > *click* what the hell am i saying??  jean-paul, we've got a clear need
  75 > for improvements to coriolis2, it is *really* easy to justify putting
  76 > in an application for NLNet funding, here.
  77
  78 Hello Luke,
  79
  80 This is a complicated matter. As a team of one, I have limited resources,
  81 so I must prioritize (and I know myself, I'm not very good at that).
  82 Anyway, the short term goal is to have the 180nm circuit done and
  83 working by October. In order to do that I/we must not "finish"
  84 Coriolis, but put it to a point it can fulfil that objective.
  85 I'm convinced it is doable, but we should go straight to the point,
  86 because I'm sure that lots of unexpected issues will pop-up and
  87 I will have to tackle them quickly.
  88
  89 My "development cycle" are alternate steps of "adding features" then
  90 "improve code at constant features".
  91
  92 So, having more hands will really be a plus (as you already proposed in
  93 an early mail). The problem is to have someone(s) with that triple skills
  94 (ASIC, algorithmic, software) and it has been proven difficult on my
  95 end. To have an example of the kind of code I get, you could take a
  96 look to the whole capacitor stuff in coriolis/oroshi/python/
  97 (and you will easily see where I modified the code with my unique
  98  coding style). This was made by a good electrical engineer, but
  99 with embryonic software knowledge. The code is to draw the layout
 100 of one or a matrix of analog capacitors. The comments are made for
 101 doxygen.
 102
 103 And besides, all of our students have already chosen their internship
 104 (in the industry). I think we may have a good one in June.
 105 And lastly, due to the Covid-19 and University shutdown we cannot
 106 hire anybody, should we have a candidate.
 107
 108 I absolutely do not want to give you the impression that I do not
 109 want more people working on Coriolis, quite the contrary.
 110 But I want to expose the context as rightfully as it is.
 111 The question being how to circumvent those initial conditions
 112 to get more efficient people working on Coriolis?
 113
 114 I've taken a look at GNUstep, it seems a bit quite by there...
 115 (maybe I was on the wrong site). For the record, WidowMaker is
 116 one of the more memory efficient window manager I have ever seen
 117 (still can work on my UltraSparc 1 / NetBSD).
 118
 119 However I will remove Boost as soon as possible, it has proven to
 120 be a pebble in my shoes for too long. And migrating towards Python3.
 121
 122 I'm currently making my Python code a bit more PEP8 compliant then
 123 backporting some of the work of Jock in soclayout. *But* I will keep
 124 some style that you may find bad. Paradox is that the "comma" at the
 125 start of line was showed to me by an early Python adopter back around
 126 2000...
 127
 128
 129 Best regards,
 130 --=20
 131
 132       .-.     J e a n - P a u l   C h a p u t  /  Administrateur Systeme
 133       /v\     Jean-Paul.Chaput@lip6.fr
 134     /(___)\   work: (33) 01.44.27.53.99             =20
 135      ^^ ^^    cell:      06.66.25.35.55   home: 09.65.29.83.38
 136
 137     U P M C   Universite Pierre & Marie Curie
 138     L I P 6   Laboratoire d'Informatique de Paris VI
 139     S o C     System On Chip
 140
 141 --=-1xMN/UKcAW4fqZhcLB9V--
 142
 143
 144
 145 --===============9156565726221374067==
 146 Content-Type: text/plain; charset="utf-8"
 147 MIME-Version: 1.0
 148 Content-Transfer-Encoding: base64
 149 Content-Disposition: inline
 150
 151 X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KbGlicmUtcmlz
 152 Y3YtZGV2IG1haWxpbmcgbGlzdApsaWJyZS1yaXNjdi1kZXZAbGlzdHMubGlicmUtcmlzY3Yub3Jn
 153 Cmh0dHA6Ly9saXN0cy5saWJyZS1yaXNjdi5vcmcvbWFpbG1hbi9saXN0aW5mby9saWJyZS1yaXNj
 154 di1kZXYK
 155
 156 --===============9156565726221374067==--
 157
 158
 159