[OpenWrt-Devel] [PATCH 2/9] ar71xx: PowerCloud CAP324 image generation
openwrt at daniel.thecshore.com
Mon Sep 7 16:38:58 EDT 2015
Sorry meant to cancel after I looked closer.
However, because it looks like it involves a whack of undocumented
variable settings and rather a mess, to be frank, so I doubt I'll get to
it anytime soon if ever because I think it would take way more effort
than I think it's worth (it certainly looks to me like a lot more effort
than the old way, in part because of lack of documentation, and in part
because there's more to write for new oems).
On 2015-09-07 4:14 PM, Daniel Curran-Dickinson wrote:
> On 2015-09-07 3:01 PM, Daniel Dickinson wrote:
>> On 2015-09-07 8:29 AM, Alexander Couzens wrote:
>>>> diff --git a/target/linux/ar71xx/image/Makefile
>>>> b/target/linux/ar71xx/image/Makefile index 8f609de..15bb6a3 100644
>>>> --- a/target/linux/ar71xx/image/Makefile
>>>> +++ b/target/linux/ar71xx/image/Makefile
>>> Could you migrate to the new image Makefile format?
>>> Like the tplink wdr4300 is using.
> Are you a developer? It looks to me like the tp-link format you mention
> is specifically for tp-link devices.
> The devices I did are follow the format of every device except those
> tp-link devices, and I am not aware of these devices *having* a hardware
> id like the tp-link devices, not am I seeing in particular the benefit
> of the 'new' format over the old (in fact the new format seems a whole
> lot more verbose).
>> Will look at that, but probably not until next weekend.
>>> IMHO: I'm not sure if we need 2 builds for the devices, when only the
>>> layout is the difference.
>>> When using the nocloud layout is it possible to go back to the OEM
>> No, hence the two builds.
>>> openwrt-devel mailing list
>>> openwrt-devel at lists.openwrt.org
>> openwrt-devel mailing list
>> openwrt-devel at lists.openwrt.org
openwrt-devel mailing list
openwrt-devel at lists.openwrt.org
More information about the openwrt-devel