lantiq: Fixed brnImage signature for the VGV7510KW22BRN images
The old signature only worked because brnboot ignores the leading "5" in the signature. We can see the correct signature when flashing a brnImage via recovery web-interface, in this case brnboot reports: [CGI-Signature Check] buf:[BRNDA6431], sigInFlash:[BRNDA6431] Thanks to Mathias Kresin for reporting this. Signed-off-by: Martin Blumenstingl <martin.blumenstingl@googlemail.com> SVN-Revision: 48269
This commit is contained in:
parent
f8d2ec6e9d
commit
deb4c31da4
1 changed files with 1 additions and 1 deletions
|
@ -417,7 +417,7 @@ Image/BuildKernel/Profile/VGV7510KW22NOR=$(call Image/BuildKernel/Template,VGV75
|
|||
Image/Build/Profile/VGV7510KW22NOR=$(call Image/Build/$(1),$(1),VGV7510KW22NOR)
|
||||
|
||||
Image/BuildKernel/Profile/VGV7510KW22BRN=$(call Image/BuildKernel/Template,VGV7510KW22BRN,$(1))
|
||||
Image/Build/Profile/VGV7510KW22BRN=$(call Image/Build/$(1),$(1),VGV7510KW22BRN,5BRNDA6431,0x12345678,0x04c11db7,$(1))
|
||||
Image/Build/Profile/VGV7510KW22BRN=$(call Image/Build/$(1),$(1),VGV7510KW22BRN,BRNDA6431,0x12345678,0x04c11db7,$(1))
|
||||
|
||||
Image/BuildKernel/Profile/VGV7519NOR=$(call Image/BuildKernel/Template,VGV7519NOR,$(1))
|
||||
Image/Build/Profile/VGV7519NOR=$(call Image/Build/$(1),$(1),VGV7519NOR)
|
||||
|
|
Loading…
Reference in a new issue