From owner-freebsd-arm@freebsd.org Sat Jul 20 02:42:23 2019 Return-Path: Delivered-To: freebsd-arm@mailman.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mailman.nyi.freebsd.org (Postfix) with ESMTP id EA518B25A5 for ; Sat, 20 Jul 2019 02:42:23 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from id.bluezbox.com (id.bluezbox.com [45.55.20.155]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id F281169C4B for ; Sat, 20 Jul 2019 02:42:22 +0000 (UTC) (envelope-from gonzo@bluezbox.com) Received: from localhost ([127.0.0.1] helo=id.bluezbox.com) by id.bluezbox.com with esmtps (TLSv1.2:ECDHE-RSA-AES256-GCM-SHA384:256) (Exim 4.92 (FreeBSD)) (envelope-from ) id 1hofKA-000Eox-Om; Fri, 19 Jul 2019 19:42:16 -0700 Received: (from gonzo@localhost) by id.bluezbox.com (8.15.2/8.15.2/Submit) id x6K2gEC7056974; Fri, 19 Jul 2019 19:42:14 -0700 (PDT) (envelope-from gonzo@bluezbox.com) X-Authentication-Warning: id.bluezbox.com: gonzo set sender to gonzo@bluezbox.com using -f Date: Fri, 19 Jul 2019 19:42:14 -0700 From: Oleksandr Tymoshenko To: Vijay Kumar Banerjee Cc: freebsd-arm@freebsd.org Subject: Re: Question regarding framebuffer driver. Message-ID: <20190720024214.GA56812@bluezbox.com> References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Operating-System: FreeBSD/11.2-RELEASE-p10 (amd64) User-Agent: Mutt/1.11.4 (2019-03-13) X-Spam-Level: -- X-Spam-Report: Spam detection software, running on the system "id.bluezbox.com", has NOT identified this incoming email as spam. The original message has been attached to this so you can view it or label similar future email. If you have any questions, see The administrator of that system for details. Content preview: Vijay Kumar Banerjee (vijaykumar9597@gmail.com) wrote: > Hello everyone, > > I'm working on porting the framebuffer driver to RTEMS with Beaglebone > Black as the target device. I have have already po [...] Content analysis details: (-2.9 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -1.0 ALL_TRUSTED Passed through trusted hosts only via SMTP -1.9 BAYES_00 BODY: Bayes spam probability is 0 to 1% [score: 0.0000] X-Rspamd-Queue-Id: F281169C4B X-Spamd-Bar: ----- Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of gonzo@bluezbox.com designates 45.55.20.155 as permitted sender) smtp.mailfrom=gonzo@bluezbox.com X-Spamd-Result: default: False [-5.59 / 15.00]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-1.00)[-1.000,0]; FROM_HAS_DN(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+mx]; NEURAL_HAM_LONG(-1.00)[-1.000,0]; MIME_GOOD(-0.10)[text/plain]; HAS_XAW(0.00)[]; DMARC_NA(0.00)[bluezbox.com]; RCVD_COUNT_THREE(0.00)[3]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MX_GOOD(-0.01)[mx.bluezbox.com]; RCPT_COUNT_TWO(0.00)[2]; NEURAL_HAM_SHORT(-0.98)[-0.978,0]; RCVD_TLS_LAST(0.00)[]; FREEMAIL_TO(0.00)[gmail.com]; FROM_EQ_ENVFROM(0.00)[]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:14061, ipnet:45.55.0.0/19, country:US]; MID_RHS_MATCH_FROM(0.00)[]; IP_SCORE(-2.30)[ip: (-8.34), ipnet: 45.55.0.0/19(-4.17), asn: 14061(1.07), country: US(-0.05)] X-BeenThere: freebsd-arm@freebsd.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: "Porting FreeBSD to ARM processors." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 20 Jul 2019 02:42:24 -0000 Vijay Kumar Banerjee (vijaykumar9597@gmail.com) wrote: > 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 the code that is responsible for turning > the > screen on after VT initialization? Hi Vijay, Because the code is ported to another OS there are too many ways things can go wrong. The problem can be in VT, in am335x_lcd or in TDA driver so it's hard to pinpoint exact location. If I was to debug such problem I'd try to isolate each driver and make sure it works on its own. I think the easiest way is to get LCD screen that connects directly to AM335x, without HDMI framer and try to initialize framebuffer in am335x_lcd driver with certain pattern to make sure it works. FreeBSD driver worked with 4DCAPE [1] at some point, so it might be a good start. Once you make sure am335x_lcd driver works, you can verify TDA driver with some hardcoded logic that doesn't require VT layer and once both are known to work - it's only VT layer to debug. [1] https://4dsystems.com.au/gen4-4dcape-43t -- gonzo