https://libre-soc.org/nlnet_2022_opf_isa_wg/
(approved 25 oct 2022. reminder: prior ISA WG work not permitted to place RFPs)

-----------------------------------------------------------------------

Schedule A

# Research for RFCs

Research and discussion is needed before an RFC to add new instructions
to the Power ISA is needed. Sometimes an instruction, if added, is just
not used enough to make it worthwhile. Others might be so specific that
they have very limited use-cases. Thus research is required to provide
justification for every instruction proposed.

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

Budget: 19000

-------------------------------------------------

# Writeup and first submission of RFCs

Each Draft ISA RFC requires an intial draft. This task's sub-tasks are
completed at the point that the first Draft RFC is submitted as an
External OPF ISA RFC at https://openpower.foundation/isarfc/
(formal proposal or detailed RFC as appropriate)

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

Budget: 33000

-------------------------------------------------

# Iterative OPF ISA WG questions, feedback, and re-submission

Each Draft ISA RFC, once submitted, has to be reviewed for consideration
by the OpenPOWER ISA Working Group.  This process, for which RED
Semiconductor Ltd specifically joined the OPF ISA WG (and is under
Commercial Confidentiality), itself has multiple stages, including
review by several teams internally within IBM (the primary user of
the Power ISA). RED Semiconductor Ltd will take responsibility for
collating the questions and ensuring that permission
is granted by the ISA WG to publish the questions with neither an
NDA nor Commercial Confidentiality being violated, working as a
Member of the ISA WG to ensure that no Confidential Information provided
by OPF Members becomes public.  This is complex!

Also involved here may be documenting of modifications to SVP64 and/or
the Simulator(s) - the python-based ISACaller and the (new) cavatools
2021-08-071 Grant, bug #939.  The documentation of modifications is
part of this Milestone: the implementation of changes is not (that
should be covered by Grant 2022 08 107, bug #961).

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

Budget: 23000

-------------------------------------------------

# Report on final status (accept / reject) of RFC(s)

A public report needs to be generated on the status of each RFC,
or a set of RFCs,
whether accepted, rejected, and what the next steps need to be,
if any.

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

Budget: 3000

-------------------------------------------------

# Development of an SVP64 "cookbook"

Every ISA has recipes demonstrating how to optimally achieve certain
goals. Best practices for an entirely new ISA needs a "jump-start"
on what is now normally created by bloggers, academic papers, and
questions on stackexchange and other such forums.  This milestone
therefore covers some example recipes such as sorting algorithms,
DCT, FFT, and other extremely useful algorithms, explained in
a conversational or "whitepaper" style.

URL: 10000

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

-------------------------------------------------

# Online-only Conferences, whitepapers, presentations

It is very important to increase awareness of the work being done on
the Power ISA. Writing good presentations, whitepapers is different
from the "cookbook" recipes which more target developers, and give an
overview and background from a different perspective.

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

Budget: 9000

-------------------------------------------------

# binutils updates from OPF RFC feedback

As changes are made to the RFCs due to feedback, there are corresponding
changes needed to binutils to match the requested changes.

Budget: EUR 3,000

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

-------------------------------------------------