From owner-freebsd-current Wed Oct 3 5:12:13 2001 Delivered-To: freebsd-current@freebsd.org Received: from plab.ku.dk (plab.ku.dk [130.225.105.65]) by hub.freebsd.org (Postfix) with ESMTP id 0CCE437B405 for ; Wed, 3 Oct 2001 05:12:09 -0700 (PDT) Received: (from root@localhost) by plab.ku.dk (8.11.3/8.9.3) id f93CC2u19203 for freebsd-current@freebsd.org.AVP; Wed, 3 Oct 2001 14:12:02 +0200 (CEST) (envelope-from postmaster@plab.ku.dk) Received: from raven.plab.ku.dk (raven.plab.ku.dk [130.225.105.67]) by plab.ku.dk (8.11.3/8.9.3) with ESMTP id f93CC1v19195 for ; Wed, 3 Oct 2001 14:12:02 +0200 (CEST) (envelope-from postmaster@plab.ku.dk) Subject: /dev/cuaa broken ? Content-Transfer-Encoding: 8bit To: freebsd-current@freebsd.org From: Dmitry Karasik Keywords: 2001334874 Content-Type: text/plain; charset="koi8-r" Lines: 38 Mime-Version: 1.0 Date: 03 Oct 2001 14:12:57 +0200 X-Mailer: Mail::Mailer[v1.18] Net::SMTP[v2.13] Message-Id: Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG Hello! After upgrade to 3.5 to 4.3-stable we encoutered a problem with our custom device connected to com-port. The device accepts command strings and returns strings in response, but under 4.3 it strangely does not respond to commands that are longer than 15 bytes ( 16 with \r). The device is controlled by a code, which, if stripped to functional minimum is as such: open F, "+< /dev/cuaa0" or die "Cannot:$!\n"; system "/bin/stty -f /dev/cuaa0 gfmt1:ispeed=19200:ospeed=19200 cstopb"; print F "123\r"; # <- works under both 3.5 and 4.3 # print F "1234567890123456\r" # <- doesn't work under 4.3 print "|$_|\n" while ; close F; One more strange effect is, that under cu(1) it works. That makes us assume that the programming technique used into our program is inappropriate - but it seems pretty straightforward and we are just clueless about what implicit 16-byte buffers might be involved here. My suspicion is that it's the device driver bug, but unfortunately we cannot afford tracking the exact commit that caused the malfunction. Any help will be appreciated - change to the code, or to the kernel variables, or whatever. Please help. -- Sincerely, Dmitry --- www.karasik.eu.org --- Life ain't fair, but the root password helps. - BOFH To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message