This is the mail archive of the ecos-patches@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] |
Jani> these functions just like the others in drv_api are part of Jani> an optional API. cyg_drv_interrupt , cond_vars , mutexes etc Jani> imply interrupts don't they? what are the disadvantages of Jani> adding these functions? Redboot does not use them so it Jani> cannot be affected.
It is not RedBoot itself, it is device drivers (especially ethernet drivers) that may be used by either RedBoot or by an eCos application - hence the term driver API. The various functions in the current driver API will do the right thing irrespective of whether the system is running with interrupts enabled or disabled. Your proposed timer
functions will only work correctly if the system is running with interrupts enabled, otherwise your cyg_current_time() would return misleading data and your cyg_thread_delay() will block forever. The distinction seems pretty clear to me.
Does using polling on some devices, imply that interrupts must be disabled-system wide? Can't redboot use eth drivers in polled mode while a timer interrupt ticks?
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |