MobileRead Forums - View Single Post

Adam B. · 11-14-2008, 11:18 AM

I've talked to Karel at iRex about our custom firmware poject, and we have an unfortunate piece of news. We will not be able to include the Mobipocket reader, or software keyboard in our firmware release. The problem is that we cannot redistribute these proprietary programs not created by iRex.

While this is a setback, we have a few options. I've asked Karel, if a package can be requested from the IDS containing these files. This way we can distribute the firmware without the files, and have the iLiad connect to the IDS, and download them after the firmware reflash is complete.

The second option may be to run a "pre install" script. This copies the necessary files from internal memory, to the CF card or protected storage area. Then, the reflash is performed and files are automatically copied back after it's complete. We may be able to automate this process if we modify the reflash scripts, but those will have to be flashed before the app.image.

We want the process of installing the community image to be as seamless for the end user as possible. Idealy, it would be good to do it in one step without forcing the user to connect to IDS to get these components.

Thoughts, ideas, suggestions?

11-14-2008, 11:18 AM	#1
Adam B. Addicted to Porting Posts: 1,697 Karma: 7194 Join Date: Oct 2006 Location: Indianapolis, IN Device: iRex iLiad, Nokia 770, Samsung i760	Redistributing Reflash Image I've talked to Karel at iRex about our custom firmware poject, and we have an unfortunate piece of news. We will not be able to include the Mobipocket reader, or software keyboard in our firmware release. The problem is that we cannot redistribute these proprietary programs not created by iRex. While this is a setback, we have a few options. I've asked Karel, if a package can be requested from the IDS containing these files. This way we can distribute the firmware without the files, and have the iLiad connect to the IDS, and download them after the firmware reflash is complete. The second option may be to run a "pre install" script. This copies the necessary files from internal memory, to the CF card or protected storage area. Then, the reflash is performed and files are automatically copied back after it's complete. We may be able to automate this process if we modify the reflash scripts, but those will have to be flashed before the app.image. We want the process of installing the community image to be as seamless for the end user as possible. Idealy, it would be good to do it in one step without forcing the user to connect to IDS to get these components. Thoughts, ideas, suggestions?