From: "Nicholas A. Preyss" <nalp@gmx.net>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Questions about BlueZ in commercial use
Date: Sun, 27 Jun 2004 19:13:36 +0200 [thread overview]
Message-ID: <20040627171336.GA25886@gmx.net> (raw)
In-Reply-To: <001101c45c55$7803b160$0364a8c0@haruo>
On 0, KeiHachi <keihachi@swissinfo.org> wrote:
> Thanks for your reply, nicholas.
> > If this is the first GPL software you are using, please read and
> > understand the implications of this license. This is no offense, but i
> > think some DVD and Router manufacturer didn't do this before integrating
> > linux code in their products.
>
> Thanks.
> I know the topic of GPL in Linux world of course,
> so we have already studied about the license issues,
> and will continue to study more & more about it from now.
> > > - eSCO (enhanced SCO) in Bluetooth 1.2
> > > Do you have any plan to develop these?
> >
> > I am not Marcel and not writing any kernel code, but i listened his talk
> > at Linuxtag Karlsruhe. I think the problem is the lack of the end-user
> > products already supporting this. But it is on his plan:
> >
> > http://www.holtmann.org/papers/bluetooth/lt2004_slides.pdf
>
> Thanks.
> I think he will need to spend a little extra time (maybe a few months)
> for supporting eSCO.
I think if you pay him for supporting eSCO, then it will be very quickly
integrated.
> > > - Audio/Video related profiles
> > > Do you have any plan to develop these(A2DP, AVRCP)?
> >
> > He posted some time ago a request, that if people supply him such
> > hardware he would implent those support.
>
> Do you mean that offering a headphone with Bluetooth audio functionality
> to him is necessary to develop A2DP?
Look here:
http://sourceforge.net/mailarchive/message.php?msg_id=8643774
I don't know whether someone donated anything after this request, but I
think he can't get enought. ;)
> > I don't understand, are you looking for a company that provides such
> > support or you want to start a business providing such support?
> > I don't know of the first, but contacting the developer directly, one
> > may provide such support. The second is of course possible.
>
> I supposed the first one you mentioned. The latter one is out of my
> supposition.
> If you have a few guesses about such a company that provides the
> support of using BlueZ, please tell me the name of such a company.
I don't know of any...
> Or, please forgive me for asking this rude question, but,
> could the developers of BlueZ community provide the support to ensure
> the quality, as counter value for some maintenance fee?
..but i am quite sure this might be possible. Marcel while probably
reply itself. He is the best suited person, for such a job.
> > It is so stable, you don't need one, ;) Just kidding. Why do you think,
> > there is no stable version? I think the releases are considered stable
> > and the CVS stuff and the utils2/libs2 are the testing branch.
>
> For example, Affix provides us these two versions software,
> the testing version and the stable version.
> http://affix.sourceforge.net/#download
>
> I suppose such version control or management like Affix.
>
> If a new profile is testing or has been released immediately
> after the development, probably some bugs are still included.
> So we think if BlueZ is used for the commercial use, the stable
> version is necessary,
> because a commercial product is required to be a high quality.
Yeah I understand your problem and IMO you are partly right. There is no
so strict seperation of a testing and a stable tree. But you have to
seperate: the generic ACL/RFCOMM support is quite stable. You can use
it without integrating all those parts which might be considered not
completely stable.
I personaly wouldn't use HID or SCO support in a commercial device.
> If I misundersood, I am sorry.
> The utils2/libs2 are the testing version, the others are the
> stable version, you mean?
yes
> If so, is the modification of the kernel part still stable?
You mean those -mh patches for 2.6?
nicholas
-------------------------------------------------------
This SF.Net email sponsored by Black Hat Briefings & Training.
Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
digital self defense, top technical experts, no vendor pitches,
unmatched networking opportunities. Visit www.blackhat.com
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel
next prev parent reply other threads:[~2004-06-27 17:13 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-27 9:47 [Bluez-devel] Questions about BlueZ in commercial use KeiHachi
2004-06-27 12:52 ` Nicholas A. Preyss
2004-06-27 14:45 ` KeiHachi
2004-06-27 17:13 ` Nicholas A. Preyss [this message]
2004-06-28 16:30 ` KeiHachi
2004-06-28 17:22 ` Marcel Holtmann
2004-06-27 18:29 ` Marcel Holtmann
2004-06-28 16:33 ` KeiHachi
2004-06-28 17:45 ` Marcel Holtmann
2004-06-28 14:39 ` Ademar de Souza Reis Jr.
2004-06-28 14:48 ` Marcel Holtmann
2004-06-28 15:19 ` Ademar de Souza Reis Jr.
2004-06-28 15:38 ` Marcel Holtmann
2004-06-28 15:59 ` Stephen Crane
2004-06-28 17:06 ` Ademar de Souza Reis Jr.
2004-06-28 17:15 ` Marcel Holtmann
2004-06-27 18:09 ` Marcel Holtmann
2004-06-27 19:10 ` Nicholas A. Preyss
2004-06-27 19:09 ` Marcel Holtmann
2004-06-27 20:34 ` Nicholas A. Preyss
2004-06-27 20:49 ` Marcel Holtmann
2004-06-27 21:42 ` Nicholas A. Preyss
2004-06-28 7:37 ` Marcel Holtmann
2004-06-28 16:28 ` KeiHachi
2004-06-28 17:13 ` Marcel Holtmann
2004-06-29 17:08 ` KeiHachi
2004-06-29 17:41 ` Marcel Holtmann
2004-06-30 16:22 ` KeiHachi
2004-06-30 18:11 ` Marcel Holtmann
2004-07-04 8:57 ` KeiHachi
2004-07-04 11:38 ` Marcel Holtmann
2004-07-04 13:19 ` Peter Favrholdt
2004-07-04 13:47 ` 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=20040627171336.GA25886@gmx.net \
--to=nalp@gmx.net \
--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