From owner-freebsd-arm@freebsd.org Sat Jul 20 05:54:40 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 9E94EB5836 for ; Sat, 20 Jul 2019 05:54:40 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from mail.myserver.ws (mail.myserver.ws [144.217.111.45]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mail.myserver.ws", Issuer "Let's Encrypt Authority X3" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id AC2846E677 for ; Sat, 20 Jul 2019 05:54:39 +0000 (UTC) (envelope-from sm@ara-ler.com) Received: from dendrobates (c-73-153-76-61.hsd1.co.comcast.net [73.153.76.61]) (Authenticated sender: sm@ara-ler.com) by mail.myserver.ws (Postfix) with ESMTPSA id 2C168AAC6E; Sat, 20 Jul 2019 05:54:30 +0000 (UTC) Date: Fri, 19 Jul 2019 23:54:21 -0600 From: Sergey Manucharian To: Oleksandr Tymoshenko Cc: Vijay Kumar Banerjee , freebsd-arm@freebsd.org Subject: Re: Question regarding framebuffer driver. Message-ID: <20190720055421.GB41013@dendrobates> References: <20190720024214.GA56812@bluezbox.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20190720024214.GA56812@bluezbox.com> User-Agent: Mutt/1.11.4 (2019-03-13) X-Rspamd-Queue-Id: AC2846E677 X-Spamd-Bar: - Authentication-Results: mx1.freebsd.org; spf=pass (mx1.freebsd.org: domain of sm@ara-ler.com designates 144.217.111.45 as permitted sender) smtp.mailfrom=sm@ara-ler.com X-Spamd-Result: default: False [-1.06 / 15.00]; RCVD_VIA_SMTP_AUTH(0.00)[]; TO_DN_SOME(0.00)[]; R_SPF_ALLOW(-0.20)[+a:mail.myserver.ws]; MX_GOOD(-0.01)[mail.myserver.ws]; RECEIVED_SPAMHAUS_PBL(0.00)[61.76.153.73.zen.spamhaus.org : 127.0.0.10]; R_DKIM_NA(0.00)[]; MIME_TRACE(0.00)[0:+]; ASN(0.00)[asn:16276, ipnet:144.217.0.0/16, country:FR]; IP_SCORE(0.06)[ipnet: 144.217.0.0/16(-0.85), asn: 16276(1.17), country: FR(-0.01)]; FROM_EQ_ENVFROM(0.00)[]; ARC_NA(0.00)[]; NEURAL_HAM_MEDIUM(-0.76)[-0.764,0]; FROM_HAS_DN(0.00)[]; RCPT_COUNT_THREE(0.00)[3]; NEURAL_SPAM_SHORT(0.41)[0.415,0]; NEURAL_HAM_LONG(-0.97)[-0.966,0]; MIME_GOOD(-0.10)[text/plain]; DMARC_NA(0.00)[ara-ler.com]; TO_MATCH_ENVRCPT_SOME(0.00)[]; MID_RHS_NOT_FQDN(0.50)[]; FREEMAIL_CC(0.00)[gmail.com]; RCVD_COUNT_TWO(0.00)[2]; RCVD_TLS_ALL(0.00)[] 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 05:54:40 -0000 Vijay Kumar Banerjee (vijaykumar9597@gmail.com) wrote: > > >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. What kind of screen? If it's not HDMI, but directly connected LCD, "turn on" has two different meaning: one is the screen's backlight, another is the actual text/image drawn on the screen. So, even if your screen is black, do you see the backlight? Usually the backlight is controlled by PWM signal, if the backlight is off, the corresponding pin is not configured properly. Instead of PWM you can configure it just as output with high value to check. Excerpts from Oleksandr Tymoshenko's message from Fri 19-Jul-19 19:42: > 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. I confirm it works with Newhaven 7" LCD cape as well. (Except touchpanel, which is completely different story). -S.