Kaitai Struct only support purely stateless parsing. That only works up
to the packet layer for Xilinx bitstreams. As there are now both C++
(prjxray) and Rust (gaffe) parsers that work up through config frames,
the KSY only serves to mislead someone that Kaitai Struct works for this
purpose.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Also a few minor changes as requested by @mithro regarding the content itself and rearranged the paragraphs.
Signed-off-by: Davide <davide.toldo@stud.tu-darmstadt.de>
Describes how frame addressing relates to physical chip structure. Rough
notes on how frames are loaded into the device and the packet format
used to operate that state machine.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Target starts sphinx-autobuild which watches the source files and
rebuilds the output on writes. Output is served via a local HTTP server
that injects code to refresh the page when a new version is available.
Saving a source file triggers the browser to reload the page generated.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Tried to merge definitions from wiki/Glossary and my understandings of
terms related to architecture and configuration.
Signed-off-by: Rick Altherr <raltherr@google.com>
When loaded into https://ide.kaitai.io, Xilinx bitstreams can be
visually explored a lot more easily.
Signed-off-by: Rick Altherr <kc8apf@kc8apf.net>
Signed-off-by: Tim 'mithro' Ansell <mithro@mithis.com>