rtems-libbsd build error

[Vijay Kumar Banerjee]

On Sun, Apr 7, 2019 at 6:24 PM Christian Mauderer <list at c-mauderer.de>
wrote:

> Am 07.04.19 um 14:50 schrieb Vijay Kumar Banerjee:
> >
> >
> > On Sun, Apr 7, 2019 at 6:08 PM Christian Mauderer <list at c-mauderer.de
> > <mailto:list at c-mauderer.de>> wrote:
> >
> >     Am 07.04.19 um 14:35 schrieb Vijay Kumar Banerjee:
> >     >
> >     >
> >     >
> >     > On Sun, Apr 7, 2019 at 5:37 PM Christian Mauderer
> >     <list at c-mauderer.de <mailto:list at c-mauderer.de>
> >     > <mailto:list at c-mauderer.de <mailto:list at c-mauderer.de>>> wrote:
> >     >
> >     >     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 commits.
> >     > 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?
> >     >
> >
> >     You want to test more than I intended. My main concern was whether
> the
> >     BSP still runs without throwing an exception.
> >
> > Okay, I'll test this.
> > Is running the hello world application through gdbserver, enough to
> check
> > that it works without exception?
> > Is there a way to run multiple exes? If I'm asking something that can be
> > found
> > in the docs, a link would help. I couldn't find at first search. :)
>
> I don't think that there are a lot of docs for how to test. Although I'm
> sure that there are some scripts to run a number of libbsd tests, I'm
> not sure where. Maybe in the RTEMS tester but I think that is mainly for
> the core tests?
>
> so far I know, RTEMS Tester is only for core tests. I'll ask in the devel
if there's
some way to run libbsd test with the tester.

> My approach would be to run one of the tests that do something more like
> the media01 from libbsd  (you boot into a shell in that test) and take a
> look whether there are some boot messages regarding the driver. Most
> libbsd drivers tend to tell you that they found their device.
>
> I have tried running media01.exe and it seems to run fine and I see this
nice
line during cpu starting
fb0: <AM335x LCD controller> mem 0x4830e000-0x4830efff irq 36 on simplebus0

> >
> >     For testing the whole system together another set of patches
> importing
> >     the tda driver is OK.
> >
> >     >
> >     >     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/b6d05aa6/attachment-0002.html>