[Libre-soc-bugs] [Bug 961] NLnet 2022 Libre-SOC "ongoing" milestone 2022-08-107 (approved, MoU TBD)

bugzilla-daemon at libre-soc.org bugzilla-daemon at libre-soc.org
Wed Aug 30 23:04:21 BST 2023


https://bugs.libre-soc.org/show_bug.cgi?id=961

--- Comment #18 from Jacob Lifshay <programmerjake at gmail.com> ---
(In reply to Luke Kenneth Casson Leighton from comment #17)
> https://libre-soc.org/task_db/report/
> 
> bug #737 shows EUR 2500 unallocated to subtasks
> bug #1035 EUR 4000 and

afaict the leftover budget is unused for both of those, so is available for
re-assigning.

> bug #1026 shows EUR 5000

the whole budget is used in bug #1026, like #1025 there are enough subtasks
that we are constrained by the budget and will have to pick and choose what to
do. the full list of tasks isn't established for #1026 yet since it'll likely
be partially leftovers from #1025 and I haven't done the subtask budget
estimation yet.

> ghostmansd needs for example to say an amount he
> is happy with to cover v3.1 SFFS 32bit ops in binutils (and
> insndb if needed), and jacob if you want to move budget from
> 1035 to 1026 you need to do a full lines/days-estimate on
> every v3.1 SFFS 32bit op, before moving budget in case it ends
> up leaving too little.

as mentioned on IRC, I already finished all non-binutils work for bug #1035 and
I'm happy with the budget. the binutils budget under #1035 is currently set to
EUR 1000 and ghostmansd seems happy with that, since the work should be pretty
easy to do. ghostmansd left the budget assignment for the rest of #1035 up to
the rest of us:
https://libre-soc.org/irclog/%23libre-soc.2023-08-30.log.html#t2023-08-30T20:38:49

> 
> but also bear in mind as i said on IRC, if there *is* spare it
> should be balanced against LD/ST-322 and Vectorised-Immediates
> also likely needing extra (particularly VI).

ok, I missed that on bug #1047 you already did most the work and the extra
budget would be needed for getting whoever works on it up-to-speed.

As mentioned on IRC, I don't think we should assign more budget to
Vectorised-Immediates since I think it should be lower priority than #1025 and
most other tasks, if we run out of budget for Vectorised-Immediates then I
think we should do what fits in the current budget and put off the rest for
another grant.

therefore, I think we should take the leftover budget from bug #737 and bug
#1035 and assign it like so:

we have EUR 6500 to distribute:
* bug #1047 gets additional EUR 1000 
  2500 for lkcl and 1500 for whoever finishes it off
  the additional money is for the learning curve and because there's not
  much left after paying lkcl.
* bug #1025 gets additional EUR 4500
  it could use a lot more than that...iirc the full task list 
  sums to well in excess of 20k, somewhere around 30k last I checked
* bug #1146 gets EUR 1000 
  assigned through bug #1037 increasing it to EUR 7000
  I think it's highly beneficial to have a decent amount of working ram
  without needing to wait on ddr3 getting figured out.
  additionally, making it work with a RPi or other SBC with a SPI interface
  is useful because they're much more widely available than HyperRAM and
  have much more ram, enough that we could run compilers and stuff.
  I estimate that EUR 1000 is just about enough to get the wishbone to
  SPI slave translator and write the simple ram emulator program which
  will use SPI through Linux's drivers.

-- 
You are receiving this mail because:
You are on the CC list for the bug.


More information about the libre-soc-bugs mailing list