public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Zygo Blaxell <zblaxell@feedme.hungrycats.org>
To: Gene Heskett <gene.heskett@verizon.net>
Cc: Zygo Blaxell <zblaxell@feedme.hungrycats.org>,
	Bastien Nocera <hadess@hadess.net>,
	Zygo Blaxell <zblaxell@dactyl.vpn7.hungrycats.org>,
	jayjwa <jayjwa@atr2.ath.cx>,
	linux-bluetooth@vger.kernel.org
Subject: Re: The link I had working quit.  Help
Date: Wed, 8 Apr 2009 15:30:08 -0400	[thread overview]
Message-ID: <20090408193008.GE18671@hungrycats.org> (raw)
In-Reply-To: <200904081450.37424.gene.heskett@verizon.net>

[-- Attachment #1: Type: text/plain, Size: 751 bytes --]

On Wed, Apr 08, 2009 at 02:50:37PM -0400, Gene Heskett wrote:
> >gnome-bluetooth is a fork of bluez-gnome.  You'd probably have to build it
> > out of svn at svn://svn.gnome.org/svn/gnome-bluetooth unless someone's
> > making binary packages somewhere.
> >
> I see.  Since I've built and installed bluezx-4.34, am I new enough?

bluez is the user-space part of the bluetooth stack.  gnome-bluetooth is the UI.

> Got it, cu doesn't know the port(s) I named with the -p option.  And the 
> manpage doesn't seem to describe that part either. :(

	cu -l /dev/ttyS0 -s 9600

or for rfcomm most likely just

	cu -l /dev/rfcomm0

though with a real RS-232 port on the remote device I don't
know if you have to match baud rates or not.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

  reply	other threads:[~2009-04-08 19:30 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-04 20:36 The link I had working quit. Help Gene Heskett
2009-04-05 20:59 ` Gene Heskett
2009-04-05 21:59   ` Gene Heskett
     [not found]     ` <alpine.LNX.2.00.0904060246560.29837@nge2.ngu.pk>
2009-04-06 18:57       ` Gene Heskett
2009-04-06 22:14         ` Zygo Blaxell
2009-04-07  4:08           ` Gene Heskett
2009-04-07 20:40             ` Zygo Blaxell
2009-04-08  4:11               ` Gene Heskett
2009-04-07 18:54           ` Gene Heskett
2009-04-07 20:02             ` Zygo Blaxell
2009-04-07 21:35               ` Gene Heskett
2009-04-07 21:56                 ` Zygo Blaxell
2009-04-07 23:05               ` Bastien Nocera
2009-04-08  4:26                 ` Gene Heskett
2009-04-08 15:06                 ` Gene Heskett
2009-04-08 16:17                   ` Zygo Blaxell
2009-04-08 18:50                     ` Gene Heskett
2009-04-08 19:30                       ` Zygo Blaxell [this message]
2009-04-08 19:35                         ` Gene Heskett
2009-04-08 19:36                           ` Zygo Blaxell
2009-04-09  2:40                             ` Gene Heskett
2009-04-09 14:55                               ` Zygo Blaxell
2009-04-09 18:28                                 ` Gene Heskett
2009-04-08 19:03                     ` Gene Heskett
     [not found]         ` <alpine.LNX.2.00.0904062153190.3436@nge2.ngu.pk>
2009-04-07  4:47           ` Gene Heskett

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=20090408193008.GE18671@hungrycats.org \
    --to=zblaxell@feedme.hungrycats.org \
    --cc=gene.heskett@verizon.net \
    --cc=hadess@hadess.net \
    --cc=jayjwa@atr2.ath.cx \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=zblaxell@dactyl.vpn7.hungrycats.org \
    /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