[ECOS] Disabled packages in Configuration tool

[K. Young Park]

Most device drivers in eCos are composed of two layers.
Physical device driver which directly controls the hardware (located in the packages/devs directory)
and more abstract upper layers which provide hardware independent interface. (located in the packages/io directory).

So you need to include both physical driver and general IO support package to support a new device. 
As for your case, you should include common ethernet support and generic flash memory support.
Of course, you should include the network package too.

-----Original Message-----
From: ecos-discuss-owner@sources.redhat.com [mailto:ecos-discuss-owner@sources.redhat.com]On Behalf Of John Anderson
Sent: Thursday, April 25, 2002 11:44 PM
To: ecosforum
Subject: [ECOS] Disabled packages in Configuration tool


I've created a new platform/target for our Arm based board.  However when I
use the configuration tool I see a couple of the packages disabled.  I've
included the at91/EB40 Flash and the CS8900 Ethernet controller packages and
they are grayed out.  Can anyone tell me what dependancies/definitions are
missing and how does the configuration tool know to disable a package?  You
would think if a package is included in a target then being disabled would
be an error of some sort.

John Anderson



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