From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] USSP compilation problem for linux 2.6
Date: Wed, 16 Mar 2005 14:55:32 +0100 [thread overview]
Message-ID: <1110981332.11792.32.camel@pegasus> (raw)
In-Reply-To: <f54d8640503160537449496dd@mail.gmail.com>
Hi Benny,
> We have purchased a BT Serial port adapter. I am now involved in
> testing this. To one PC I am connecting a Standard BT USB dongle and
> to another PC I am connecting the BT Serial port adaptor.
>
> I am facing some problems while compiling(On fedora 3 - linux kernel -
> 2.6.9-1.667) the "ussp" source found in the "rfcomm-0.10" source
> downloaded from the
> http://www.holtmann.org/linux/bluetooth/rfcomm.html site.
don't even try to deal the the old RFCOMM implementation. The new one is
inside the kernel and directly integrated into the network socket and
the TTY layer.
Regards
Marcel
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next prev parent reply other threads:[~2005-03-16 13:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-07 18:45 [Bluez-users] PAN Configurations Anderson Rodrigues
2005-03-09 11:45 ` [Bluez-users] Can 2 services work parallely between a PC and a BT device Benny
2005-03-09 17:57 ` Marcel Holtmann
2005-03-16 13:37 ` [Bluez-users] USSP compilation problem for linux 2.6 Benny
2005-03-16 13:55 ` Marcel Holtmann [this message]
2005-03-16 15:04 ` Benny
2005-03-16 15:26 ` 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=1110981332.11792.32.camel@pegasus \
--to=marcel@holtmann.org \
--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 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.