On Fri, Jan 22, 2016 at 1:44 AM, Uwe Kleine-König <[email protected]> wrote: > Hello Roger, > > On Fri, Jan 22, 2016 at 12:11:12AM +0900, Roger Shimizu wrote: >> On Mon, Jan 11, 2016 at 2:23 PM, Martin Michlmayr <[email protected]> wrote: >> > Package: linux >> > Version: 4.3.3-5 >> > Severity: wishlist >> > Tags: patch >> > >> > It would be nice to include the Device Tree model in the reportbug >> > output. On DT based platforms, /proc/cpuinfo only includes quite >> > generic information. >> > >> > Please note that the strange "echo ... $(cat ..)" construct is >> > intentional. 'cat /proc/device-tree/model' leads to a strange >> > character at the end because there's no newline and using echo >> > gets rid of it. >> > >> > diff --git a/debian/templates/image.plain.bug/include-model >> > b/debian/templates/image.plain.bug/include-model >> > index 60a7112..9c6aedd 100644 >> > --- a/debian/templates/image.plain.bug/include-model >> > +++ b/debian/templates/image.plain.bug/include-model >> > @@ -39,6 +39,11 @@ grep_model() { >> > false >> > ;; >> > esac >> > + >> > + # Device Tree model >> > + if [ -r /proc/device-tree/model ]; then >> > + echo "Device Tree model:" $(cat /proc/device-tree/model) >> > + fi >> > } >> > >> > add_model() { >> >> Above patch seems only report the model from dts. >> How about user uses a modified dts, other than the one ships with the kernel? >> >> So I suggest to add a hash-code of the dts used currently. >> Is there any method to find the file location of dts used currently? > The location is not available, because it's put in memory by the > bootloader before jumping into the kernel image. So the best thing you > can do is to extract it from /sys. I don't know off-hand how this works, > but I know who to ask if needed.
According to: http://xillybus.com/tutorials/device-tree-zynq-1 the DTS can be extracted by: scripts/dtc/dtc -I fs -O dts -o ~/effective.dts /proc/device-tree/ I haven't tried this, but if so and we need to add the dependency of dtc command, then we can append the DTS to bugreport. Cheers, Roger
