Yuli Barcohen yuli@arabellasw.com wrote:
I don't mean it already covers DW boards (I haven't got one) though no significant modifications should be necessary.
I didn't deem it, either.
DW boards use CFI-compliant flash so common CFI driver can be used instead of the board-specific one.
Well, although DW use CFI-compliant flash, it still work with a board-specific one at least in CVS. I once used CFI driver on DW but failed.
PlanetCore saves its environment in the I2C EEPROM so PlanetCore can initialise the board accordingly. It's possible to use this information
If so, U-Boot and PlanetCore can share one ENV to work??? IMHO, ENV in EEPROM of PlanetCore use it's own definition keyword. Only to change ENV of U-Boot can meet the requirement of PlanetCore. It will decrease u-boot ENV variability.
in the U-Boot but some hard-coded values still remain. CFG_MONITOR_LEN and CFG_ENV_SECT_SIZE
If used EEPROM for ENV home, could we need to set CFG_ENV_SECT_SIZE?
Actually, I am worring about one thing if we wanted to combine CW nad DW port. That's how to deal with HIGH boot mode[DW] and LOW boot mode[CW] in one image.
time values. Any ideas if and how it's possible?
The "possible" I used was really a draft idea. Don't take it seriously. To me, it isn't worthwhile to implement it. CW is too old to be popular nowdays. Take a look at it's main page if avaiable.
http://www.embeddedplanet.com/products/lite.asp
In one word, you fix on RPXlite is a treasure. Just stop and keep that. Those who are interested on RPXlite[C/DW] can get enough hints from exist port work in CVS.
Thanks for your time,
Sam
___________________________________________________________ 雅虎免费G邮箱－中国最强免费防毒反垃圾超大邮箱 http://cn.mail.yahoo.com/?id=77072