| Variable | Value |
|---|
Edit count of the user (user_editcount) | 97 |
Name of the user account (user_name) | 'Flow' |
Age of the user account (user_age) | 387253031 |
Page ID (page_id) | 242944 |
Page namespace (page_namespace) | 510 |
Page title (without namespace) (page_title) | 'RISC-V' |
Full page title (page_prefixedtitle) | 'Project:RISC-V' |
Action (action) | 'edit' |
Edit summary/reason (summary) | '' |
Old content model (old_content_model) | 'wikitext' |
New content model (new_content_model) | 'wikitext' |
Old page wikitext, before the edit (old_wikitext) | '{{Project
|Name=RISC-V Development
|Description=Gentoo RISC-V architecture support project.
|Email=riscv@gentoo.org
|Bug assignment=No
|Packages=No
|IRC=#gentoo-riscv
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|Members={{Project Member
|Developer=User:Dilfridge
|Role=Release engineering
|IsLead=No
}}{{Project Member
|Developer=User:Gokturk
|IsLead=No
}}{{Project Member
|Developer=User:Dlan
|IsLead=No
}}{{Project Member
|Developer=User:Alexxy
|IsLead=No
}}{{Project Member
|Developer=User:Nerdboy
|IsLead=No
}}{{Project Member
|Developer=User:Marecki
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|Role=can do keywording
|IsLead=No
}}{{Project Member
|Developer=User:Jsmolic
|IsLead=No
}}{{Project Member
|Developer=User:Xen0n
|IsLead=No
}}{{Project Member
|Developer=User:Maffblaster
|Role=VisionFive 2
|IsLead=No
}}
}}
[[Article description::The RISC-V project is an effort to bring first-class [[wikipedia:RISC-V|RISC-V]] CPU architecture support in Gentoo.]]
== Status ==
[https://www.gentoo.org/downloads/ Riscv64 stages are available via the normal Gentoo download page], and a set of packages in the Gentoo repository is keyworded. At the moment we have the following stages:
* riscv64gc / lp64d, openrc
* riscv64gc / lp64d, systemd
* riscv64imac / lp64, openrc
* riscv64imac / lp64, systemd
'''qemu-riscv''' can run riscv64 binaries just fine. This way one can also test in an emulated chroot.
=== What needs to be done ===
Things to happen yet:
* Get riscv32 running somehow (fails due to bugs in qemu user mode emulation)
* '''Bonus''': provide a bootable image to make setup easier (flash to SD card directly rather than needing to do a normal Gentoo install with install media; arm would benefit from this too).
== Keywording policy ==
* '''ARCH=riscv''' is the assigned keyword.
* No stable '''riscv''' keywords are planned for the moment.
* For packages without obvious hardware aspect, qemu-user or qemu-system testing is sufficient for keywording '''~riscv'''
* Packages with hardware aspect (bootloader, drivers, ...) have to be tested on real hardware.
* Multilib packages should get tested for both lp64d and lp64 ABI, for others lp64d is sufficient
* When we get to stabilizations in the future, that will require testing on real hardware.
== Documentation ==
* TODO: Describe arch-specific gotchas (alignment requirements, immediate encodings, PIC story).
* [[RISC-V ABIs]]
* [[RISC-V Multilib]]
* [[RISC-V Qemu setup]]
* [[Embedded systems/RISC-V hardware list|RISC-V hardware list]]
== Links ==
* [https://bugs.gentoo.org/buglist.cgi?component=Keywording&email2=riscv%40gentoo.org&emailcc2=1&emailtype2=substring&list_id=6015663&product=Gentoo%20Linux&query_format=advanced&resolution=--- outstanding riscv keyword requests]' |
New page wikitext, after the edit (new_wikitext) | '{{Project
|Name=RISC-V Development
|Description=Gentoo RISC-V architecture support project.
|Email=riscv@gentoo.org
|Bug assignment=No
|Packages=No
|IRC=#gentoo-riscv
|ParentProject=Project:Gentoo
|PropagatesMembers=No
|Members={{Project Member
|Developer=User:Dilfridge
|Role=Release engineering
|IsLead=No
}}{{Project Member
|Developer=User:Gokturk
|IsLead=No
}}{{Project Member
|Developer=User:Dlan
|IsLead=No
}}{{Project Member
|Developer=User:Alexxy
|IsLead=No
}}{{Project Member
|Developer=User:Nerdboy
|IsLead=No
}}{{Project Member
|Developer=User:Marecki
|IsLead=No
}}{{Project Member
|Developer=User:GYakovlev
|Role=can do keywording
|IsLead=No
}}{{Project Member
|Developer=User:Jsmolic
|IsLead=No
}}{{Project Member
|Developer=User:Xen0n
|IsLead=No
}}{{Project Member
|Developer=User:Maffblaster
|Role=VisionFive 2
|IsLead=No
}}{{Project Member
|Developer=User:Flow
|IsLead=No
}}
}}
[[Article description::The RISC-V project is an effort to bring first-class [[wikipedia:RISC-V|RISC-V]] CPU architecture support in Gentoo.]]
== Status ==
[https://www.gentoo.org/downloads/ Riscv64 stages are available via the normal Gentoo download page], and a set of packages in the Gentoo repository is keyworded. At the moment we have the following stages:
* riscv64gc / lp64d, openrc
* riscv64gc / lp64d, systemd
* riscv64imac / lp64, openrc
* riscv64imac / lp64, systemd
'''qemu-riscv''' can run riscv64 binaries just fine. This way one can also test in an emulated chroot.
=== What needs to be done ===
Things to happen yet:
* Get riscv32 running somehow (fails due to bugs in qemu user mode emulation)
* '''Bonus''': provide a bootable image to make setup easier (flash to SD card directly rather than needing to do a normal Gentoo install with install media; arm would benefit from this too).
== Keywording policy ==
* '''ARCH=riscv''' is the assigned keyword.
* No stable '''riscv''' keywords are planned for the moment.
* For packages without obvious hardware aspect, qemu-user or qemu-system testing is sufficient for keywording '''~riscv'''
* Packages with hardware aspect (bootloader, drivers, ...) have to be tested on real hardware.
* Multilib packages should get tested for both lp64d and lp64 ABI, for others lp64d is sufficient
* When we get to stabilizations in the future, that will require testing on real hardware.
== Documentation ==
* TODO: Describe arch-specific gotchas (alignment requirements, immediate encodings, PIC story).
* [[RISC-V ABIs]]
* [[RISC-V Multilib]]
* [[RISC-V Qemu setup]]
* [[Embedded systems/RISC-V hardware list|RISC-V hardware list]]
== Links ==
* [https://bugs.gentoo.org/buglist.cgi?component=Keywording&email2=riscv%40gentoo.org&emailcc2=1&emailtype2=substring&list_id=6015663&product=Gentoo%20Linux&query_format=advanced&resolution=--- outstanding riscv keyword requests]' |
Unified diff of changes made by edit (edit_diff) | '@@ -40,4 +40,7 @@
|Developer=User:Maffblaster
|Role=VisionFive 2
+|IsLead=No
+}}{{Project Member
+|Developer=User:Flow
|IsLead=No
}}
' |
Old page size (old_size) | 2783 |
Lines added in edit (added_lines) | [
0 => '|IsLead=No',
1 => '}}{{Project Member',
2 => '|Developer=User:Flow'
] |
Lines removed in edit (removed_lines) | [] |
New page text, stripped of any markup (new_text) | '
RISC-V Development
Description
Gentoo RISC-V architecture support project.
Project email
riscv@gentoo.org
IRC channel
#gentoo-riscv (webchat)
Lead(s)
none No lead election date set
Member(s)
Alexey Shvetsov
(alexxy)Andreas K. Hüttel
(dilfridge)Release engineeringYixun Lan
(dlan)Georgy Yakovlev
(gyakovlev)can do keywordingGöktürk Yüksek
(gokturk)Jakov Smolić
(jsmolic)Marek Szuba
(Marecki)Steve Arnold
(nerdboy)Matthew Marchese
(maffblaster)VisionFive 2WANG Xuerui
(xen0n)
Subproject(s)(and inherited member(s))
(none)
Parent Project
Gentoo
Project listing
The RISC-V project is an effort to bring first-class RISC-V CPU architecture support in Gentoo.
Contents
1 Status
1.1 What needs to be done
2 Keywording policy
3 Documentation
4 Links
Status[edit | edit source]
Riscv64 stages are available via the normal Gentoo download page, and a set of packages in the Gentoo repository is keyworded. At the moment we have the following stages:
riscv64gc / lp64d, openrc
riscv64gc / lp64d, systemd
riscv64imac / lp64, openrc
riscv64imac / lp64, systemd
qemu-riscv can run riscv64 binaries just fine. This way one can also test in an emulated chroot.
What needs to be done[edit | edit source]
Things to happen yet:
Get riscv32 running somehow (fails due to bugs in qemu user mode emulation)
Bonus: provide a bootable image to make setup easier (flash to SD card directly rather than needing to do a normal Gentoo install with install media; arm would benefit from this too).
Keywording policy[edit | edit source]
ARCH=riscv is the assigned keyword.
No stable riscv keywords are planned for the moment.
For packages without obvious hardware aspect, qemu-user or qemu-system testing is sufficient for keywording ~riscv
Packages with hardware aspect (bootloader, drivers, ...) have to be tested on real hardware.
Multilib packages should get tested for both lp64d and lp64 ABI, for others lp64d is sufficient
When we get to stabilizations in the future, that will require testing on real hardware.
Documentation[edit | edit source]
TODO: Describe arch-specific gotchas (alignment requirements, immediate encodings, PIC story).
RISC-V ABIs
RISC-V Multilib
RISC-V Qemu setup
RISC-V hardware list
Links[edit | edit source]
outstanding riscv keyword requests' |
Parsed HTML source of the new revision (new_html) | '<div class="mw-parser-output"><table class="table table-condensed" style="width: 30em; font-size: 95%; border: 1px solid #ddd; background-color: #f9f9f9; color: black; margin-bottom: 0.5em; margin-left: 1em; padding: 0.2em; float: right; clear: right; text-align:left;">
<tbody><tr>
<th style="text-align: center; background-color:#3E355A; color: white;" colspan="2"><big>RISC-V Development</big>
</th></tr>
<tr valign="top">
<th>Description
</th>
<td style="text-align: justify;">Gentoo RISC-V architecture support project.
</td></tr>
<tr>
<th><span title="Mails to member(s) listed below.">Project email</span>
</th>
<td><a rel="nofollow" class="external text" href="mailto:riscv@gentoo.org">riscv@gentoo.org</a>
</td></tr>
<tr>
<th><span title="The link opens an IRC client to libera.chat IRC channel.">IRC channel</span>
</th>
<td><span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="ircs://irc.libera.chat/#gentoo-riscv">#gentoo-riscv</a></span> (<span style="font-family: monospace; font-size: 95%;"><a rel="nofollow" class="external text" href="https://web.libera.chat/#gentoo-riscv">webchat</a></span>)
</td></tr>
<tr valign="top">
<th>Lead(s)
</th>
<td>none <br />No lead election date set
</td></tr>
<tr valign="top">
<th>Member(s)
</th>
<td><ul><li><a href="/wiki/User:Alexxy" title="User:Alexxy">Alexey Shvetsov</a>
(alexxy)</li><li><a href="/wiki/User:Dilfridge" title="User:Dilfridge">Andreas K. Hüttel</a>
(dilfridge)<br /><i>Release engineering</i></li><li><a href="/wiki/User:Dlan" title="User:Dlan">Yixun Lan</a>
(dlan)</li><li><a href="/wiki/User:GYakovlev" title="User:GYakovlev">Georgy Yakovlev</a>
(gyakovlev)<br /><i>can do keywording</i></li><li><a href="/wiki/User:Gokturk" title="User:Gokturk">Göktürk Yüksek</a>
(gokturk)</li><li><a href="/wiki/User:Jsmolic" title="User:Jsmolic">Jakov Smolić</a>
(jsmolic)</li><li><a href="/wiki/User:Marecki" title="User:Marecki">Marek Szuba</a>
(Marecki)</li><li><a href="/wiki/User:Nerdboy" title="User:Nerdboy">Steve Arnold</a>
(nerdboy)</li><li><a href="/wiki/User:Maffblaster" title="User:Maffblaster">Matthew Marchese</a>
(maffblaster)<br /><i>VisionFive 2</i></li><li><a href="/wiki/User:Xen0n" title="User:Xen0n">WANG Xuerui</a>
(xen0n)</li></ul>
</td></tr>
<tr valign="top">
<th>Subproject(s)<br /><small style="font-weight: normal;">(and inherited member(s))</small>
</th>
<td>(none)
</td></tr>
<tr>
<th>Parent Project
</th>
<td><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Gentoo</a>
</td></tr>
<tr>
<td colspan="2" style="border-top: 1px solid #ddd; font-size: smaller; text-align: center;"><a href="/wiki/Project:Gentoo" title="Project:Gentoo">Project listing</a>
</td></tr></tbody></table>
<p>The RISC-V project is an effort to bring first-class <a href="https://en.wikipedia.org/wiki/RISC-V" class="extiw" title="wikipedia:RISC-V">RISC-V</a> CPU architecture support in Gentoo.
</p>
<div id="toc" class="toc" role="navigation" aria-labelledby="mw-toc-heading"><input type="checkbox" role="button" id="toctogglecheckbox" class="toctogglecheckbox" style="display:none" /><div class="toctitle" lang="en" dir="ltr"><h2 id="mw-toc-heading">Contents</h2><span class="toctogglespan"><label class="toctogglelabel" for="toctogglecheckbox"></label></span></div>
<ul>
<li class="toclevel-1 tocsection-1"><a href="#Status"><span class="tocnumber">1</span> <span class="toctext">Status</span></a>
<ul>
<li class="toclevel-2 tocsection-2"><a href="#What_needs_to_be_done"><span class="tocnumber">1.1</span> <span class="toctext">What needs to be done</span></a></li>
</ul>
</li>
<li class="toclevel-1 tocsection-3"><a href="#Keywording_policy"><span class="tocnumber">2</span> <span class="toctext">Keywording policy</span></a></li>
<li class="toclevel-1 tocsection-4"><a href="#Documentation"><span class="tocnumber">3</span> <span class="toctext">Documentation</span></a></li>
<li class="toclevel-1 tocsection-5"><a href="#Links"><span class="tocnumber">4</span> <span class="toctext">Links</span></a></li>
</ul>
</div>
<h2><span class="mw-headline" id="Status">Status</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:RISC-V&veaction=edit&section=1" class="mw-editsection-visualeditor" title="Edit section: Status">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:RISC-V&action=edit&section=1" title="Edit section: Status">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<p><a rel="nofollow" class="external text" href="https://www.gentoo.org/downloads/">Riscv64 stages are available via the normal Gentoo download page</a>, and a set of packages in the Gentoo repository is keyworded. At the moment we have the following stages:
</p>
<ul><li>riscv64gc / lp64d, openrc</li>
<li>riscv64gc / lp64d, systemd</li>
<li>riscv64imac / lp64, openrc</li>
<li>riscv64imac / lp64, systemd</li></ul>
<p><b>qemu-riscv</b> can run riscv64 binaries just fine. This way one can also test in an emulated chroot.
</p>
<h3><span class="mw-headline" id="What_needs_to_be_done">What needs to be done</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:RISC-V&veaction=edit&section=2" class="mw-editsection-visualeditor" title="Edit section: What needs to be done">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:RISC-V&action=edit&section=2" title="Edit section: What needs to be done">edit source</a><span class="mw-editsection-bracket">]</span></span></h3>
<p>Things to happen yet:
</p>
<ul><li>Get riscv32 running somehow (fails due to bugs in qemu user mode emulation)</li>
<li><b>Bonus</b>: provide a bootable image to make setup easier (flash to SD card directly rather than needing to do a normal Gentoo install with install media; arm would benefit from this too).</li></ul>
<h2><span class="mw-headline" id="Keywording_policy">Keywording policy</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:RISC-V&veaction=edit&section=3" class="mw-editsection-visualeditor" title="Edit section: Keywording policy">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:RISC-V&action=edit&section=3" title="Edit section: Keywording policy">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li><b>ARCH=riscv</b> is the assigned keyword.</li>
<li>No stable <b>riscv</b> keywords are planned for the moment.</li>
<li>For packages without obvious hardware aspect, qemu-user or qemu-system testing is sufficient for keywording <b>~riscv</b></li>
<li>Packages with hardware aspect (bootloader, drivers, ...) have to be tested on real hardware.</li>
<li>Multilib packages should get tested for both lp64d and lp64 ABI, for others lp64d is sufficient</li>
<li>When we get to stabilizations in the future, that will require testing on real hardware.</li></ul>
<h2><span class="mw-headline" id="Documentation">Documentation</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:RISC-V&veaction=edit&section=4" class="mw-editsection-visualeditor" title="Edit section: Documentation">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:RISC-V&action=edit&section=4" title="Edit section: Documentation">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li>TODO: Describe arch-specific gotchas (alignment requirements, immediate encodings, PIC story).</li>
<li><a href="/wiki/RISC-V_ABIs" title="RISC-V ABIs">RISC-V ABIs</a></li>
<li><a href="/wiki/RISC-V_Multilib" title="RISC-V Multilib">RISC-V Multilib</a></li>
<li><a href="/wiki/RISC-V_Qemu_setup" title="RISC-V Qemu setup">RISC-V Qemu setup</a></li>
<li><a href="/wiki/Embedded_systems/RISC-V_hardware_list" title="Embedded systems/RISC-V hardware list">RISC-V hardware list</a></li></ul>
<h2><span class="mw-headline" id="Links">Links</span><span class="mw-editsection"><span class="mw-editsection-bracket">[</span><a href="/index.php?title=Project:RISC-V&veaction=edit&section=5" class="mw-editsection-visualeditor" title="Edit section: Links">edit</a><span class="mw-editsection-divider"> | </span><a href="/index.php?title=Project:RISC-V&action=edit&section=5" title="Edit section: Links">edit source</a><span class="mw-editsection-bracket">]</span></span></h2>
<ul><li><a rel="nofollow" class="external text" href="https://bugs.gentoo.org/buglist.cgi?component=Keywording&email2=riscv%40gentoo.org&emailcc2=1&emailtype2=substring&list_id=6015663&product=Gentoo%20Linux&query_format=advanced&resolution=---">outstanding riscv keyword requests</a></li></ul>
' |
Unix timestamp of change (timestamp) | 1708273066 |
Wiki