Folks, it had been quite a few years since callout tty devices had
been deprecated. IMO it's time to bury them - the following
if ((tty->driver.type == TTY_DRIVER_TYPE_SERIAL) &&
(tty->driver.subtype == SERIAL_TYPE_CALLOUT)) {
printk("Warning, %s opened, is a deprecated tty "
"callout device\n", tty_name(tty, buf));
in tty_open() had been theres since 2.1.90-pre2. IOW, we had two stable
branches since then.
Quite a few things in tty code and related data structures exist only
because of these beasts and I'd rather get rid of them.
If nobody has serious objections I'll submit patches removing that stuff,
so if you _do_ have a reason to keep callouts around, yell now.
[email protected] wrote:
>
> if ((tty->driver.type == TTY_DRIVER_TYPE_SERIAL) &&
> (tty->driver.subtype == SERIAL_TYPE_CALLOUT)) {
> printk("Warning, %s opened, is a deprecated tty "
> "callout device\n", tty_name(tty, buf));
google says that one person hit this in 1998. That's it.
The current message is
printk(KERN_WARNING "tty_io.c: "
"process %d (%s) used obsolete /dev/%s - "
"update software to use /dev/ttyS%d\n",
and google("update software to use") == 201, spread across 1999-2001.
Kill it.
On Mon, May 12, 2003 at 11:44:15PM -0700, Andrew Morton wrote:
...
> The current message is
> printk(KERN_WARNING "tty_io.c: "
> "process %d (%s) used obsolete /dev/%s - "
> "update software to use /dev/ttyS%d\n",
> and google("update software to use") == 201, spread across 1999-2001.
Even I have hit that, groaned, reconfigured things, and never
had trouble about it since. Certainly didn't bother to write
to any list.
For certain people will encounter configurations that use very
old userspace things with new kernels. After all, kernels are
easier to change than doing full re-install.
> Kill it.
I might instead add a bit of text: "obsolete (since Year-Month) /dev/..."
/Matti Aarnio