All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: Jim Thompson <jimt@vivato.net>
Cc: Jun Sun <jsun@mvista.com>,
	linux-mips@linux-mips.org,
	Charlie Brady <charlieb-linux-mips@e-smith.com>
Subject: Re: Broadcom 4702?
Date: Wed, 14 Jan 2004 22:53:53 +0000	[thread overview]
Message-ID: <1074120339.866.1.camel@dhcp23.swansea.linux.org.uk> (raw)
In-Reply-To: <7CB2EF32-46DA-11D8-9715-000393C30E1E@vivato.net>

On Mer, 2004-01-14 at 21:42, Jim Thompson wrote:
> I have binaries.  I asked.  I was told "no".

Please report that to the Free Software Foundation. If Broadcom provided
you the binaries and refused to provide you the source they are in
violation of license and the FSF as copyright holder will be happy to
take a (*polite* initially) hammer to their toenails...

Also beware of stupid support people. Some of them come preprogrammed
with "you cant have the source" and you have to go via their managers
for GPL stuff.

  parent reply	other threads:[~2004-01-14 22:56 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-01-13 22:00 Broadcom 4702? Charlie Brady
2004-01-13 22:28 ` Jun Sun
2004-01-14 20:49   ` Charlie Brady
2004-01-14 21:05     ` Jim Thompson
2004-01-14 21:15       ` Alan Cox
2004-01-14 21:42         ` Jim Thompson
2004-01-14 22:00           ` Broadcom gcc/binutils mods (Re: Broadcom 4702?) Charlie Brady
2004-01-14 22:53           ` Alan Cox [this message]
2004-01-15  1:03           ` Broadcom 4702? Jun Sun
2004-01-15  3:39             ` Charlie Brady
2004-01-15  9:11               ` Dominic Sweetman
2004-01-15 21:33                 ` Alan Cox
2004-01-15 22:46                   ` ilya
2004-01-14 21:50       ` Broadcom gcc/binutils changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-14 21:18     ` Broadcom 4702? Jun Sun
2004-01-15 18:53 ` Charlie Brady
2004-01-15 19:14   ` John W. Linville
2004-01-15 20:08     ` Broadcom gcc changes (was Re: Broadcom 4702?) Charlie Brady
2004-01-15 20:18       ` Steven J. Hill
2004-01-15 20:25       ` John W. Linville

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=1074120339.866.1.camel@dhcp23.swansea.linux.org.uk \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=charlieb-linux-mips@e-smith.com \
    --cc=jimt@vivato.net \
    --cc=jsun@mvista.com \
    --cc=linux-mips@linux-mips.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 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.