profile specific patches?
Posted: Mon Jan 25, 2021 2:31 am
I've looked through the build script and can see where the generic and architecture specific patches are applied, but there doesn't seem to be any support for profile specific patches.
The specific use case I had in mind relates to the Netgear D7800, where there is evidence that many production samples have 512MB of RAM (supported by the Netgear D7800 product brochure) however BETA samples are known to only have 256MB of RAM. OpenWrt, after some early toing & froing, only has a DTS configuration for 256MB (recent discussion with some historical links here).
Given that Gargoyle has the concept of profiles within architectures, this could be a case where both 256MB (default) and 512MB (specific profile) builds could exist - provided that there was a satisfactory way to apply a patch to the DTS (or copy an alternate DTS file).
Another potential use case that comes to mind is with the RaspberryPi - one scenario would be to use VLANs on the onboard ethernet port to support both WAN and LAN (requires a VLAN capable switch) as one profile with the alternate approach relying on having a USB ethernet (or USB WiFi adapter) for the WAN and use the onboard ethernet for the LAN as an alternate profile. There are ways to achieve this with smart script logic and possibly some UI changes, but is that a better approach than separate profiles (assuming documentation is also available to guide users to the image they need)?
Are there any better, or simpler/easier, approaches to achieve the same outcomes?
The specific use case I had in mind relates to the Netgear D7800, where there is evidence that many production samples have 512MB of RAM (supported by the Netgear D7800 product brochure) however BETA samples are known to only have 256MB of RAM. OpenWrt, after some early toing & froing, only has a DTS configuration for 256MB (recent discussion with some historical links here).
Given that Gargoyle has the concept of profiles within architectures, this could be a case where both 256MB (default) and 512MB (specific profile) builds could exist - provided that there was a satisfactory way to apply a patch to the DTS (or copy an alternate DTS file).
Another potential use case that comes to mind is with the RaspberryPi - one scenario would be to use VLANs on the onboard ethernet port to support both WAN and LAN (requires a VLAN capable switch) as one profile with the alternate approach relying on having a USB ethernet (or USB WiFi adapter) for the WAN and use the onboard ethernet for the LAN as an alternate profile. There are ways to achieve this with smart script logic and possibly some UI changes, but is that a better approach than separate profiles (assuming documentation is also available to guide users to the image they need)?
Are there any better, or simpler/easier, approaches to achieve the same outcomes?