Skip to content

Ethetnet boot documentation#260

Closed
chintan013 wants to merge 4 commits intoTexasInstruments:masterfrom
chintan013:ethboot_doc
Closed

Ethetnet boot documentation#260
chintan013 wants to merge 4 commits intoTexasInstruments:masterfrom
chintan013:ethboot_doc

Conversation

@chintan013
Copy link

No description provided.

@praneethbajjuri
Copy link
Collaborator

@danish-ti to review

Update Ethernet boot documentation with device specific config snippet to
avoid adding the same code-block for every device. Also add config
variables of the device for which documentation already exist, AM64X and
AM62X.

Signed-off-by: Chintan Vankar <c-vankar@ti.com>
Ethernet boot support has been added to J722s SoC, add documentation for
the same.

Signed-off-by: Chintan Vankar <c-vankar@ti.com>
Ethernet boot support has been added to AM62px SoC, add documentation for
the same.

Signed-off-by: Chintan Vankar <c-vankar@ti.com>
Ethernet boot support has been added to J721s2 SoC, add documentation for
the same.

Signed-off-by: Chintan Vankar <c-vankar@ti.com>
Copy link
Contributor

@danish-ti danish-ti left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

If using ISC dhcpd an example host entry would look like this:

.. code-block:: text
.. parsed-literal::
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Alright, this can kind of work, but there are issues.

  1. Ifconfig is essentially a mask. This section will still be parsed on other platforms and will result in a replacement error if they do not have the replacement definition. Right now you've defined the variable for all machines that include this file, so it's fine. You can remove that ifconfig mask as it's not doing anything.

  2. Parsed literals will not be escaped. Any valid RST will be parsed. This example is fine right now. Any additions will have to take this into account.

This is why I was pushing more towards defining a table and user template here. I'll let others weigh in.

@StaticRocket
Copy link
Member

Duplicate

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants