NMT:DTS: Difference between revisions
No edit summary |
No edit summary |
||
Line 14: | Line 14: | ||
4) Make an A-110 firmware be A-100 firmware. | 4) Make an A-110 firmware be A-100 firmware. | ||
: That worked rather well. DTS works. | : That worked rather well. DTS works. | ||
So, while we are changing the firmware, I could add telnet, and even load FUSE. Can I replace NTFS with NTFS-3g automatically? Perhaps not. Replace "mount" with script, but sys_mount() I can not. |
Revision as of 22:33, 3 December 2008
Flashing a A-110 firmware on A-100 does fail pretty early on.
1) make A100 think its A110. Will it work? Does it check things too deep? (cpukeys etc)
- Might not be possible, but if it would work, it would make everything complete.
- Changing /etc/config, /etc/kinfo and hostname from 402 to 403, will make it complain about wrong size. Perhaps a better idea is to change the firmware to say 402 in its version: c403dPOPk15
- Unfortunately my first tests of this complained about wrong flash size, this turns out that you have to do a stepping flash before you can do newer firmwares, so this could be re-visited. For now, I have made a 403 firmware be 402.
2) pull out ucode from A110, and add to A100 firmware. Not too hard, but tedious. Have all keys, and CRC code already.
- Apart from ucode, other parts of the software might check for model number to enable/disable 2ch mix-down. So we might have to do partial 1) anyway.
3) pull out ucode and attempt to get it to initialise after A100 has booted up.
- Unlikely replacing ucode after boot will work, and may still need part of 1) to work.
4) Make an A-110 firmware be A-100 firmware.
- That worked rather well. DTS works.
So, while we are changing the firmware, I could add telnet, and even load FUSE. Can I replace NTFS with NTFS-3g automatically? Perhaps not. Replace "mount" with script, but sys_mount() I can not.