Re: Serial Driver Name Question (kernels 2.4.x)

[Andrew Morton]

Richard Gooch wrote:
> 
> > > Why exactly is just "ttyS" broken?
> >
> > umm..  Because it doesn't tell the user which serial port the
> > message pertains to?
> 
> Exactly where is it broken? I look at my dmesg output and things look
> fine.
> 

Try disabling devfs.

At the head-of-thread, Ivan said:

> This was spotted by a Cyclades customer who was getting overrun msgs
> as:
> 
> ttyC: 1 input overrun(s)
> 
> After he changed the driver.name to be "ttyC%d", he started to get
> properly formatted msgs, such as:
> 
> ttyC39: 1 input overrun(s)
> 
> This problem would happen on any msg that used the function
> tty_name() to get the TTY name, and after the change the problem
> disappeared completely.

-