From: Marcel Holtmann <marcel@holtmann.org>
To: Andy Ross <andy@plausible.org>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] RFCOMM bug?
Date: Wed, 18 Feb 2004 01:08:22 +0100 [thread overview]
Message-ID: <1077062902.2665.158.camel@pegasus> (raw)
In-Reply-To: <4032AA5C.3060505@plausible.org>
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
next prev parent reply other threads:[~2004-02-18 0:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-17 22:58 [Bluez-devel] RFCOMM bug? Andy Ross
2004-02-17 23:33 ` Marcel Holtmann
2004-02-17 23:57 ` Andy Ross
2004-02-18 0:08 ` Marcel Holtmann [this message]
2004-02-18 0:59 ` Andy Ross
2004-02-18 6:48 ` Marcel Holtmann
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1077062902.2665.158.camel@pegasus \
--to=marcel@holtmann.org \
--cc=andy@plausible.org \
--cc=bluez-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox