public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: BlueZ development <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Kernel Module
Date: Mon, 26 Feb 2007 12:44:43 +0100	[thread overview]
Message-ID: <1172490283.27370.20.camel@violet> (raw)
In-Reply-To: <002d01c75995$ccc41470$664c3d50$@gen.tr>

Hi Yunus,

> >> >> I want to write a kernel module and use some bluez commands those
> >> >> included in the kernel. 
> >> >> 
> >> >> I will use it some experimental cases. 
> >> >> 
> >> >> Is it possible to use bluez commands in kernel modules? If so, how can
> I
> >> >> do it?
> >> 
> >> >of course it is possible, but for what strange reason you might wanna
> >> >find yourself writing a kernel module. Explain what you are planning to
> >> >do and I might can give you a more detailed answer. I am not psychic.
> >> 
> >> There is a Project called ULLA (http://ulla.sourceforge.net) and I am
> >> writing a simple bluetooth LLA fot it. ULLA collects link layer
> information
> >> (802.11x, bluetooth, zigbee etc.) to application layer programmes.
> >> 
> >> I will take Bd Addrs and user friendly names fo nearby devices and give
> it
> >> to ULLA Core. 
> >> 
> >> My program will be a kernel module, because I will collect link layer
> >> information. ULLA calls these link layer information collecting modules
> to
> >> Link Provider (LP).
> 
> >the architecture with the kernel module is totally crap. The data
> >collection has to be done in userspace and all these information are
> >provided over D-Bus.
> 
> We talked about this kernel-module problem with you a couple of weeks ago in
> irc #bluez channel. You advice me to work in userspace everytime. My work
> contains only some querying functuonality, for example bd address, user
> friendly name etc. I do not want the whole bluez functuonality in my
> project. I have to do in in kernel-space.

and why does nobody believe me that it is a bad idea to have such stuff
inside the kernel. You have to have the BlueZ userspace part anyway,
because otherwise the adapter is not useful. However feel free to change
the kernel and invent all things again. The D-Bus API actually provides
a prefect interface for your needs. You might wanna run the example
bluetooth-proximity tool to see what I mean. It is only an UI using
D-Bus only.

Regards

Marcel



-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys-and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

      reply	other threads:[~2007-02-26 11:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <D299A7A94D00F12.54EFE86A2B@broadview.com>
2007-02-25 11:14 ` [Bluez-devel] Kernel Module Yunus Özen
2007-02-25 23:49   ` Marcel Holtmann
2007-02-26  4:46     ` Yunus Özen
2007-02-26  9:35       ` Marcel Holtmann
2007-02-26 11:03         ` Yunus Özen
2007-02-26 11:44           ` Marcel Holtmann [this message]

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=1172490283.27370.20.camel@violet \
    --to=marcel@holtmann.org \
    --cc=bluez-devel@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