On 23 February 2017 at 13:44, Imre Kaloz <kaloz@xxxxxxxxxxx> wrote: > On 2017-02-23 13:29, Rafał Miłecki wrote: >> >> On 23 February 2017 at 13:27, Imre Kaloz <kaloz@xxxxxxxxxxx> wrote: >>> >>> As discussed for other platforms as well, please use the board's name as >>> the >>> same board can end up being sold under multiple model numbers. >>> >>> So please rename the file to bcm47094-linksys-panamera.dts >> >> Huh? Where did you get panamera name from?! > > Your manners shine on these dark days of winter. For about a decade now, > http://192.168.1.1/sysinfo.cgi will show you quite a bit of information if > you are too lazy to look into the GPL tarball or at the original bootlogs. Today I decided to do my homework & check GPL sources of EA9500 fw. I grepped them for panamera and I found this name in few files: ./checkpatches ./src/mod_bdutil/platform/brcm/usbhub.h ./src/mod_bdutil/platform/brcm/buttons.h ./src/mod_bdutil/platform/brcm/usbhub.c ./src/mod_bdutil/platform/brcm/leds_panamera.c ./src/mod_bdutil/platform/brcm/leds.c ./src/mod_bdutil/bdutil.h.panamera ./src/mod_bdutil/Makefile.panamera Unfortunately all these results aren't very clear for getting board name of EA9500. I checked them and panamera is only one of listed boards there. E.g. checkpatches contains following lines: # patched by BRCM for Panamera # patched by BRCM for F70 # patched by BRCM for Pinnacles # patched by BRCM for EA9200 So EA9500 board name could be any of above. Similarly there are following Makefiles in EA9500 GPL package: Makefile.audi Makefile.bentley Makefile.blk-mamba Makefile.carrera Makefile.esprit Makefile.f70 Makefile.focus Makefile.honda Makefile.impala Makefile.lemans Makefile.mamba Makefile.panamera Makefile.pub Makefile.r8 Makefile.spyder Makefile.taurus Makefile.viper Makefile.viperuivm Makefile.wraith So again, any of these name could be EA9500 board name. Will you be so generous to tell us how did you get EA9500 board name by just looking at GPL sources? -- Rafał -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
