On Tue, May 3, 2011 at 8:37 AM, Florian Fainelli <[email protected]> wrote: > On Wednesday 27 April 2011 21:54:49 Maxim Osipov wrote: >> On Wed, Apr 27, 2011 at 8:19 PM, Hauke Mehrtens <[email protected]> wrote: >> > On 04/27/2011 09:05 PM, Maxim Osipov wrote: >> >> On Tue, Apr 26, 2011 at 5:04 PM, Maxim Osipov <[email protected]> > wrote: >> >>> Signed-off-by: Maxim Osipov <[email protected]> >> >>> --- >> >>> target/linux/at91/Makefile | 2 +- >> >>> .../at91/flexibity/base-files/etc/config/dhcp | 27 + >> >>> .../at91/flexibity/base-files/etc/config/network | 20 + >> >>> .../at91/flexibity/base-files/etc/config/system | 8 + >> >>> .../flexibity/base-files/etc/config/transmission | 62 + >> >>> .../base-files/etc/init.d/custom-user-startup | 22 + >> >>> target/linux/at91/flexibity/config-2.6.37 | 2514 >> >>> ++++++++++++++++++++ target/linux/at91/flexibity/image/Makefile >> >>> | 27 + >> >>> target/linux/at91/flexibity/target.mk | 16 + >> >>> 9 files changed, 2697 insertions(+), 1 deletions(-) >> >>> create mode 100644 >> >>> target/linux/at91/flexibity/base-files/etc/config/dhcp create mode >> >>> 100644 target/linux/at91/flexibity/base-files/etc/config/network >> >>> create mode 100644 >> >>> target/linux/at91/flexibity/base-files/etc/config/system create mode >> >>> 100644 target/linux/at91/flexibity/base-files/etc/config/transmission >> >>> create mode 100755 >> >>> target/linux/at91/flexibity/base-files/etc/init.d/custom-user-startup >> >>> create mode 100644 target/linux/at91/flexibity/config-2.6.37 >> >>> create mode 100644 target/linux/at91/flexibity/image/Config.in >> >>> create mode 100644 target/linux/at91/flexibity/image/Makefile >> >>> create mode 100644 target/linux/at91/flexibity/target.mk >> > >> > Hi Maxim, >> > >> > I do not have this board or any other board supported by the at91 >> > target, so I am unable to test anything, but I have some questions. >> > >> > Why did you create a new subtarget and why didn't you integrate >> > flexibity into one of the existing subtargets? >> > Why does the flexibity subtarget use kernel 2.6.37, but the other >> > subtargets are using 2.6.38? >> > >> > Hauke >> >> Hi Hauke, >> >> The boards are different - so different devices, config, modules, etc. >> The same with base-files customisation - it cannot be shared with >> other hardware. Regarding the kernel - I've chosen the most used in >> OpenWRT kernel version where my patches are already included. 2.6.38 >> doesn't build for me yet and I don't want too many experimental >> things. > > Please use a profile for this instead of a completely separate target. If your > profile requires a different kernel configuration, then let profiles also > supply > their specific kernel configuration.
Okay. But what the purpose of subtarget in this case? I had an impression that profile is something like a distro in OE. And subtarget is similar to machine. I. e. I had plans to add several profiles with specific sets of packages for my subtarget. In what situation I should add subtargets and profiles? Kind regards, Maxim _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
