![]() | |||||||||||
Messages in this thread |
Russell King wrote: > On Mon, Feb 26, 2007 at 12:02:57PM -0500, Rob Prowel wrote: > >> See below for a (script) dump of that demonstrates the behavior I >> describe. Additional ports are not configurable until a driver such as >> fourport is loaded. This is in 2.6.20.1 and 2.6.17 (those versions I >> have tested). >> > > Check what /proc/tty/driver/serial contains, rather than relying on > setserial. setserial distributed by distros hasn't kept up with the > changes in the serial layer. > > The setserial being used is the latest one from sourceforge. Its relevant output matches the /proc entries. The problem still remains though. Entries for ttyS4 and up seem to be read-only until I add a supplemental driver such as fourport. - 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: 2007-02-27 15:27 [from the cache] ©2003-2008 | |||||||||||