Hello,
Before confirming the resources to qualify BlueZ I need to work out what
will be involved. I will get to know BlueZ a bit and work out what we might
be able to qualify and what will be needed to do so. Then I can appeal for
help!
I will also produce a Qualification FAQ which summarises the various
discussions I have in both Bluetooth and BlueZ circles.
There is a general question I can usefully answer about Qualifying Bluetooth
products now:
The Qualified Product Listing can change, this means that unless the whole
thing is rewritten I cant imagine BlueZ needing to be requalified completely
(and expensively with a new listing fee). We can start with a basic listing
because new profiles can be added and other changes can be made for whatever
reason, they just need appropriate evidence to be approved by the BQB. The
Qualified Product listing for Widcoms stack for instance covers all versions
of Windows and has a great long revision history. You can view it at
http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts&D
etails=Yes&ProductID=250.
I will have to discuss with the BQB what limits of platform may be
appropriate if the same source code is used. My BQB has little knowledge of
Linux so my advice will be a great help to him, but I need to know from you
how different kernels and processors and even compilers affect BlueZ.
Also I need your questions and pointers to any problems you can see arising,
such as non-conformances with the BT specification.
Could someone tell me the best way of posting the Qualification FAQ?
BlueZ seems to be the sole copyright of Qualcomm - is this correct?
Would it be appropriate to make the listing in the name of Qualcomm with Max
as the contact, or is there now some other kind of BlueZ organisation?
Best Wishes.
Halam
--------------------------------------------
Halam Rose
Bluetooth Specialist
7 layers UK Ltd
Don't miss the 7 layers
Update-seminar on testing & qualification
9 April 2003
London Heathrow
more details: http://www.7layers.com/news-room/news-room-events-2003.html
Tel: +44 (0)1763 262524
Fax: +44 (0)1763 261177
Mob: +44 (0)7876 560922
[email protected]
http://www.7layers-UK.com
Melbourn Science Park
Cambridge Road
Melbourn
Hertfordshire SG8 6HB
--------------------------------------------
The information contained in this message
is confidential and should not be disclosed
to any third party whether or not you are the
intended addressee indicated in the message.
Addressees of this email may exercise their
rights under the 1988 Data Protection Act.
--------------------------------------------
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
Hello Gentlemen,
Bluetooth products are listed in the name of a member of the Bluetooth Sig.
Membership is free for 'Adopter Members'.
May I suggest that someone - Max I expect - register the BlueZ Project in
preparation for the Qualification work.
We will also need someone to sign the 'Compliance Folder' which is a job for
a representative of the BlueZ Project.
Who can help me complete the ICS (implementation conformance statements)?
These documents declare what functionality is supported - get them wrong and
the wrong tests are specified. I'm reluctant to keep on asking Max because
he seems to handle a lot of stuff already.
BW
Halam
--------------------------------------------
Halam Rose
Bluetooth Specialist
7 layers UK Ltd
Don't miss the 7 layers
Update-seminar on testing & qualification
9 April 2003
London Heathrow
more details: http://www.7layers.com/news-room/news-room-events-2003.html
Tel: +44 (0)1763 262524
Fax: +44 (0)1763 261177
Mob: +44 (0)7876 560922
[email protected]
http://www.7layers-UK.com
Melbourn Science Park
Cambridge Road
Melbourn
Hertfordshire SG8 6HB
--------------------------------------------
The information contained in this message
is confidential and should not be disclosed
to any third party whether or not you are the
intended addressee indicated in the message.
Addressees of this email may exercise their
rights under the 1988 Data Protection Act.
--------------------------------------------
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. http://www.etnus.com
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
At 04:47 AM 3/5/2003, Stephen Crane wrote:
>On Wed, 2003-03-05 at 12:04, Marcel Holtmann wrote:
>> > BlueZ seems to be the sole copyright of Qualcomm - is this correct?
>> >
>> > Would it be appropriate to make the listing in the name of Qualcomm with Max
>> > as the contact, or is there now some other kind of BlueZ organisation?
>>
>> The copyright thing is not very easy. The core code (HCI and L2CAP) are
>> copyright of Qualcomm, the BNEP code contains copyright from Inventel
>> and Max, the RFCOMM code has copyright from Max and me. The HCI drivers
>> have much more different copyrights inside. For the user space part you
>> will also get some more names.
>>
>> Maybe my idea with an own organization for BlueZ is a good one.
>
>Or turn the copyright over to the FSF?
Very very very very (whole bunch of "very" words here) unlikely :)
>(I'd push to have the user-space libs relicensed under the LGPL first though.)
Yeah, thanks for reminder :)
Max
At 09:24 AM 3/3/2003, Halam Rose wrote:
>There is a general question I can usefully answer about Qualifying Bluetooth
>products now:
>The Qualified Product Listing can change, this means that unless the whole
>thing is rewritten I cant imagine BlueZ needing to be requalified completely
>(and expensively with a new listing fee). We can start with a basic listing
>because new profiles can be added and other changes can be made for whatever
>reason, they just need appropriate evidence to be approved by the BQB. The
>Qualified Product listing for Widcoms stack for instance covers all versions
>of Windows and has a great long revision history. You can view it at
>http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts&D
>etails=Yes&ProductID=250.
Good. Thanks for clarifying that.
>I will have to discuss with the BQB what limits of platform may be
>appropriate if the same source code is used.
Yeah, that'd be interesting.
>My BQB has little knowledge of Linux so my advice will be a great help to him,
>but I need to know from you how different kernels and processors and even compilers
>affect BlueZ.
Processors shouldn't really affect all endianess and memory access issues have been
fixed long time ago.
The only compile that we support is GCC. Intel C compiler might be able to compile
Linux kernel in which case it will work with Bluetooth code also.
>Also I need your questions and pointers to any problems you can see arising,
>such as non-conformances with the BT specification.
>
>Could someone tell me the best way of posting the Qualification FAQ ?
This mailing list. You could send updates periodically.
>BlueZ seems to be the sole copyright of Qualcomm - is this correct?
No. Several people (including me) have personal copyrights. And other
companies too.
>Would it be appropriate to make the listing in the name of Qualcomm with Max
>as the contact,
No. These days Qualcomm has pretty much nothing to do with it. Other than the
fact that I work for this excellent company.
>or is there now some other kind of BlueZ organisation?
Not that I know of :).
Can it be listed as something like
Linux Bluetooth protocol stack.
Organization:
BlueZ project.
Contacts:
[email protected]
?
Max
-------------------------------------------------------
This SF.net email is sponsored by: Etnus, makers of TotalView, The debugger
for complex code. Debugging C/C++ programs can leave you feeling lost and
disoriented. TotalView can help you find your way. Available on major UNIX
and Linux platforms. Try it free. http://www.etnus.com
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel
On Wed, 2003-03-05 at 12:04, Marcel Holtmann wrote:
> > BlueZ seems to be the sole copyright of Qualcomm - is this correct?
> >
> > Would it be appropriate to make the listing in the name of Qualcomm with Max
> > as the contact, or is there now some other kind of BlueZ organisation?
>
> The copyright thing is not very easy. The core code (HCI and L2CAP) are
> copyright of Qualcomm, the BNEP code contains copyright from Inventel
> and Max, the RFCOMM code has copyright from Max and me. The HCI drivers
> have much more different copyrights inside. For the user space part you
> will also get some more names.
>
> Maybe my idea with an own organization for BlueZ is a good one.
Or turn the copyright over to the FSF? (I'd push to have the user-space
libs relicensed under the LGPL first though.)
Later,
Steve
--
Stephen Crane, Rococo Software Ltd. http://www.rococosoft.com
[email protected] +353-1-6601315 (ext 209)
Hi Halam,
> There is a general question I can usefully answer about Qualifying Bluetooth
> products now:
> The Qualified Product Listing can change, this means that unless the whole
> thing is rewritten I cant imagine BlueZ needing to be requalified completely
> (and expensively with a new listing fee). We can start with a basic listing
> because new profiles can be added and other changes can be made for whatever
> reason, they just need appropriate evidence to be approved by the BQB. The
> Qualified Product listing for Widcoms stack for instance covers all versions
> of Windows and has a great long revision history. You can view it at
> http://qualweb.opengroup.org/Template2.cfm?LinkQualified=QualifiedProducts&D
> etails=Yes&ProductID=250.
this sounds very good.
> I will have to discuss with the BQB what limits of platform may be
> appropriate if the same source code is used. My BQB has little knowledge of
> Linux so my advice will be a great help to him, but I need to know from you
> how different kernels and processors and even compilers affect BlueZ.
>From my knowledge and from the postings on the mailing list the BlueZ
stack have successful tested on
- x86 (UP and SMP)
- sparc (32bit and 64bit, UP and SMP)
- arm (StrongARM, XScale)
- PowerPC
The Motorola DragonBall is also listed as supported platfrom, but I
can't remember any posting about success on it (Max, please correct me).
And the new Intel HT technologie should also be supported, but I don't
have heard from any success.
The kernel requires a Gnu C compiler (gcc) 2.95.3. I use a 2.95.4, but
it should also compile with the 2.96 from RedHat and the new GCC 3.x (if
it dooesn't, we will fix it). For information about kernel compiler
requirements, please take a look at Documentation/Changes in the 2.4
kernel tree.
> BlueZ seems to be the sole copyright of Qualcomm - is this correct?
>
> Would it be appropriate to make the listing in the name of Qualcomm with Max
> as the contact, or is there now some other kind of BlueZ organisation?
The copyright thing is not very easy. The core code (HCI and L2CAP) are
copyright of Qualcomm, the BNEP code contains copyright from Inventel
and Max, the RFCOMM code has copyright from Max and me. The HCI drivers
have much more different copyrights inside. For the user space part you
will also get some more names.
Maybe my idea with an own organization for BlueZ is a good one.
Regards
Marcel
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Bluez-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/bluez-devel