From: Marco Trudel <mtrudel@gmx.ch>
To: bluez-users@lists.sourceforge.net
Subject: [Bluez-users] Installing Bluez
Date: Wed, 26 Jan 2005 23:14:43 +0100 [thread overview]
Message-ID: <41F81653.4030601@gmx.ch> (raw)
Hello everyone
I've to install bluez on an arm system with a 2.6.7 kernel.
So I've to activate bluez in the kernel, install bluez-libs and bluez-utils.
How to activate bluez support in the kernel?
Is it enough to select (make menuconfig):
Networking Support -> Bluetooth subsystem support
USB Support -> USB Bluetooth TTY support
Or do I have to apply a patch from bluez.org/patches.html?
Is it possible to leave the kernel as it is and make a module for bluez?
Will there be any problems to compile the libs and utils on an arm processor?
kind regards
Marco Trudel
-------------------------------------------------------
This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting
Tool for open source databases. Create drag-&-drop reports. Save time
by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc.
Download a FREE copy at http://www.intelliview.com/go/osdn_nl
_______________________________________________
Bluez-users mailing list
Bluez-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-users
next reply other threads:[~2005-01-26 22:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 22:14 Marco Trudel [this message]
2005-01-26 22:24 ` [Bluez-users] Installing Bluez Marcel Holtmann
2005-01-26 22:54 ` Marco Trudel
2005-01-27 17:32 ` Marcel Holtmann
2005-01-28 14:13 ` Marco Trudel
2005-01-28 17:39 ` Marcel Holtmann
2005-01-28 6:15 ` [Bluez-users] Workaround for the bug in gnu arm linker while using sdpd program Heejune AHN
2005-01-28 7:42 ` Marcel Holtmann
-- strict thread matches above, loose matches on Subject: below --
2005-09-30 9:27 [Bluez-users] Installing BlueZ ronny hidayat
2005-09-30 12:09 ` 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=41F81653.4030601@gmx.ch \
--to=mtrudel@gmx.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 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.