OpenHarmony/third_party_mesa3d
2
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: xml -> XML

Browse Source 
Reviewed-by: Yonggang Luo <luoyonggang@gmail.com>
Part-of: <https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/19297>
This commit is contained in:
Erik Faye-Lund
2022-10-25 12:08:35 +02:00
committed by Marge Bot
parent d9a04acdba
commit cf0b5a60f4
2 changed files with 4 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/ci/bare-metal.rst
View File

@@ -28,7 +28,7 @@ The boards need to be able to have a kernel/initramfs supplied by the
gitlab-runner system, since Mesa often needs to update the kernel either for new
DRM functionality, or to fix kernel bugs.
The boards must have networking, so that we can extract the dEQP .xml results to
The boards must have networking, so that we can extract the dEQP XML results to
artifacts on GitLab, and so that we can download traces (too large for an
initramfs) for trace replay testing. Given that we need networking already, and
our dEQP/Piglit/etc. payload is large, we use nfs from the x86 runner system

6
docs/drivers/freedreno/isaspec.rst
View File

@@ -1,7 +1,7 @@
ISASPEC - XML Based ISA Specification
=====================================
isaspec provides a mechanism to describe an instruction set in xml, and
isaspec provides a mechanism to describe an instruction set in XML, and
generate a disassembler and assembler. The intention is
to describe the instruction set more formally than hand-coded assembler
and disassembler, and better decouple the shader compiler from the
@@ -16,10 +16,10 @@ and verification that different encodings don't have conflicting bits
(i.e. that the specification cannot result in more than one valid
interpretation of any bit pattern).
The isaspec tool and xml schema are intended to be generic (not specific
The isaspec tool and XML schema are intended to be generic (not specific
to ir3), although there are currently a couple limitations due to short-
cuts taken to get things up and running (which are mostly not inherent to
the xml schema, and should not be too difficult to remove from the py and
the XML schema, and should not be too difficult to remove from the py and
decode/disasm utility):
* Maximum "field" size is 64b