From: Paul Fertser <fercerpav@gmail.com>
To: Konstantin Klubnichkin <kitsok@yandex-team.ru>
Cc: "openbmc@lists.ozlabs.org" <openbmc@lists.ozlabs.org>
Subject: Re: Serial Over Lan (SOL) no login prompt on Linux IRQ mode
Date: Tue, 27 Jul 2021 12:30:15 +0300 [thread overview]
Message-ID: <20210727093015.GQ875@home.paul.comp> (raw)
In-Reply-To: <477521627375667@mail.yandex-team.ru>
On Tue, Jul 27, 2021 at 11:53:57AM +0300, Konstantin Klubnichkin wrote:
> SIRQ polarity is something I didn't try, will do it. And yes, SIRQ bit is zero,
> but all other bits are also zero in that register, that confuses me.
I was also able to manually export the SIRQ pin via sysfs and when
manually toggling it the host was seeing UART interrupts and getting
data to and from VUART. That lead nowhere though, so we resorted to
hardware routing in ast2500 between "real UARTs".
> Instead I configure UART routing by direct writing to registers via /dev/mem
> (yes, I know that it's a bad practive, but it's development).
Should work the same.
> With the routing I have absolutely no data in BMC UARTs neither during POST nor
> is OS.
> What I'm missing is how that routing works. Is it on-crystal or UART need to be
> routed to SoC pins thus TX/RX are connected via pins?
With the configuration as shown the host is sending data to and from
"COM1" (0x3f8,4) and any program on BMC is able to interact with it
via /dev/ttyS2, without any additional hardware connections, all
purely in software, the routing happens inside aspeed. Do not forget
to enable ttyS2 in your board's DTS. VUART is not involved at all.
--
Be free, use free (http://www.gnu.org/philosophy/free-sw.html) software!
mailto:fercerpav@gmail.com
next prev parent reply other threads:[~2021-07-27 9:31 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-27 6:54 Serial Over Lan (SOL) no login prompt on Linux IRQ mode AKASH G J
2019-12-27 7:33 ` Yong Li
2019-12-30 0:02 ` AKASH G J
2021-07-26 14:36 ` Konstantin Klubnichkin
2021-07-26 14:52 ` Paul Fertser
2021-07-26 16:42 ` Konstantin Klubnichkin
2021-07-26 16:51 ` Paul Fertser
2021-07-27 8:53 ` Konstantin Klubnichkin
2021-07-27 9:30 ` Paul Fertser [this message]
2021-11-24 20:33 ` Oskar Senft
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=20210727093015.GQ875@home.paul.comp \
--to=fercerpav@gmail.com \
--cc=kitsok@yandex-team.ru \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).