>If I understand correctly, the Debian kernel can't replace the NTC kernel because it does not have NAND support, but the NTC kernel's NAND support is not proprietary; it's other drivers/firmware that make the NTC kernel non-free.

That's how I understood it. I haven't been able to find any explicit proclamations that it is (the relevant drivers here are free, but I'm not sure if they're the only components required); however, the article here and the "Liberating PocketChip" thread on the arm-netbook mailing list seem to suggest they should be.

>In that case, would it be feasible to adapt this to deblob the NTC kernel?

That should work- a little bit of tinkering might also be needed for the buildroot file with the configs for the kernel, perhaps, but it doesn't look like it should be much if anything.

>I don't really understand the script, but it seems to have one or more functions that it runs for each non-free file (reject_firmware and clean_blob for .c files, clean_mk for makefiles, drop_fw for .bin files, etc.) If I find a list of all non-free drivers/firmware in the NTC kernel and modify the deblob script for the files associated with each one, could that deblob the NTC kernel, or is it not that simple?


Admittedly, I don't really understand it either, but your description looks accurate as far as I can tell. In fact, it should be possible to list any non-free components just by running the deblob_check script included with the deblob scripts. If you run the deblobber first, then (hopefully) the listing should include just the NTC/Sunxi additions.

Reply via email to