Revert "scripts: add local version number file" #605
Conversation
lgirdwood
requested review from
jajanusz,
lbetlej,
mmaka1 and
plbossart
as code owners
|
@zhuyingjiang .tarball-version generation looks ok - it should be there when you do |
|
OK, the old version has no .tarball-version in it, and I checked today the latest code "make dist" can generate .tarball-version and .version. But a new issue found that(1) all the scripts are not in the tarball, that make the uncompressed tarball still can't compile. (2) the git tag after v.1.1 is not the format that git describe needed, so "git describe" always got v1.1. I think it better to open new issue to solve these. |
|
(2) issue is caused by the fact that we probably have no clear tagging/released policy established and tagging for v1.2 was done differently than for v1.1 - 1.1 is in master 1.2 is only on stable branch so Run |
|
@zhuyingjiang dont worry about 1.2 tag today, this will be fixed for 1.3 since we are all using master today. Just make sure that make dist generates all files and correct version (according to git) to build from a tarball. |
Sometimes it can help to see how the chunks arrive from firmware when comparing logs with the kernel for example. The --mark-chunks flag will add a marker for each new chunk that is printed with a running number and the size of the given chunk, for example: --- Chunk thesofproject#604 start (size: 652) --- [ 0.000000] <inf> init: print_version_banner: FW ABI 0x301d001 DBG ABI 0x5003000 tags SOF:v2.5-stable-branch-2772-g76e650e56598-dirty zephyr:v3.7.0-2127-ge7c84756087f src hash 0x4ff3fd64 (ref hash 0x4ff3fd64) *** Booting Zephyr OS build v3.7.0-2127-ge7c84756087f *** [ 0.000000] <inf> main: sof_app_main: SOF on intel_adsp [ 0.000000] <inf> main: sof_app_main: SOF initialized [ 0.000000] <inf> ipc: ipc_cmd: rx : 0x44000000|0x31400008 [11896.403666] <inf> ipc: ipc_cmd: tx-reply : 0x64000000|0x31400008 [11896.404076] <inf> ipc: ipc_cmd: rx : 0x44000000|0x3060004c [11896.404093] <inf> ipc: ipc_cmd: tx-reply : 0x64000000|0x3060004c --- Chunk thesofproject#605 start (size: 196) --- [11896.969658] <inf> ipc: ipc_cmd: rx : 0x11000005|0x0 [11896.969671] <inf> pipe: pipeline_new: pipeline new pipe_id 0 priority 0 [11896.969685] <inf> ipc: ipc_cmd: tx-reply : 0xb1000000|0x0 --- Chunk thesofproject#606 start (size: 2236) --- Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Sometimes it can help to see how the chunks arrive from firmware when comparing logs with the kernel for example. The --mark-chunks flag will add a marker for each new chunk that is printed with a running number and the size of the given chunk, for example: --- Chunk #604 start (size: 652) --- [ 0.000000] <inf> init: print_version_banner: FW ABI 0x301d001 DBG ABI 0x5003000 tags SOF:v2.5-stable-branch-2772-g76e650e56598-dirty zephyr:v3.7.0-2127-ge7c84756087f src hash 0x4ff3fd64 (ref hash 0x4ff3fd64) *** Booting Zephyr OS build v3.7.0-2127-ge7c84756087f *** [ 0.000000] <inf> main: sof_app_main: SOF on intel_adsp [ 0.000000] <inf> main: sof_app_main: SOF initialized [ 0.000000] <inf> ipc: ipc_cmd: rx : 0x44000000|0x31400008 [11896.403666] <inf> ipc: ipc_cmd: tx-reply : 0x64000000|0x31400008 [11896.404076] <inf> ipc: ipc_cmd: rx : 0x44000000|0x3060004c [11896.404093] <inf> ipc: ipc_cmd: tx-reply : 0x64000000|0x3060004c --- Chunk #605 start (size: 196) --- [11896.969658] <inf> ipc: ipc_cmd: rx : 0x11000005|0x0 [11896.969671] <inf> pipe: pipeline_new: pipeline new pipe_id 0 priority 0 [11896.969685] <inf> ipc: ipc_cmd: tx-reply : 0xb1000000|0x0 --- Chunk #606 start (size: 2236) --- Signed-off-by: Peter Ujfalusi <peter.ujfalusi@linux.intel.com>
Reverts #597