From: Marcel Holtmann <marcel@holtmann.org>
To: Anthony Yulo <strikewing16th@hotmail.com>
Cc: BlueZ Mailing List <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] rfcomm error message?
Date: Wed, 21 Jan 2004 13:45:25 +0100 [thread overview]
Message-ID: <1074689125.7088.71.camel@pegasus> (raw)
In-Reply-To: <Law11-F41C9IHzQL9P30004988b@hotmail.com>
Hi Anthony,
> well, im just testing with the rfcomm program to see if i can connect to the
> linux box with a smartphone.. i didn't read the source of rfcomm that much,
> so im asking if i can still make a bluetooth program thru RFCOMM, without
> the TTY support?..
yes you can, but in that case you have to start with RFCOMM socket
programming. Look at rctest for an example.
> how do i set the kernel options CONFIG_BLUEZ_RFCOMM_TTY? The only way i know
> how to set it is thru recompiling the kernel.. i.e. "make xconfig"... other
> ways to do it?
The best way is to recompile and install the whole kernel, but
recompiling the RFCOMM module should also be enough.
Regards
Marcel
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-01-21 12:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-21 8:32 [Bluez-devel] rfcomm error message? Anthony Yulo
2004-01-21 12:45 ` Marcel Holtmann [this message]
[not found] ` <LAW11-OE47NCsn8BWz60002faea@hotmail.com>
2004-01-21 15:01 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2004-01-20 13:35 Anthony Yulo
2004-01-20 13:49 ` 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=1074689125.7088.71.camel@pegasus \
--to=marcel@holtmann.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=strikewing16th@hotmail.com \
/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