[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Perfomance problems and main stream
- Date: Mon, 22 Feb 1999 15:47:15 -0500 (EST)
- From: qqi at world.std.com (Quality Quorum)
- Subject: Perfomance problems and main stream
On Mon, 22 Feb 1999, Mark Johannes wrote:
> Hello,
>
> It is my opinion that we are attempting to move the hardware integration
> layers into a more modular set of components. For some time now, we as
> users of RTEMS as well as developers and maintainers have been hindered by
> the tight coupling of the "BSP" in whole to the executive and toolset
> itself. The approach is the early stages of decoupling these entities to
> provide for a more standalone kernel with multiple peripherals. I believe
> that these discussions are healthy and that we welcome the technical
> viewpoints of the user community. This foem of development team make RTEMS
> better in the long run leveraging against the diverse talent pool.
>
> I agree that the BSP is the area of most diversity, hence the problem.
> What we are really attempting in to provide a framework and architecture
> that allows this diversity to be applied without hindrance. Therefore, I
> believe this will assist the newbie when a clear architecture is presented
> for the structure that he/she has to integrate the application hardware
> within.
IMHO,
BSP should represent no more than common starting point for
various platforms allowing:
1. Boot the system
2. Do debugging
3. Have working samples of basic drivers
Everything else:
1. Is too application specific, so I doubt that
it will be ever possible to coin it into something as universal
as BSP.
2. It should be configured once application is up - so better
debugging of initialization process is possible.
> Sincerely,
>
> Mark Johannes
Thanks,
Aleksey