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]

where to put platform specific code


I've implemented a variant and a platform HAL. Now I want to add two more features which don't seem to be covered by the standard eCos file structure.

I have the diagnostic serial interface in the variant HAL, but for compatibility with the common HAL everything's still named hal_diag.*

First, I want a LED funtion. I'm thinking about declaring the interface in the variant's hal_diag.h, and implementing it in platform_misc.c. Good?

Second, I have some platform-specific functions (shift register with output pins). Would you make a driver package for that, or can they go somewhere into the platform HAL? In the latter case, which header and source file names should I use?

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


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