On 06/05/2013 10:34 PM, Paul Walmsley wrote: > Hi Stephen, > > thanks very much for the review - > > On Wed, 5 Jun 2013, Stephen Warren wrote: > >> On 06/04/2013 11:59 PM, Paul Walmsley wrote: >>> >>> Here are some basic Tegra test results for Linux v3.10-rc1. >>> Logs and other details at: ... >> I'm curious what the difference is between the "t33beaver" and >> "tegra30-beaver" path entries is, in the following URL: >> >> http://www.pwsan.com/tegra/testlogs/test_v3.10-rc1/20130519152115/boot/t33beaver/tegra30-beaver/ >> >> It might be better to call this board just "tegra30-beaver" for >> consistency with other upstream tools like cbootimage-configs and the >> DTB filename. > > In the boot test environment here, "t33beaver" uniquely identifies the > board, while "tegra30-beaver" identifies the DTB used to boot it. > So if an alternate DTB were used, the boot test path would be: > > ../boot/t33beaver/tegra30-beaver-alternate/ > > If it's important to you, I'll change it. Otherwise, I'd prefer not to > call the board 'tegra30-beaver' -- mostly to avoid confusing myself > between the board name and the DTB name :-) Could you name the directories .../boot/board-tegra30-beaver/tegra30-beaver.dtb/ or ../boot/board-tegra30-beaver/tegra30-beaver-alternate.dtb/? I'd really love not to propagate a different set of names for the boards. -- To unsubscribe from this list: send the line "unsubscribe linux-tegra" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
