Quote:
Originally Posted by knc1
...
For the K1's kernel (also built with menuconfig):
cat /proc/kallsyms
while the kernel is running (do it now - before we both forget).
(/proc/kallsyms contains a list of symbols from every *.o = 'y' or 'm' when the kernel was built)
|
When I tried posting that in a code box, the web browser (or rather, web server thread?) hung when I clicked the MR "preview" button. Too big, so included as compressed attachment (below).
FYI, all those "stl" symbols in that data dump are for the "Sector Translation Layer", which manages all the OneNAND (just a lump of dumb flash memory) write wear-levelling and bad block relocation. The mmc socket does not need this added layer of complexity, because SD cards contain their own (often quite sophisticated) CPU to manage all that out of sight of the hardware application.
BTW, many SD cards are hackable (I even have root shell on one of my SD cards, but logging to flash from that shell, while the SD card is visible to a host PC, is rather hard to sync and sometimes causes file system corruption).