[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <278afb05-8c8d-98d2-eed0-f73b954b03c7@gmail.com>
Date: Wed, 30 Sep 2020 19:36:19 -0700
From: Florian Fainelli <f.fainelli@...il.com>
To: Scott Branden <scott.branden@...adcom.com>,
Arnd Bergmann <arnd@...db.de>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Olof Johansson <olof@...om.net>
Cc: Kees Cook <keescook@...omium.org>, linux-kernel@...r.kernel.org,
bcm-kernel-feedback-list@...adcom.com
Subject: Re: [PATCH v5 15/15] misc: bcm-vk: add ttyVK support
On 9/30/2020 6:28 PM, Scott Branden wrote:
> Add ttyVK support to driver to allow console access to VK card from host.
>
> Device node will be in the follow form /dev/bcm-vk.x_ttyVKy where:
> x is the instance of the VK card
> y is the tty device number on the VK card
>
> Signed-off-by: Scott Branden <scott.branden@...adcom.com>
Was it not possible to:
- emulate a standard 8250 UART and just expose an additional bar + MSI
vector such that one could get a debug UART out of this device with
little to no work on the host side?
- or use virtio console and implement virtio on the firmware that runs
on VK?
It's not a lot of code, but it just feels like this should not have to
be done at all.
--
Florian
Powered by blists - more mailing lists