From: Marc Karasek
To: 'Richard B. Johnson '
Sent: 4/19/01 11:53 AM
Subject: RE: Bug in serial.c
Did something change between 2.4.2 & 2.4.3? Under 2.4.2 I did not have
to init the terminal (are you refering to the host or client side?) and
just accepted the defaults (9600, 8n1) which was fine for debug and
My issue is with 2.4.2 it works with 2.4.3 (same .config) it does not.
So in my mind this is a bug of some type..... :-)
Which kernel are you using in your embedded project??
From: Richard B. Johnson
To: Marc Karasek
Sent: 4/19/01 11:43 AM
Subject: Re: Bug in serial.c
On Thu, 19 Apr 2001, Marc Karasek wrote:
> I am doing some embedded development with the 2.4.x series and have
> a few things..
> 2) In 2.4.3 the console port using ttySX is broken. It dumps fine to
> terminal but when you get to a point of entering data (login,
> scripts, etc) the terminal does not accept any input.
It is not broken. It is used all the while in our embeded systems.
> So far I have been able to debug to the point where I see that the
> receiving the characters from the serial.c driver. But it never echos
> or does anything else with them. I will continue to look into this at
Did you ever initialize the terminal? And I'm not talking about
There is a termios structure of information necessary to configure a
terminal for I/O.
> I was also wondering if anyone else has seen this or if a patch is
> this bug??
You refer to a BUG? There isn't any of the kind you describe.
Penguin : Linux version 2.4.1 on an i686 machine (799.53 BogoMips).
"Memory is like gasoline. You use it up when you are running. Of
course you get it all back when you reboot..."; Actual explanation
obtained from the Micro$oft help desk.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/