View Single Post
Old 11-14-2008, 01:32 PM   #5
Adam B.
Addicted to Porting
Adam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the roughAdam B. is a jewel in the rough
 
Adam B.'s Avatar
 
Posts: 1,697
Karma: 7194
Join Date: Oct 2006
Location: Indianapolis, IN
Device: iRex iLiad, Nokia 770, Samsung i760
Quote:
Originally Posted by jharker View Post
After looking over the boot files posted in the zImage thread, I realized that we may have other issues.

The current initrd and linuxrc script contain, and load, most of the kernel modules. These include buttons, battery, and delta, for which we have the source code. But they also include keystore and sysset (iRex, no source), and tffs (proprietary). Later in the boot process are the pcmcia and usb drivers, whose origins are unknown to me, but iRex only provides binaries for download.

The linuxrc script also calls "imagetodoc", which is a binary, not a shell script.

If and when we eventually update the kernel, some or all of these proprietary modules will need to be recompiled with the new kernel, right? At the very least we'll need the latest tffs, I think.

Am I missing something here?
I'm not sure what keystore does...perhaps encryption with the IDS. Sysset sets hardware configuration parameters and system information. But other than IDS connections and IDS updates, it't not necessary. From what I'm told, there's a new tffs driver in the 2.6 kernel that should work.

Modifying imagetodoc won't be necessary to create custom reflash images, however, it may be an issue if we upgrade to a new kernel, we'll have to see.
Adam B. is offline   Reply With Quote