From 5bcb1af59eda025a097a35b032bf14ccd25fa4c0 Mon Sep 17 00:00:00 2001
From: Himanshu kohale <hkohale22@gmail.com>
Date: Sun, 31 Mar 2024 23:23:07 -0400
Subject: [PATCH] final proposal
---
proposals/himanshuk.rst | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/proposals/himanshuk.rst b/proposals/himanshuk.rst
index 47e6607..9b92aa5 100644
--- a/proposals/himanshuk.rst
+++ b/proposals/himanshuk.rst
@@ -106,7 +106,8 @@ How it will be possible, see an example for blink LEDs via device tree ovelay wh
};
-Implementation of device tree
+
+Implementation of device tree :
.. image:: https://devicetree-specification.readthedocs.io/en/stable/_images/graphviz-58c8267ade85edeca7b1b0299af2b1e473987ddc.png
:alt: Device tree Implementation
@@ -120,6 +121,8 @@ BeagleV-Fire also support the robotic cape with librobotcontrol package and cape
but as BBB support the librobotcontrol with more functionality and flexible application, beagleV-fire is not capable for librobotcontrol package due to less number of device_tree fragment present in robotic-cape (.dts) file which is pre-installed in V-fire image.
With help of customization for cape gateware in V-fire which Provide more flexibility to board with cape, librobotcontrol package will support V-fire with robotic cape.
+V-fire Gateware architecture:
+
.. image:: https://docs.beagle.cc/latest/_images/Gateware-Flow-simplified-overview.png
:alt: V-fire Gateware architecture
:align: center
--
GitLab