Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 26 Dec 2013 20:37:59 -0800
From:      Oleksandr Tymoshenko <gonzo@bluezbox.com>
To:        Tim Kientzle <tim@kientzle.com>
Cc:        "freebsd-arm@freebsd.org" <freebsd-arm@freebsd.org>
Subject:   Re: HDMI output on Beaglebone black
Message-ID:  <968F55AA-34DA-4245-B8C1-A3C0E365FF11@bluezbox.com>
In-Reply-To: <FB96D3DB-3DC2-4D5F-B83F-CF294F69F93D@kientzle.com>
References:  <CAASDrVnu-0vJsnnp-rEQAT6dkg3eyNcjTejYzwwaKDpfkzFXdw@mail.gmail.com> <7C58B233-1E84-47A3-ABB2-0038928BB1B2@bluezbox.com> <FB96D3DB-3DC2-4D5F-B83F-CF294F69F93D@kientzle.com>

next in thread | previous in thread | raw e-mail | index | archive | help

On 2013-12-26, at 6:52 PM, Tim Kientzle <tim@kientzle.com> wrote:

>=20
> On Dec 26, 2013, at 1:18 PM, Oleksandr Tymoshenko <gonzo@bluezbox.com> =
wrote:
>=20
>>=20
>> On 2013-12-25, at 9:08 PM, "Lundberg, Johannes" =
<johannes@brilliantservice.co.jp> wrote:
>>=20
>>> Hi
>>>=20
>>> According to the readme for Beaglebone Black in crochet-freebsd =
there is no
>>> support for HMDI output yet (as of Dec 2013).
>>>=20
>>> Does anyone know what is required to make this work?
>>=20
>> You need to write driver for NXP TDA19988 HDMI (LCD to HDMI =
converter), driver=20
>> for LCD controller and vt/syscons wrapper. Also properly pinmux LCD =
pins in .dts.
>=20
> Does newcons make this any simpler?

Hardware part - no. vt/syscons - probably. At least I think so, I =
haven't caught up to the=20
latest stuff yet but AFAIR whole point of newcons was to make =
console/framebuffer=20
drivers more sane.=20=



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?968F55AA-34DA-4245-B8C1-A3C0E365FF11>