From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Subject: Re: [Bluez-devel] RFCOMM bug? From: Marcel Holtmann To: Andy Ross Cc: BlueZ Mailing List In-Reply-To: <4032AA5C.3060505@plausible.org> References: <40329CA6.7080302@mdolabs.com> <1077060827.2665.137.camel@pegasus> <4032AA5C.3060505@plausible.org> Content-Type: text/plain Message-Id: <1077062902.2665.158.camel@pegasus> Mime-Version: 1.0 Sender: bluez-devel-admin@lists.sourceforge.net Errors-To: bluez-devel-admin@lists.sourceforge.net List-Unsubscribe: , List-Id: List-Post: List-Help: List-Subscribe: , List-Archive: Date: Wed, 18 Feb 2004 01:08:22 +0100 Hi Andy, > Duh, dunno why I didn't try that. A simple stty -cooked indeed fixes > the problem. > > That said: isn't this still a bug? Serial ports don't behave this way > by default, and an rfcomm device is supposed to look like an RS232 > device. Certainly a hardware tty *can* be made to echo to the remote > device, but that's the job of programs like getty to set up properly. > Something seems backwards here, is there a reason for making > /dev/rfcomm* work differently from /dev/ttyS*? the question is what should be default? This is application specific and so the kernel can't (and shouldn't) do anything about it. Regards Marcel ------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ Bluez-devel mailing list Bluez-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/bluez-devel