Question regarding framebuffer driver.

[Vijay Kumar Banerjee]

On Sat, Aug 24, 2019 at 12:35 AM Aleksandr Rybalko <ray at ddteam.net> wrote:

> Hi Vijay!
>
> vt_fb driver is a simple consumer, it just use passed info about location
> of FrameBuffer in memory and its properties, like width/height/colors/etc.
> So if display keeps blank, you have to check correctness of passed data.
> Or maybe even writing  driver that prepare graphic subsystem to work with
> FB.
>
> Thanks.
>
> Hi Aleksandr,

Thanks for the reply, I checked the data and it was alright. The screen
wasn't even
turning on, I figured out that the problem was in pinmuxing. The problem is
now solved
when I ported the pinmux driver correctly.

Thanks and regards,
Vijay

> вт, 16 лип. 2019 о 15:22 Vijay Kumar Banerjee <vijaykumar9597 at gmail.com>
> пише:
>
>> Hello everyone,
>>
>> I'm working on porting the framebuffer driver to RTEMS with Beaglebone
>> Black as the target device. I have have already ported the am335x_lcd,
>> tda19988, fbd and VT drivers, but the screen doesn't seem to "power up".
>> From the FreeBSD bootlog (12-RELEASE), I see that the screen is
>> turning on after the VT initialization message, so I guess it's something
>> that happens after the vt initialization that turns the screen on.
>>
>> So far I have ported the vt_fb and vt_core and it boots up well with the
>> message :
>> VT: initialize with new VT driver "fb".
>>
>> But the screen doesn't seem to turn on. Can someone please tell me
>> or point me to the right place in code that is responsible for turning the
>> screen on after VT initialization?
>>
>> Thank you,
>> Vijay
>> _______________________________________________
>> freebsd-hackers at freebsd.org mailing list
>> https://lists.freebsd.org/mailman/listinfo/freebsd-hackers
>> To unsubscribe, send any mail to "freebsd-hackers-unsubscribe at freebsd.org
>> "
>>
>
>
> --
> WBW
> -------
> Rybalko Aleksandr <ray at ddteam.net>
>
>