From: Tom Rini <trini@konsulko.com>
To: u-boot@lists.denx.de
Subject: Switching among serial consoles
Date: Fri, 20 Mar 2020 14:26:33 -0400 [thread overview]
Message-ID: <20200320182633.GE5793@bill-the-cat> (raw)
In-Reply-To: <da095208-37b3-b117-ccf8-e1396399ad5a@xilinx.com>
On Wed, Mar 18, 2020 at 09:48:36AM +0100, Michal Simek wrote:
> Hi,
>
> long time ago I was playing with switching among consoles.
> I have two IPs with the same driver where main console is probed and
> used which is visible via dm tree.
>
> serial 1 [ + ] serial_zynq | |-- serial at ff000000
> serial 2 [ ] serial_zynq | |-- serial at ff010000
>
> then I have also dcc which can be also used as a console
>
> serial 0 [ ] arm_dcc |-- dcc
>
> Lastly I have enabled netconsole feature.
>
> I have no problem to switch between serial at ff000000 and nc but I can't
> switch it to dcc or second instance.
>
> dhcp
> setenv ncip 192.168.0.105
> setenv nc 'setenv stdout nc;setenv stdin nc'
> setenv dcc 'setenv stdout dcc;setenv stdin dcc'
> setenv serial0 'setenv stdout serial at ff000000;setenv stdin serial at ff000000'
> setenv serial1 'setenv stdout serial at ff010000;setenv stdin serial at ff010000'
> run nc
>
> and then via netconsole
>
> run serial0
>
> works to get back.
>
>
> Console info is showing only available and registered instances.
>
> ZynqMP> con
> List of available devices:
> serial at ff000000 00000007 IO
> serial 00000003 IO stdin stdout stderr
> nulldev 00000003 IO
> nc 00000003 IO
>
> It means the question is how to probe second instance of serial_zynq
> serial at ff010000 and dcc. I expect when probe is done it will show up in
> console list and switch is possible.
>
> I found SERIAL_SEARCH_ALL symbol but it is just search not probe.
>
> I am quite sure that it was working in past but not sure if this was
> before DM but I would like to know how you are doing it/testing it today.
I think the answer is we don't have any tests for multiple consoles to
start with, so it's not tested. I'd start by grabbing an old platform
and bisect'ing back the years to see when it did last work as the first
thing. Sorry!
--
Tom
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 659 bytes
Desc: not available
URL: <https://lists.denx.de/pipermail/u-boot/attachments/20200320/b5ba9701/attachment.sig>
next prev parent reply other threads:[~2020-03-20 18:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-18 8:48 Switching among serial consoles Michal Simek
2020-03-20 18:26 ` Tom Rini [this message]
2020-03-23 15:36 ` Simon Glass
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=20200320182633.GE5793@bill-the-cat \
--to=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
/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