Commit graph

6 commits

Author SHA1 Message Date
Hauke Mehrtens
da7493d8f9 mostly revert commit r22396
CFE does not boot images generated with these checksums because of
wrong checksum.

After flashing then with tftp to my Asus wl500-GPv1 the following messages
are show:
Null Rescue Flag.
Boot program checksum is invalid
Hello!! Enter Rescue Mode: (Check error)

SVN-Revision: 22418
2010-07-30 21:19:49 +00:00
Markus Wigge
7a052dc799 fix CRC32 calculation for sysupgrade
* reduce image size for CRC calculation by fs_mark size

sysupgrade sometimes failed for me and I noticed that it was due
to incorrect CRC values in trx-header after performing it.
It seems that the fs_mark was completely included in the calculation
and that it was nevertheless modified by sysupgrade while appending
the jffs data.
This only occurs for the first boot after sysupgrade as the flashmap
driver recalculates the CRC to an even smaller area when it boots.

SVN-Revision: 22396
2010-07-27 15:37:37 +00:00
Markus Wigge
114ce0bd4c renamed wrt54g3gv2-vf images
'factory' and 'sysupgrade' did not make much sense. A discussion
with jow convinced me that .trx results in a helpdesk disaster.
So I decided to use '.bin' for normal bin-headers and '.noheader.bin'
for the trx-v2 image.
I fixed the wiki accordingly.

SVN-Revision: 22013
2010-07-01 10:48:13 +00:00
Felix Fietkau
812f026323 add back the base-files/image code from brcm-2.4 to brcm47xx
SVN-Revision: 21945
2010-06-26 20:41:49 +00:00
Felix Fietkau
519b6a2f4c remove brcm47xx symlinks to brcm-2.4 (unfortunately svn does not allow a proper type changing commit)
SVN-Revision: 21944
2010-06-26 20:41:40 +00:00
Felix Fietkau
56231056ea strip the kernel version suffix from target directories, except for brcm-2.4 (the -2.4 will be included in the board name here). CONFIG_LINUX_<ver>_<board> becomes CONFIG_TARGET_<board>, same for profiles.
SVN-Revision: 8653
2007-09-06 16:27:37 +00:00
Renamed from target/linux/brcm47xx-2.6/image (Browse further)