All of lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/minicom: make default port and lock directory config options
Date: Sat, 23 Nov 2019 13:34:24 +0100	[thread overview]
Message-ID: <87r21yydnz.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20191123110346.GT32494@scaer> (Yann E. MORIN's message of "Sat,  23 Nov 2019 12:03:46 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

 > James, All,
 > On 2019-11-21 15:30 +0000, James Byrne spake thusly:
 >> Minicom's configure script will set values for the default port and lock
 >> directory based on the configuration of the host machine, which is not
 >> useful for cross-compiling, so make them config options that can be set
 >> to suit the target system.

 > Thnks for this patch.

 > However I wonder if it makes sense to have those configurable at all.

My thought exactly.

 > The man page of minicom states, for the lock dir, that it default to
 > /var/lock on Linux ("GNU/Linux systems use /var/lock"), so we should
 > probably set that. The user can provide an override in a system-wide
 > config file (in /etc/minicom/).

 > Also, I think we should just set the default port (aka device in minicom
 > terminology) do /dev/ttyS1, as written in the man page ("/dev/tty1 or
 > /dev/ttyS1 for most people"). Ditto, users may override that with a
 > system-wide config file.

I wonder if ttyS0 wouldn't be a more sensible default. But ok, if you use
/dev/ttyS0 for the Linux console, then ttyS1 is probably indeed a good
default.

-- 
Bye, Peter Korsgaard

  reply	other threads:[~2019-11-23 12:34 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-21 15:30 [Buildroot] [PATCH 1/1] package/minicom: make default port and lock directory config options James Byrne
2019-11-21 17:35 ` Giulio Benetti
2019-11-23 11:03 ` Yann E. MORIN
2019-11-23 12:34   ` Peter Korsgaard [this message]
2019-11-26  9:52 ` [Buildroot] [PATCH v2] package/minicom: make default port and lock directory fixed defaults James Byrne
2019-11-26 11:54   ` Thomas Petazzoni
2019-12-03 13:46   ` Peter Korsgaard

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=87r21yydnz.fsf@dell.be.48ers.dk \
    --to=peter@korsgaard.com \
    --cc=buildroot@busybox.net \
    /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.