From: Stefan Seyfried <stefan.seyfried@googlemail.com>
To: linux-bluetooth@vger.kernel.org
Subject: Re: access point networking without X
Date: Fri, 14 Aug 2009 16:19:39 +0200 [thread overview]
Message-ID: <20090814161939.43f64dea@stoetzler> (raw)
In-Reply-To: <d89ddf300908140007h767dd390r639955e1d004e2be@mail.gmail.com>
On Fri, 14 Aug 2009 01:07:44 -0600
Brad Midgley <bmidgley@gmail.com> wrote:
> Hey
>
> I've got some python scripts for driving access point services
> (dun/pan) under bluez4. The idea is to cover machines like gumstix or
> beagleboard that run without a ui and can't do the gnome/kde bluetooth
> controllers.
>
> Is anyone interested in me pulling these things together and housing
> them in a standalone project? I was thinking we could move toward a C
> implementation once things have settled down in the python prototype.
> (Python is not always a great requirement to put on embedded hosts).
> If anyone else has built similar helpers, we should collect those
> together.
I am definitely interested in BlueZ console tools (not only) for
embedded systems. It can also be beneficial for debugging (even though
most of that can be done with the bluez-supplied test scripts).
> I'd like to be able to extend this beyond simple access point and be
> able to do audio and voip sort of services as well. These little
> machines are quite capable these days and wouldn't have much trouble
> keeping up.
Would be cool, and I would be willing to help (where possible with my
rather limited knowledge ;-)
--
R&D Preload Department | "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg | "Well, surrounding them's out."
This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2009-08-14 14:19 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-14 7:07 access point networking without X Brad Midgley
2009-08-14 14:19 ` Stefan Seyfried [this message]
2009-08-15 17:36 ` Brad Midgley
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=20090814161939.43f64dea@stoetzler \
--to=stefan.seyfried@googlemail.com \
--cc=linux-bluetooth@vger.kernel.org \
/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