-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Somebody in the thread at some point said:
|> # strings current-uboot.bin | grep git |> U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb (Aug 4 2008 - 02:33:52) |> Neo1973 Bootloader U-Boot 1.3.2+gitr18+64eb10cab8055084ae25ea4e73b66dd03cc1a0cb |> |> So obviously, the version on u-boot's prompt is not meanlingful, |> then... :( |> |> Should I file a bug report ? | | | I would consider it a bug that the version on u-boot's prompt is not | meaningful, although I know in some cases that comes out of the source | control package automatically and is not easily fixed. Is that the case | in our case, or is this an error that can be fixed? It turned out the guy was booting his NOR U-Boot and reporting the version data from that. He said his NAND U-Boot version string when he did see it was good (ie, had the correct date and git hash). - -Andy -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org iEYEARECAAYFAkiXQwMACgkQOjLpvpq7dMqHTQCfcnweBXMKAk2zAZabxZKUzhAE +6UAn0rYPJe19mG9E53jcjgpWZxrWGQB =DA6m -----END PGP SIGNATURE----- _______________________________________________ support mailing list support@lists.openmoko.org https://lists.openmoko.org/mailman/listinfo/support