blackfin bf537ezlite bsp
allanh-rtems2 at kallisti.com
Tue Nov 9 19:21:01 UTC 2010
On Tue, 9 Nov 2010 00:04:34 -0500, Mike Frysinger wrote:
> On Tue, Nov 2, 2010 at 13:16, Joel Sherrill wrote:
> > Then this sounds VERY VERY much like a BSP variant. ?Is the
> > core of the board is the same, then the board name came
> > used in configure.ac to trigger building specific features.
> not really. i highly doubt RTEMS has an audio stack let alone codec
> drivers for the parts that are on the board. so if you ignore those,
> the software is exactly the same.
> however, on the off chance RTEMS does support these codecs, it would
> still need to dynamically detect whether the codecs are connected
> (since the ezkit has switches to disconnect them from the
> Blackfin/power). in which case the BSP code would still be exactly
> the same.
There is an SPI driver in the bfin libcpu which has successfully
communicated with a codec, although not the same one that is on the
ezkit. There is also an SPORT driver only in my local tree because
so far it is untested, but when it has been tested it will also be in
Both of these could be instantiated by the BSP, and of course the BSP
could include code to dynamically detect the codecs. However,
dynamically detecting those means the drivers would be present,
increasing the minimum footprint a little, in all bf537stamp builds.
So I'd suggest adding some configure options that would control whether
they're included at all. Then BSP variants might be useful to change
the default state of those configure options.
Allan N. Hessenflow allanh at kallisti.com
More information about the users