From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
Cc: linux-serial@vger.kernel.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Donald Buczek <buczek@molgen.mpg.de>
Subject: Re: Device to write to all (serial) consoles
Date: Fri, 2 Aug 2019 21:59:06 +0200 [thread overview]
Message-ID: <cab1fe06-0dc7-e7c1-50ac-cc01773c5ef5@molgen.mpg.de> (raw)
In-Reply-To: <20190802160243.GA15484@kroah.com>
Dear Greg,
On 02.08.19 18:02, Greg Kroah-Hartman wrote:
> On Fri, Aug 02, 2019 at 03:23:08PM +0200, Paul Menzel wrote:
>> On a lot of devices, like servers, you have more than one serial console,
>> and you do not always know, how they are numbered. Therefore, we start a
>> console on ttyS0 and ttyS1.
>>
>> In user space, we also would like to write to both consoles to not worry
>> about the numbering. Writing to `/dev/console` only write to the active
>> console.
>
> So the same data to multiple console devices with just one userspace
> call? Why?
Because the cable is always connected to the port on the back side, and
sometimes the port in the front has ID 0, and the one in the back 1, and
other times vice versa. We do not want to track that, and it would be
convenient to just write to both ports.
>> $ more /proc/consoles # I think
>> tty0 -WU (EC p ) 4:1
>> ttyS0 -W- (E p a) 4:65
>> ttyS1 -W- (E p a) 4:65
>>
>> Does a device exist, or can a device be configured so you can write to
>> all (serial) consoles from user space?
>
> With one syscall, not that I know of, sorry.
Can such a device be created with udev or so?
Kind regards,
Paul
next prev parent reply other threads:[~2019-08-02 19:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-02 13:23 Paul Menzel
2019-08-02 16:02 ` Greg Kroah-Hartman
2019-08-02 19:59 ` Paul Menzel [this message]
2019-08-03 6:46 ` Greg Kroah-Hartman
2019-08-03 13:23 ` Adam Borowski
2019-08-03 13:55 ` Greg Kroah-Hartman
2019-08-03 15:15 ` Adam Borowski
2019-08-08 14:52 ` Enrico Weigelt, metux IT consult
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=cab1fe06-0dc7-e7c1-50ac-cc01773c5ef5@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=buczek@molgen.mpg.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-serial@vger.kernel.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
all inboxes | Powered by JetHome®