From: "KeiHachi" <keihachi@swissinfo.org>
To: "Nicholas A. Preyss" <nalp@gmx.net>, <bluez-devel@lists.sourceforge.net>
Subject: Re: [Bluez-devel] Questions about BlueZ in commercial use
Date: Tue, 29 Jun 2004 01:30:36 +0900 [thread overview]
Message-ID: <001701c45d2d$3fe99280$0364a8c0@haruo> (raw)
In-Reply-To: 20040627171336.GA25886@gmx.net
Hi, nicholas.
Thanks for your reply again.
> > 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.
Thanks for your advice.
It can't be decided on my own responsibility,
but I will input it to our team members when we will study on this topic.
> > 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. ;)
Thank you very much for this reference of the thread that you have searched.
I also guess he doesn't get enough donation.
> > 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...
OK, thank you.
And please forgive me for asking such a rude question.
> > 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.
Yes, I think so, too.
The problem is whether it is acceptable to ask him to do such a job, or not.
I'm worried that such a business model may be unseemly in the open-source world.
(This is the reason why I ask a question to this mailing-list)
> > 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.
Yes, I understand what you say, because of the reply from you and Marcel.
> I personaly wouldn"t use HID or SCO support in a commercial device.
Why won't you use these features in a commercial device?
(This is only my personal interest.)
> > If so, is the modification of the kernel part still stable?
>
> You mean those -mh patches for 2.6?
Now I understand this part in my mind.
I'm sorry for this confusing question. Please forget this part.
Regards,
KeiHachi
-------------------------------------------------------
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-28 16:30 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
2004-06-28 16:30 ` KeiHachi [this message]
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='001701c45d2d$3fe99280$0364a8c0@haruo' \
--to=keihachi@swissinfo.org \
--cc=bluez-devel@lists.sourceforge.net \
--cc=nalp@gmx.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.