public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: David Mackie <D.Mackie@ru.ac.za>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] running 2 rfcomm modules simultaneously
Date: Tue, 14 Sep 2004 14:47:18 +0200	[thread overview]
Message-ID: <20040914124718.GA76088@rucus.ru.ac.za> (raw)
In-Reply-To: <1094998092.5695.19.camel@pegasus>

On Sun 2004-09-12 (16:08), Marcel Holtmann wrote:
> > Has anyone done something like this before?
> 
> this is not possible this way. It needs more changes to provide such a
> functionality and you must keep it inside the RFCOMM module. Why do you
> need it?

I had hoped to be able to "pick-up" data sent to the 2nd RFCOMM Module
(using a new PCM value to differentiate it from the "Original") and pass it to
another program to transport it across the network to another PC where it
would be "injected" into a modified module there. At the moment, I am only
loading the modified module, and it not absolutely necessary that both be
loaded at a time, but would be interesting to do.

-dave

-- 
 David Mackie
 MSc Student - Computer Science -  Rhodes University
 email: D.Mackie@ru.ac.za
   web: http://www.cs.ru.ac.za/research/students/g99m0302/


-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. 
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users

  reply	other threads:[~2004-09-14 12:47 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-01 13:01 [Bluez-users] running 2 rfcomm modules simultaneously David Mackie
2004-09-12 14:08 ` Marcel Holtmann
2004-09-14 12:47   ` David Mackie [this message]
2004-09-14 13:08     ` 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=20040914124718.GA76088@rucus.ru.ac.za \
    --to=d.mackie@ru.ac.za \
    --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