I'm working on a small app that talks to a device with a FTDI USB to 232 chip in it. ucom and uftdi seem to detect it just fine. But calls to read() hang and I'm getting messages like "putc to a clist with no reserved cblocks" in my kernel logs. Any idea what this is? In a previous post (subject: ucom and sio) I asked about a similar problem with read() hanging on prolific chips. The fix involved ignoring modem control lines with CLOCAL, but that doesn't appear to do the trick here. Oddly, the exact same software/hardware works fine on my powerbook. What am I missing? I can send code if its needed. Thanks
On Mon, 28 Feb 2005 11:14, Brandon Fosdick wrote:> I'm working on a small app that talks to a device with a FTDI USB to 232 > chip in it. ucom and uftdi seem to detect it just fine. But calls to read() > hang and I'm getting messages like "putc to a clist with no reserved > cblocks" in my kernel logs. Any idea what this is?What version of FreeBSD? -- Daniel O'Connor software and network engineer for Genesis Software - http://www.gsoft.com.au "The nice thing about standards is that there are so many of them to choose from." -- Andrew Tanenbaum GPG Fingerprint - 5596 B766 97C0 0E94 4347 295E E593 DC20 7B3F CE8C -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 187 bytes Desc: not available Url : http://lists.freebsd.org/pipermail/freebsd-stable/attachments/20050228/6630a65a/attachment-0001.bin