Giters

bmx666 / dtv-demo

Device Tree Visualizer

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

What is the diffrence in the fork?

guysoft opened this issue · comments

commented

Hey,
I have the question, also I think the answer is worth noting in the README

commented

Hi @guysoft, I didn't get it your question 😞 Maybe you asked about dev-0x7C6/fdt-viewer#5 (comment) ?

commented

What I am asking is what has chanaged in terms of functionality in the fork. Is it only compatibility to newer libraries or is there any other features that were added? Or bugs fixed?

So what I understood in your comment above I understand it's only library updates?

commented
  1. The initial repo was created as MVP to visualize simple DTS-files. I tried to contact with developer to maintain project and implement new features, but without any success
  2. A lot of PoC code: specific paths for dts-files, issues and crashes during dts visualization
  3. I used this project as a skeleton for my idea and another problem, in my projects I have 100+ dtsi and dts overlay files for 10+ boards and during a new BSP release from a 3rd party company it's easy to go crazy comparing the difference in dtsi files in new releases, especially after the dtbo merge, it's hard to tell what's left, what's been removed or added. That's why I forked and extended the original DTC to keep all the history of all added, removed or renamed properties, nodes and labels during the overlay process in the generated dts that are used by my fork. (See README - DTV with patched dtc and DTV with overlays). And I extended original project to support that feature.
  4. add a command line to open dts without a UI menu (quite annoying doing it 4 hours a day)
  5. add a modified pyFDT library to make it easier to parse the generated dts after the merge process
  6. add ovmerge perl script from the RPi project, which also made the merging process easier
  7. add function to independently support the original DTC and my patched DTC.

@guysoft I'm not a big fan of the "why I did my own fork" in README, I just shared my idea to make my workflow easier. If you don't like the README, you can always contribute and add more details, feel free to.

commented

Ok cool, thanks for sharing and explaning