The text below was written while your last posts weren't available yet.
If you know what you're doing ... the second step is it, to repeat this procedure with the current 1750E kernel (the one, you want to use for your alien image) and to save the same file from this build-run, too (and once again show it here).
Afterwards the content of both files should be "diff"ed - only the lines for the BLOB data are of interest. The content of the two BLOBs (the assembler code is only a byte-wise array containing the binary data) should be always the same, no matter which version of FRITZ!OS is used as template - but only for the two used devices. Due to this assumption it should be possible to create a
diff output file, which may be used to apply the needed changes for the DVB-C FDT to the 1750E file, after the latter one was created by the
[...].bin2asm tool.
After the needed change to
kernel.mk (to apply the patch after
[...].bin2asm), you should remove all files matching the template
avm_kernel_config_area* to
enforce their rebuild. The next
make call (with 1750E settings) should create your own kernel, with a properly changed
avm_kernel_config area.
I would assume if freetz-ng exists for quite some time it should already know about this thingy and provide some solution to it.
I don't understand this sentence.
I wrote this tool in the past to SOLVE exactly this problem and it was (partially as code and in a whole as idea) incorporated into Freetz - and as a result into Freetz-NG, too. Are you really astonished, that your use case of 1750E as an "alien" for a DVB-C device isn't fully supported from scratch by Freetz-NG?
If you've used a "standard configuration" for your 7490 with Freetz-NG, the same tool was used to extract the
avm_kernel_config area from the original kernel - logically. But there's no source code BY AVM for these parts and other toolchains beside Freetz and its forks will not be able to build a working kernel without a solution for this problem.
And on again to the problem from #35 ... the found names look like results from a very different setting - usually from a 7490 build. Are you sure, you're looking in the right place? Had you a look at file times? Possibly the correct file is the one without any $DL_SOURCE_ID part - I had a reason for my wish/request to show the content here in the board (as attachment or within a CODE block).
If there's really no other file matching the pattern and the file without DL_SOURCE_ID isn't the needed one, you have to repeat the build process and to create a log file for it (using the provided
fmake script in the base folder of your Freetz-NG checkout - this script is able to show you a help screen, how to use it correctly), which you may attach here. It's rather long, but it's needed completely to analyze, whether the build steps were run and where the results are located.
---------- assembled posts ----------
If you've started a new build, you should consider to stop it, clear the intermediate results and restart it once again - but this time already using
fmake to save the build log.
