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 07:48:57 +0100 [thread overview]
Message-ID: <1077086937.2665.172.camel@pegasus> (raw)
In-Reply-To: <4032B8FB.8050309@plausible.org>
Hi Andy,
> I don't follow. The initialization state for a tty device is
> obviously set by the kernel, not an application. I'm simply saying
> that the kernel should initialize rfcomm devices to a state that
> matches RS232 devices, since that is what the user expects.
>
> It's just a principle of least surprise argument. I mean, the rfcomm module
> *could* do anything by default. But some choices make more sense than
> others.
the RFCOMM module inits the TTY the same as the serial driver does. You
can compare it by yourself. Look at drivers/serial/serial_core.c and at
net/bluetooth/rfcomm/tty.c and you will see that the init is the same.
If I missed anything I am happy to change 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
prev parent reply other threads:[~2004-02-18 6:48 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
2004-02-18 0:59 ` Andy Ross
2004-02-18 6:48 ` Marcel Holtmann [this message]
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=1077086937.2665.172.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.