On Mon, Nov 20, 2017 at 06:50:30AM +0100, Sebastien Marie wrote: > When it did that, it uses the object (I didn't recall the exact name) > with the previous mentioned array, with *default* configuration. So the > previous modification done with config(8) is cleared.
Yeah, I figured that out after I updated the saved KARL hash and then my box came up with no serial console :). > For me, there is currently no way to ask config(8) to alter the right > file in /usr/share/relink/kernel to "ship" the modification in all > future generated KARL kernels. I thought that might be the case; maybe someday config(8) will be extended to work with the object files as well as the kernel binary itself to allow that. > - makes your changes in /usr/src/sys, build and install a new no-GENERIC > kernel (and do it at each upgrade) If I do that, can the resultant object files (which will have my com2 irq change) be used with KARL? Hmm, it seems like all I really need to do is compile a new com_isa.o and drop it in to the existing directory? Or replace whichever object file contains the constant I need to change; it's not like I'm modifying code or making any drastic changes... Hmm, I'll have to compile a new kernel and poke at it; it'll just be a matter of remembering to redo it after patches, but I already had to redo the config -e anyway. Thanks...
