This is the mail archive of the ecos-discuss@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: HAL architecture question


Dinesh Kumar <mljangir@yahoo.co.in> writes:

> I am little confused about HAL architecture. The
> directory "hal" contains many subdirectories (arm,
> common, i386, powerpc and many more).
> Is subdirectory "common" used by all other
> subdirectories? 

"common" contains code that lives at the HAL level but which is
platform-independent. Things like the virtual vector interface and the
GDB stubs live here.

> 
> Now the subdirectory "arm" contains more
> sub-subdirectories (integrator etc, similarly powerpc
> subdirectory also). AFAIK sub-subdirectory
> "integrator" is a target board having ARM 920t
> processor plus a particular configuration of other
> devices or peripherals. While in subdirectory powerpc,
> I see sub-subdirectory like mpc8260, which is a
> processor. My question is sub-subdirectories represent
> an processor architecture or a target board?
> Considering an example, I have a proprietary target
> board having MPC8260 processor. For porting eCos over
> that board, where my HAL source should go?

Take a look at the HAL documentation and porting guide. It's all
described there.

-- 
Nick Garnett                    eCos Kernel Architect
http://www.ecoscentric.com      The eCos and RedBoot experts


-- 
Before posting, please read the FAQ: http://sources.redhat.com/fom/ecos
and search the list archive: http://sources.redhat.com/ml/ecos-discuss


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