All of lore.kernel.org
 help / color / mirror / Atom feed
From: Joel Stanley <joel@jms.id.au>
To: "Alexander A. Filippov" <a.filippov@yadro.com>,
	Eddie James <eajames@linux.ibm.com>,
	 Brad Bishop <bradleyb@fuzziesquirrel.com>
Cc: OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: IKVM on AST2400
Date: Mon, 27 May 2019 03:10:26 +0000	[thread overview]
Message-ID: <CACPK8XeXzDE6tsfE7X0qX5E9R2WPCqFT6OuAktNVy4uQxB0jEw@mail.gmail.com> (raw)
In-Reply-To: <20190524120328.GA648@bbwork.lan>

Hi Alexander,

On Fri, 24 May 2019 at 12:03, Alexander A. Filippov
<a.filippov@yadro.com> wrote:
>
> Some time ago the obmc-ikvm service was added to the firmware. It causes some
> problems on our VESNIN hardware. As it based on AST2400 it does not have support
> for IKVM in the DTS. The system log contains messages that create_usbhid.sh is
> unable to find some items in the sysfs and then obmc-ikvm service crashes. It
> causes fail in QEMU_CI test.
>
> I belive that this issue also present on other platforms based on AST2400.
>
> IBM Guys: Do you run tests for Palmetto?
> Is there anybody else who uses AST2400?

I am not sure that anyone has tested it on ast2400. If it works, we
can enable it for palmetto.

>
> Well, my proposal is to make the IKVM support optional by moving it to the
> distrofeature.
>
> Besides, I've solved these problems for our hardware by adding required kernel
> modules and modifying DTS.
> IKVM works, but bring a lot of warnings after the host was shut down while the
> VNC-client is still connected.
>
> During the solving I copied some records from aspeed-g5.dtsi to aspeed-g4.dtsi.
> Should I commit these changes to Torvalds or OpenBMC repo?

Send them to mainline (Torvalds).

Thanks,

Joel

  reply	other threads:[~2019-05-27  3:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-05-24 12:03 IKVM on AST2400 Alexander A. Filippov
2019-05-27  3:10 ` Joel Stanley [this message]
2019-05-27  8:19 Wim Vervoorn
2019-05-27 12:40 ` Alexander A. Filippov
2019-05-28 15:33   ` Eddie James
2019-05-29 12:09     ` Wim Vervoorn
2019-05-29 13:14       ` Eddie James

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CACPK8XeXzDE6tsfE7X0qX5E9R2WPCqFT6OuAktNVy4uQxB0jEw@mail.gmail.com \
    --to=joel@jms.id.au \
    --cc=a.filippov@yadro.com \
    --cc=bradleyb@fuzziesquirrel.com \
    --cc=eajames@linux.ibm.com \
    --cc=openbmc@lists.ozlabs.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.