2013.01.19. 18:29 keltezéssel, Paul Fertser írta: >> I agree that this adds some complexity. However both the sysupgrade and >> factory >> images were provided for these boards, and if one of them disappear users >> will >> complain about that. > > Right, they might. Probably it'd be nice to write down the explicit > rules somewhere once and then always refer users to them.
http://wiki.openwrt.org/doc/howto/obtain.firmware.download#file.naming http://wiki.openwrt.org/doc/faq/before.installation#what.is.the.difference.between.the.different.image.formats >> And what should we tell to the users? >> >> - On board A from vendor B use the image without any suffix, but be aware >> that >> it is only working with the sysupgrade command from OpenWrt." > > I think if the image is only suitable for sysupgrade it should have a > -sysupgrade suffix. > >> - On board C from vendor D, feel free to use the image without any suffix, >> and >> that will work with the original web interface and with OpenWrt as well. > > Yes, if the image has no suffix i'd expect it to be universally applicable. > >> - On board E from vendor F, the image with the -factory prefix must be used >> from >> the factory web interface, and the -sysupgrade image must be used to upgrade >> an >> existing OpenWrt installation. > > Yes. > >> Additionally, the fact that the factory images can be used for sysupgrade on >> some boards does not mean that this will be true always. Of course, the >> factory >> format won't change but we might want to use a generic format for sysupgrade >> on >> all boards later. There were plans for that. > > In that case the images will start to differ so all the targets that > have means to generate factory images can start generating > -factory-named images plus a sysupgrade image. This way we would have three different name schemes for the firmware images instead of two. We have used 'universal' images on the ar71xx platform three years ago but those were replaced by the factory/sysupgrade images. I'm not going to reintroduce the universal images again. >>> Alternatively, i'd require every target to generate both -factory and >>> -sysupgrade images >> >> This won't happen until someone does not investigate the format of the >> factory >> images and write a tool for them for the boards where we are not providing >> factory images yet. > > I meant to say that this alternative proposal is to require every > target to generate a sysupgrade image and (whenever possible) a > factory image but if that factory image can also be used for > sysupgrade they should be explicitely the same so that the developers > looking through the Makefiles will never be confused about that. If a developer working on a particular board he/she should know if that board requires different image for the initial flashing or not. >> More consistency? The -factory images must be used to flash OpenWrt from the >> original web interface, and the -sysupgrade images must be used to upgrade an >> existing OpenWrt installation. This is quite consistent IMO. > > Ok, so if that's declared the policy It is not a declared policy, rather it is chosen by the maintainer of the given target. > (it's about the same as my second suggestion but i'd prefer to require > sysupgrade files be copied from factory files when possible), Copying a sysupgrade image from the factory file is not always a good idea even if it is possible on some boards. For example, the factory images of the ar71xx based TP-Link boards can be used for sysupgrade at the moment, however the size of the factory images are fixed (the factory web interface verifies that). The sysupgrade files does not have such requirement so those can be much smaller. In this case it makes no sense to duplicate a ~8MB image. > it should be written down somewhere and all the new targets be required to > adhere to it. Sure, it would be good if it would be consistent across all supported platforms. However I'm not going to change every platform to follow this policy. -Gabor _______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/mailman/listinfo/openwrt-devel
