Why doesn't ppc(4) check non-ENXIO failures during probe?

2010-08-15 Thread Garrett Cooper
One thing that's puzzling me about the ppc(4) driver's ISA routines is that it only checks to see whether or not the device has an IO error: (from sys/dev/ppc/ppc_isa.c) @@ -121,8 +121,8 @@ parent = device_get_parent(dev); error = ISA_PNP_PROBE(parent, dev, lpc_ids);

Re: Problem detecting and reacting to serial break

2010-08-15 Thread Paul Thornton
Paul Thornton wrote: > Ed Schouten wrote: >> * Paul Thornton wrote: >>> I'm using 8.0-RELEASE with uftdi and ucom driving the serial port. >> Somewhat unrelated question: have you ever tried running the this code >> on 7.x? If so, did it work? > > I've just tried this on 7.2-RELEASE (that was the

Re: Problem detecting and reacting to serial break

2010-08-15 Thread Daniel O'Connor
On 15/08/2010, at 23:25, Paul Thornton wrote: > With Linux, it all works as expected - but the linux tcsetattr doesn't > like the nonstandard baud rate either. However, in linux I used > setserial to set a base baud rate of 2400 and a divisor of 96 to get > 250k baud rate. When I run, I have

mount(2) not returning EINVAL with invalid filesystems

2010-08-15 Thread Garrett Cooper
mount(2) says it should fail with EINVAL if the magic block is wrong: [EINVAL] The super block for the file system had a bad magic number or an out of range block size. This doesn't appear to be the case with a nmount layer though :/. I didn't find a