How to use lvgl on pc386 BSP.

[Karel Gardas]

Hi Jan and Christian,

thanks for your advice! Indeed, dev_nic_e1000 = off solved my troubles
with broken e1000 driver and was able to build libbsd from 5 branch
successfully even on pc686 bsp.

I used that and jumped to compilation of lvgl library which went fine
too. Then I tried lvgl example from rtems-examples and this failed. I
needed to change location of i2c.h header file -- I guess it's not on
bsp generic location and is more BSP specific so no problem changing it
but then I've also needed to add linking with libz in order to solve
linker complains about missing symbols. So at  the end I've finished
with 2 lvgl examples linked.

Unfortunately they are not running or it (hello) is not running I guess
VESA VBE does have some troubles on the testing notebook (lenovo b5400).
Tomorrow I'll try it on more hardware around.

The example diff needed is attached.

Thanks a lot!
Karel


On 9/8/20 7:45 PM, Jan.Sommer at dlr.de wrote:
> Hi Karel,
> 
>> -----Original Message-----
>> From: users <users-bounces at rtems.org> On Behalf Of Karel Gardas
>> Sent: Tuesday, September 8, 2020 7:32 PM
>> To: Christian Mauderer <oss at c-mauderer.de>; Christian Mauderer
>> <christian.mauderer at embedded-brains.de>; users at rtems.org
>> Subject: Re: How to use lvgl on pc386 BSP.
>>
>>
>> Hello Christian,
>>
>> On 9/7/20 6:22 PM, Christian Mauderer wrote:
>>> I have analyzed a bit more:
>>>
>>> We have two main libbsd branches:
>>>
>>> - master
>>> - 6-freebsd-12
>>>
>>> Same for the release. There it is
>>>
>>> - 5
>>> - 5-freebsd-12
>>>
>>> The first one tracks the latest FreeBSD development branch. The later
>>> one tracks the stable FreeBSD 12 branch.
>>>
>>> It seems that the evdev stuff is only on the first branch (master and
>>> 5). So if you compiled 5-freebsd-12 (which is not unlikely - I would
>>> recommend that for application development) the evdev support is _not_
>>> there. That's exactly what you see.
>>>
>>> Depending on your application, you might want to think about switching
>>> to the current master instead of the release. But note that I didn't
>>> compile the PC BSP there. So I'm not sure how well it works. i386 is
>>> normally not a platform that I use for RTEMS applications.
>>
>> thanks a lot for your guidance on this. However libbsd is broken on i386 due
>> to missing fixes/files. See #4052 and #4053 for more information.
>>
>> I've had a curious look into what's going on there trying to cherry-pick fix
>> from the 5-freebsd-12 branch, but the problem is currently over my available
>> time and knowledge. If it's not fixed, I'll hopefully get back to it and try to
>> work on it properly in upcoming weekends.
> 
> For the 5 and master branch (#4052 and #4053), I have already posted patches to the mailinglist.
> You can find the thread here: https://lists.rtems.org/pipermail/devel/2020-August/061373.html
> They got a bit delayed due to the work for the RTEMS5 release and because there were some discussions about branch naming for FreeBSD.
> If you just want to compile FreeBSD (5 or master) for i386 and do not need the e1000 network driver right now, that should be possible if you set "dev_nic_e1000 = off" in the your buildset ini file.
> 
> Cheers,
> 
> Jan
> 
>>
>> Thanks!
>> Karel
>> _______________________________________________
>> users mailing list
>> users at rtems.org
>> http://lists.rtems.org/mailman/listinfo/users

-------------- next part --------------
A non-text attachment was scrubbed...
Name: rtems-examples.diff
Type: text/x-patch
Size: 1337 bytes
Desc: not available
URL: <http://lists.rtems.org/pipermail/users/attachments/20200908/5fac3f46/attachment.bin>