os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Add 2017Q1 Book-E/powerpc64 entry from jhibbits

Browse source
This commit is contained in:
Benjamin Kaduk 2017-04-15 19:34:15 +00:00
parent ffc8189d95
commit 0ba50c8981
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=50165
1 changed files with 50 additions and 0 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
en_US.ISO8859-1/htdocs/news/status/report-2017-01-2017-03.xml
View file

@ -194,4 +194,54 @@
emulators to ease implementation, testing, and debugging.</task>
</help>
</project>
<project cat='arch'>
<title>64-bit PowerPC Book-E support</title>
<contact>
<person>
<name>
<given>Justin</given>
<common>Hibbits</common>
</name>
<email>jhibbits@FreeBSD.org</email>
</person>
</contact>
<body>
<p>The Book-E platform target now supports 64-bit mode
(&quot;powerpc64&quot;). It includes a 63-bit address space
split, but the page table directory list uses holes to expand
to the full address space, leaving gaps in the address space
where page mappings are repeated. This may change in the
future.</p>
<p>As with the AIM powerpc64 port, this supports running powerpc
(32-bit) binaries as well, and has even been tested with a
32-bit <tt>init</tt> and 64-bit shell.</p>
<p>Several of the SoC drivers are supported, however, the dTSEC
ethernet controller is not yet supported. Work is ongoing to
support this.</p>
<p>A QORIQ64 config is included, targeting the P5 and T* series
SoCs from Freescale.</p>
<p>Thanks to Juniper Networks for providing patches against an
older internally maintained &os; version, which enabled this
porting effort, and for providing historical context for quirks
of the pmap changes.</p>
</body>
<help>
<task>Port the dTSEC driver to 64-bit. There are assumptions in the
reference driver of operating in a 32-bit environment. It may
be easier to port the Linux driver instead, which would also
give ARM support.</task>
<task>Take advantage of pointer alignment to squeeze more bits
out of the page tables; it should be possible to squeeze at
least 3 more bits out, one at each level.</task>
</help>
</project>
</report>