rtems-libbsd build error

Vijay Kumar Banerjee vijaykumar9597 at gmail.com
Sun Apr 7 12:35:31 UTC 2019

On Sun, Apr 7, 2019 at 5:37 PM Christian Mauderer <list at c-mauderer.de>

> Am 07.04.19 um 13:08 schrieb Vijay Kumar Banerjee:
> > Hi,
> >
> > I had a look at the files related to HDMI drivers, to figure out
> separate
> > compilable parts that can be imported together and ported to RTEMS.
> > I figured that the import can be done in two parts, one for am335x_lcd
> > and one for the tda19988 framer. I have also opened a new branch for
> > am335x_lcd and have done a clean import and some basic first part of
> > the porting.
> >
> > https://github.com/thelunatic/rtems-libbsd/tree/am335x_lcd
> >
> > I had a look at the CONTRIBUTING guide and have also generated the
> > rtems-bsd-kernel-namespace.h ( not yet pushed to the remote)
> >
> > Does it look good to you?
> > What is the next set of things to do to port it to RTEMS?
> Hello Vijay,
> does everything compile and link correctly? If yes: does the software
> run on the target and is the hardware detected during boot without
> throwing an exception somewhere?
> I have checked that everything compiles and links properly with the
But Unfortunately, I don't have an lcd display module right now. I only
have a
standard monitor that works with hdmi cable ( checked it to be working with
FreeBSD image). To work with the HDMI port, I think we'll need the
tda driver
imported as well.
Is it alright if I create another set of commits to import the tda driver
as well, and
then try to run it in the target with HDMI?

> From a quick look at the patches I would move the generated files (in
> rtemsbsd directory) to the port commit so that the import commit really
> only contains unchanged imported files. But that is a matter of opinion.
> Understood. I'll move them to the port commit.

> Best regards
> Christian
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20190407/22712b99/attachment-0002.html>

More information about the devel mailing list