I think the way we incorporate hw vendor libraries into RTEMS must be considered with care, or else we risk ending up with lots of these dumps of vendor codes in RTEMS. I would like to consider the options more.
-Gedare On Wed, Mar 12, 2014 at 12:50 PM, Joel Sherrill <joel.sherr...@oarcorp.com> wrote: > Thanks for the long answer on the other email. It put me in the > right frame. > > On 3/12/2014 11:22 AM, Ralf Kirchner wrote: >> hwlib has ben reduced to only those files actually used by the BSP. > Asking ignorantly, what is the value long-term of doing this? Does it > make it easier > or harder to merge future versions? Add support for other peripherals. > > How is hwlib versioned by Altera? Will it be easy to go back to the same > version > and get matching pieces? > > Other than space and compile time, what's the benefit/ > > Looking back at the current TCP/IP stack, it left out pieces which were > not viewed > as necessary. The new approach is what I call a deep net. Deep net > seems to > provide a stronger foundation. I think we are looking at shallow versus > deep with > this and want to make sure we consciously choose. > >> _______________________________________________ >> rtems-devel mailing list >> rtems-devel@rtems.org >> http://www.rtems.org/mailman/listinfo/rtems-devel > > -- > Joel Sherrill, Ph.D. Director of Research & Development > joel.sherr...@oarcorp.com On-Line Applications Research > Ask me about RTEMS: a free RTOS Huntsville AL 35805 > Support Available (256) 722-9985 > > _______________________________________________ > rtems-devel mailing list > rtems-devel@rtems.org > http://www.rtems.org/mailman/listinfo/rtems-devel _______________________________________________ rtems-devel mailing list rtems-devel@rtems.org http://www.rtems.org/mailman/listinfo/rtems-devel
