Control: tags 812395 moreinfo On 2016-01-23, Vagrant Cascadian wrote: > On 2016-01-23, Rick Thomas wrote: >> I believe the following to be true based on experiments with my two >> sheevaplugs: >> >> If your Sheevaplug has a u-boot version prior to 2014.10+dfsg1-5, >> including any of the original "Marvell" versions, the environment is >> located at 0x60000 and this should be reflected in the "Device offset" >> field in the /etc/fw_env.config file. > > I got the impression from Martin Michlmayr in a thread on debian-arm > that the original Marvell versions had their offset at a different > location? > > https://lists.debian.org/debian-arm/2016/01/msg00103.html > > So the 0x60000 address isn't exactly for all versions prior to > 2014.10+dfsg1-5... > > >> If your Sheevaplug has a u-boot version of 2014.10+dfsg1-5, e.g. if >> you upgraded u-boot while running Debian Jessie, or 2016.01+dfsg1-1 >> or later from Debian Stretch or later, the environment is located at >> 0x80000 and this should, in turn, be reflected in the "Device offset" >> field in the /etc/fw_env.config file. > ... >> If this is correct, it needs to be reflected in >> /usr/share/doc/u-boot-tools/examples/sheevaplug.config so that users >> can configure /etc/fw_env.config correctly for their particular machines. > > The current 2016.01+dfsg1-1 package includes entries for both offsets > (0x60000, 0x80000), with the "legacy" one commented out: > > https://bugs.debian.org/781874 > > If you could please provide a patch detailing exactly what you would > like changed, that would be appreciated.
signature.asc
Description: PGP signature
