From: ebiederm@xmission.com (Eric W. Biederman)
To: Fabrice Gautier <gautier@email.enst.fr>
Cc: Linux Kernel Mailinglist <linux-kernel@vger.kernel.org>
Subject: Re: serial console problems with 2.4.4
Date: 03 May 2001 02:15:03 -0600 [thread overview]
Message-ID: <m166fiq260.fsf@frodo.biederman.org> (raw)
In-Reply-To: <20010502130958.38BB.GAUTIER@email.enst.fr> <m1elu7pv0e.fsf@frodo.biederman.org> <20010502201026.CB69.GAUTIER@email.enst.fr>
In-Reply-To: Fabrice Gautier's message of "Wed, 02 May 2001 20:52:36 +0200"
Fabrice Gautier <gautier@email.enst.fr> writes:
> On 02 May 2001 10:37:21 -0600
> ebiederm@xmission.com (Eric W. Biederman) wrote:
>
> > Fabrice Gautier <gautier@email.enst.fr> writes:
> > > So this this probably a sulogin/mingetty problem. They should set the
> > > CREAD flag in your tty c_cflag.
> > >
> > > the patch for busybox repalced the line
> > > tty.c_cflag |= HUPCL|CLOCAL
> > > by
> > > tty.c_cflag |= CREAD|HUPCL|CLOCAL
> > >
> > > Hope this help.
> >
> > This part is correct.
> >
> > However the kernel sets CREAD by default.
>
> Are your sure? Wasn't this the behaviour for 2.4.2 but changed in 2.4.3
init=/bin/bash works fine over a serial console in 2.4.4. So I am
certain.
I get the impression that something in 2.4.3 fixed CREAD handling, and we
started noticing the buggy user space.
> > sysvinit (and possibly other inits) clears CREAD.
>
> In my case I was using busybox as init. So there is no sysinit or any other
> init called before this line.
The busy box init is also clearing CREAD (as of 0.51 anyway).
> > I wish I knew where the breakage actually occured.
>
> Just look at this diff on serial.c between 2.4.2 and 2.4.3:
If it was a real diff between 2.4.2 and 2.4.3 I would agree, however it looks
like your attempt to fix 2.4.3.
Eric
> --- serial.c Sat Apr 21 17:22:53 2001
> +++ ../../../linux-2.4.2/drivers/char/serial.c Sat Feb 17 01:02:36 2001
> @@ -1764,8 +1765,8 @@
> /*
> * !!! ignore all characters if CREAD is not set
> */
> -// if ((cflag & CREAD) == 0)
> -// info->ignore_status_mask |= UART_LSR_DR;
> + if ((cflag & CREAD) == 0)
> + info->ignore_status_mask |= UART_LSR_DR;
> save_flags(flags); cli();
> if (uart_config[info->state->type].flags & UART_STARTECH) {
> serial_outp(info, UART_LCR, 0xBF);
>
next prev parent reply other threads:[~2001-05-03 8:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-05-02 9:54 Reto Baettig
2001-05-02 11:15 ` Fabrice Gautier
2001-05-02 16:37 ` Eric W. Biederman
2001-05-02 18:52 ` Fabrice Gautier
2001-05-03 8:15 ` Eric W. Biederman [this message]
2001-05-03 12:30 ` Fabrice Gautier
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=m166fiq260.fsf@frodo.biederman.org \
--to=ebiederm@xmission.com \
--cc=gautier@email.enst.fr \
--cc=linux-kernel@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®