I do embedded Linux porting. The big job is writing drivers and building the device tree. This would be so much simpler if schematics could be annotated with scrapable clues about pin connections and device parameters (e.g. device tree fragments). Its all derivable from the schematic and chip specs, but that part could be automated almost completely.
It would put me out of a job, but better than shooting myself in the head next time I have to face 40 hours of slogging through data sheets.
Manufacturers are starting to produce register maps in the form of SVD's (an xml doc?). Would starting with this not be a good start in producing the FDT?
Nope. But fortunately most chips have widely available datasheets. Except Chinese knockoffs which can involve lots of sleuthing and black-box testing. Had to write a camera driver for a clone that had spotty support (a poor copy of a better device), took a month to get it right.
It would put me out of a job, but better than shooting myself in the head next time I have to face 40 hours of slogging through data sheets.