From: Russell King [mailto:[EMAIL PROTECTED] > After experimenting here, it turns out the reason is you're trying to > configure a port with a zero base baud. Unfortunately, it starts off > as zero.
That explains why adding the fourport module fixed Rob's issue, as the fourport code sets a uartclk value for its ports. > However, when you try to change a port without specifying the > base baud, > it is possible for the port to become "usable" and unless we enforce > the "must not have zero base baud" rule we have the > possibility to oops > the kernel via a divide by zero. > > So, the answer is to specify the base baud when using setserial to > configure new ports. Would it be more intuitive to give ports the default uartclk of 1843200 at init time? That would avoid this issue, but would make the baud rates come out wrong on hardware with a non-standard clock, if a base baud wasn't specified. From: Rob Prowel [mailto:[EMAIL PROTECTED] > your website address didn't work when I tried it... The website may have been down on the weekend for maintenance. Please try again. ..Stu -- We make multiport serial products. http://www.connecttech.com/ (800) 426-8979 - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
