Linux bluetooth development
 help / color / mirror / Atom feed
From: "Mark S. Townsley" <mstownsley@gmail.com>
To: "BlueZ users" <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] minicom over /dev/rfcomm0
Date: Tue, 19 Dec 2006 12:26:32 -0800	[thread overview]
Message-ID: <be976db60612191226p7c4660a7q45d173717c81d634@mail.gmail.com> (raw)
In-Reply-To: <E34033EC-19D4-4112-A964-C656CA724290@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1798 bytes --]

Hi Bas:  thanks for your reply.

So are you implying that if I do not go through RFCOMM and all the sockets
stuff, I can
actually open /dev/rfcomm0 and get back a file descriptor just like any
other serial port?

Thanks

Mark


On 12/19/06, Bas Schulte <basschulte@gmail.com> wrote:
>
> Hi,
>
> On 19-dec-2006, at 20:23, Mark S. Townsley wrote:
>
> > In many examples that I found online where people are trying to
> > make their cellphone surf web or somehow talk to their cellphone
> > from Bluez, I notice that they can often do minicom over /dev/
> > rfcomm0 in the setup.
> >
> > If I want to access the serial port service like that, but from my
> > C program, do I just treat /dev/rfcomm0 as a serial device and use
> > standard Unix serial programming libraries from my C program to do so?
> > Just curious.  Thanks in advanced for any tip.
>
> You sure can.
>
> You can of course use the code provided by Manuel too but then your
> code won't work without rfcomm/bluetooth. The nice thing is that if
> you keep it generic you can test your application using any old
> serial connection. Or use a pipe in the filesystem etc..
>
> Caveat: I can't get mgetty to work by feeding it /dev/rfcommX though :
> ( It should work, must be one of those things ;)
>
>
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys - and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> Bluez-users mailing list
> Bluez-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bluez-users
>

[-- Attachment #1.2: Type: text/html, Size: 2434 bytes --]

[-- Attachment #2: Type: text/plain, Size: 347 bytes --]

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV

[-- Attachment #3: Type: text/plain, Size: 164 bytes --]

_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  parent reply	other threads:[~2006-12-19 20:26 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-19 19:23 [Bluez-users] minicom over /dev/rfcomm0 Mark S. Townsley
2006-12-19 19:33 ` Manuel Naranjo
2006-12-19 20:25   ` Mark S. Townsley
2006-12-19 20:33     ` Manuel Naranjo
2006-12-19 19:37 ` Bas Schulte
2006-12-19 19:46   ` Manuel Naranjo
2006-12-19 20:26   ` Mark S. Townsley [this message]
2006-12-19 20:39     ` Bas Schulte

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=be976db60612191226p7c4660a7q45d173717c81d634@mail.gmail.com \
    --to=mstownsley@gmail.com \
    --cc=bluez-users@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