This is the mail archive of the ecos-devel@sources.redhat.com mailing list for the eCos project.


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: Porting question


Uwe Kindler wrote:

Now I would like to know your opinion - if two processor families differ in register structure and stack structure like the H8S and H8300, would it be better to create a new architecture HAL H8S (and then single variants for the single family members i.e H8S2357, H8S2128, H8S2633...) or would it be better to ceate the H8S port as a new variant of the H8300 architecture.

Unhelpfully my answer is that I suppose it depends on just how much it diverges. If the instruction set would be entirely the same, and it's just a few register structure definitions in hal_arch.h, that would be one thing. But I suspect there's more difference than that.


It could mean that maybe the original port should have had a separation between a main H8 HAL and the H8300 variant.

It's up to you though, bearing in mind that if it's too hacky we may not want to incorporate the improvements back ;-).

NB I also know Nick Garnett is actively working on incorporating the H8 HAL patch backlog right now. It would be worth working off the back of that.

Does the GCC port to this work on 32-bit mode? You'll find the eCos port is a lot easier if it does.

Jifl
--
eCosCentric    http://www.eCosCentric.com/    The eCos and RedBoot experts
--[ "You can complain because roses have thorns, or you ]--
--[  can rejoice because thorns have roses." -Lincoln   ]-- Opinions==mine


Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]