linux/meta-xilinx.git/meta-xilinx-core/conf/machine/README, branch masterMirror of git.yoctoproject.org/meta-xilinx.githttps://git.enea.com/cgit/linux/meta-xilinx.git/atom?h=master2024-09-13T13:13:30+00:00conf/machine/README: Update with new values2024-09-13T13:13:30+00:00Mark Hatlemark.hatle@amd.com2024-08-15T23:54:19+00:00urn:sha1:c3100a32377c809d551601087af8c28ccef3c75e
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
various: Remove SOC_VARIANT, split versal and versal-net, add machine_features2024-06-04T23:00:14+00:00Mark Hatlemark.hatle@amd.com2024-06-04T22:51:04+00:00urn:sha1:195e1fa9fb13b21bc41af4e0747d4646caeb65e5
SOC_VARIANT has been remove, we are now only using the YP standard SOC_FAMILY
configuration. The defined families are: zynq, zynqmp, versal and versal-net.
Our decision of breaking up versal-net from versal, is based on the SoC CPU
changes from cortexa72/r5 to cortexa78/r52, thus we're treating it as a
different SoC family.
In order to capture the individual capabilities that we used to handle via
SOC_VARIANT, we have defined the following features (some may have been
previously defined):
- mali400 (zynqmp eg and ev)
- vcu (zynqmp ev)
- rfsoc (zynqmp dr RF capabiltiies)
- aie - (versal ai & premium)
- vdu - (versal ai)
SOC_VARIANT_ARCH and SOC_FAMILY_ARCH are now obsolete and replaced by
MACHINE_ARCH. This is based on the guideline that any recipes that use
MACHINE_FEATURES should be MACHINE_ARCH specific.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
README: Update README on using ATF_CONSOLE2023-08-31T14:27:20+00:00Sandeep Gundlupet Rajusandeep.gundlupet-raju@amd.com2023-08-30T22:14:29+00:00urn:sha1:9240822918e8dabd8232ed4b3fa77f56252b6d6a
Update README on using ATF_CONSOLE instead of ATF_CONSOLE_DEFAULT.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
README: Update the docs on variables2023-07-20T16:56:40+00:00Sandeep Gundlupet Rajusandeep.gundlupet-raju@amd.com2023-07-18T22:13:46+00:00urn:sha1:39569406de065e6c9ff30555c8efb429149fa200
Update READE docs on list of variables used in machine conf.
Signed-off-by: Sandeep Gundlupet Raju <sandeep.gundlupet-raju@amd.com>
Fixed a couple of typos
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
conf/machine: Better document inheritence expectations2022-11-10T23:04:42+00:00Mark Hatlemark.hatle@amd.com2022-11-07T21:55:13+00:00urn:sha1:e041b4fd3be52c1804e63a64cf2764be0c5c8675
See the README files for specific requirements, but we have designed the
machine configurations into an inheritance model. This module can be
further broken into 3 distinct categories of variables:
1 - Variables that MUST be declared BEFORE inheriting the base machine
2 - Variables that SHOULD be declared BEFORE inheriting the base machine,
as they are commonly overridden. (This will need continual review.)
3 - All remaining variables that should only be declared in the machine
.conf file, and MUST be declared AFTER inheriting the base machine.
Signed-off-by: Mark Hatle <mark.hatle@amd.com>
Deprecate BOARD and BOARD_VARIANT support2022-01-14T23:37:05+00:00Mark Hatlemark.hatle@xilinx.com2021-12-18T21:44:31+00:00urn:sha1:4501eaa3c6eac161ec0aaec87d7b648361552912
If the BOARD and/or BOARD_VARIANT is set, continue to allow this to
work, however warn the user it is deprecated.
Signed-off-by: Mark Hatle <mark.hatle@xilinx.com>