linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marcel Holtmann <marcel@holtmann.org>
To: bluez-devel@lists.sourceforge.net
Subject: Re: [Bluez-devel] Broadcom [Fwd: RE: Chipset specification [Fwd: Web Site Feedback/Support Request - Bluetooth - General]]
Date: Tue, 22 Nov 2005 12:34:00 +0100	[thread overview]
Message-ID: <1132659240.28644.32.camel@blade> (raw)
In-Reply-To: <4378F4B6.1010808@gmx.de>

Hi Maik,

> >>I don't think anyone would have a problem with you telling them you're
> >>"with" the bluez group, but I suspect they're asking this way because
> >>they want an NDA signed. That obviously wouldn't be acceptable.
> > 
> > Why wouldn't it? I would like to read it before judging it.
> 
> I think an agreement not to release any original Broadcom documents to
> the general public would be acceptable, as long as they understand and
> agree that the driver would be open-source and that therefore some
> information would indirectly be published. Of course, I can only speak
> for myself, other people might disagree.
> 
> In fact, that's pretty much what I suggested in a follow-up eMail. I'll
> see what their position is. Broadcom has been somewhat cooperative
> regarding open-source projects in the past, so maybe something can
> actually be worked out.

feel free to agree with Broadcom whatever you think is needed, but I am
not dealing with it. This is way too much politics for me and I actually
prefer to write good code. And btw it is not only Broadcom that isn't
really helpful. However they are the big player besides CSR, but did you
ever thought about Silicon Wave, Texas Instruments or Infineon. Non of
their chips have any special support so far and I can't advice anyone to
pick one of these to build an embedded device running Linux.

Maybe someone should point them to see how CSR is working with the open
source community. And I didn't see their chip sales going down, because
of it ;)

Regards

Marcel




-------------------------------------------------------
This SF.Net email is sponsored by the JBoss Inc.  Get Certified Today
Register for a JBoss Training Course.  Free Certification Exam
for All Training Attendees Through End of 2005. For more info visit:
http://ads.osdn.com/?ad_id=7628&alloc_id=16845&op=click
_______________________________________________
Bluez-devel mailing list
Bluez-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bluez-devel

  reply	other threads:[~2005-11-22 11:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-14 19:06 [Bluez-devel] Broadcom [Fwd: RE: Chipset specification [Fwd: Web Site Feedback/Support Request - Bluetooth - General]] Maik Zumstrull
2005-11-14 19:12 ` Brad Midgley
2005-11-14 20:22   ` Robert Siemer
2005-11-14 20:33     ` Maik Zumstrull
2005-11-22 11:34       ` Marcel Holtmann [this message]
2005-11-14 20:35     ` 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=1132659240.28644.32.camel@blade \
    --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;
as well as URLs for NNTP newsgroup(s).