![]() | ||||||||||
Messages in this thread |
Andrew Morton writes: > Richard Gooch wrote: > > > > Andrew Morton writes: > > > Richard Gooch wrote: > > > > > > > > > Instead, it appears that someone broke tty_name(). Here's the > > > > > 2.2 kernel's version: > > > > > > > > That "someone" was me, and I changed it from broken to fixed. > > > > > > > > > > Look at serial.c: > > > > > > #if (LINUX_VERSION_CODE > 0x2032D && defined(CONFIG_DEVFS_FS)) > > > serial_driver.name = "tts/%d"; > > > #else > > > serial_driver.name = "ttyS"; > > > #endif > > > > > > tty_name will just print "ttyS". So the transition for this case > > > was fixed->broken. > > > > 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. Regards, Richard.... Permanent: rgooch@atnf.csiro.au Current: rgooch@ras.ucalgary.ca - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | |||||||||
| Last update: 2005-03-22 11:15 [from the cache] ©2003-2008 | ||||||||||