On 01/06/16 06:42, Chris Johns wrote:
The RTEMS driver infrastructure is not capable
enough to deal with a plug-and-play architecture like x86.
This does not make sense to me and I fail to see how it relates to the
previous statement. The original classic API for RTEMS is based on a
VME bus standard and while not a hot swap bus architecture it did
allow a plug in architecture based on a huge range of slave boards.
The fact an architecture or bus has plug-and-play support does not
mean RTEMS has to provide such support nor a BSP has reached a dead
end because it does not.
The standard RTEMS driver infrastructure offers no support for
auto-configuration, power-management, hot-plug and so on. The FreeBSD
newbus infrastructure offers all of this. I don't think it make sense to
add or event develop on our own such a functionality on a per-BSP basis.
--
Sebastian Huber, embedded brains GmbH
Address : Dornierstr. 4, D-82178 Puchheim, Germany
Phone : +49 89 189 47 41-16
Fax : +49 89 189 47 41-09
E-Mail : sebastian.hu...@embedded-brains.de
PGP : Public key available on request.
Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
_______________________________________________
devel mailing list
devel@rtems.org
http://lists.rtems.org/mailman/listinfo/devel
