This is the mail archive of the ecos-patches@sourceware.org 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: Moving AUX_CHANNELS, NUM_CHANNELS logic into platform hal


Gary Thomas wrote:

Instead of making the RedBoot networking option to do a "puts" with the AUX_CHANNELS macro, it does now a "implements" command on AUX_CHANNELS, that becomes a interface; then NUM_CHANNELS becomes an option that augments COMM_CHANNELS with a "calculated" value. Is the same thing done in the #defines in redboot.h and hal_if.c, but it seems more general and less redundant.

I understand the mechanics - I still don't see how this changes anything. Do you have a platform that
needs more "AUX" channels?

In fairness, this will probably want to be done at some point anyway. Think of a console back channel for JTAG debugging, for example.


Jifl
--
--["No sense being pessimistic, it wouldn't work anyway"]-- Opinions==mine


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