From: Marcel Holtmann <marcel@holtmann.org>
To: Gregoire Favre <Gregoire.Favre@freesurf.ch>
Cc: BlueZ Mailing List <bluez-users@lists.sourceforge.net>
Subject: Re: [Bluez-users] No more bluez.o in 2.6?
Date: Thu, 08 Apr 2004 11:47:12 +0200 [thread overview]
Message-ID: <1081417632.2970.0.camel@pegasus> (raw)
In-Reply-To: <20040407214322.GA14396@magma.epfl.ch>
Hi Gregoire,
> I compiled 2.6.5-mm2 again, with all blutooth in, and now I can see my
> bluetooth device ;-) I can also scan my Palm device.
> I try http://www-jcsu.jesus.cam.ac.uk/~ned21/tech/tungsten_linux.html
> and after dund --listen --persist --msdun call dun
> I got the following error when I try to connect:
> dund[3647]: RFCOMM TTY creation failed. Operation not supported(95)
this error is because you didn't set CONFIG_BT_RFCOMM_TTY in your kernel
config.
Regards
Marcel
-------------------------------------------------------
This SF.Net email is sponsored by: IBM Linux Tutorials
Free Linux tutorial presented by Daniel Robbins, President and CEO of
GenToo technologies. Learn everything from fundamentals to system
administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&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:[~2004-04-08 9:47 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-07 17:23 [Bluez-users] No more bluez.o in 2.6? Gregoire Favre
2004-04-07 21:43 ` Gregoire Favre
2004-04-08 7:48 ` Aben Siatris
2004-04-08 15:09 ` Gregoire Favre
2004-04-08 16:29 ` Marcel Holtmann
2004-04-10 15:43 ` Aben Siatris
[not found] ` <20040410160451.GB26618@magma.epfl.ch>
2004-04-10 16:45 ` Aben Siatris
2004-04-10 17:37 ` Gregoire Favre
2004-04-08 9:47 ` Marcel Holtmann [this message]
2004-04-08 15:00 ` Gregoire Favre
2004-04-08 16:02 ` Michal Semler (volny.cz)
2004-04-09 12:40 ` Gregoire Favre
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=1081417632.2970.0.camel@pegasus \
--to=marcel@holtmann.org \
--cc=Gregoire.Favre@freesurf.ch \
--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