public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Fwiffo <fwiffo@ircom.org>
To: linux-kernel@vger.kernel.org
Subject: GPL issues with a company
Date: Sat, 09 Oct 2004 15:12:05 +0200	[thread overview]
Message-ID: <4167E3A5.8080807@ircom.org> (raw)

Excuse me if I'm sending it in the wrong place, but since I don't really 
know were to send it to, I've put the thing in here, since I think this 
should be noticed by whom is passing time over code where someone else 
now is doing whatevere he wants without respect...

Since I don't have much time, I'm pasting the letter I sent to the 
squashfs author, it contains necessary information, plus I add something 
in the end:

*-----------------------------------*
Hi,

I'm sending this notice to communicate to you that a company, formely 
named dynalink, in new zeland,
http://www.dynalink.co.nz/ is selling one (at least to my knowledge, I 
don't have investigated any further) ADSL that contain a modified Linux 
Kernel version with squashfs support, further investigation to the 
relevant portion of the squashfs filesystem gave me notice that maybe 
they've done relevant modification to your filesystem, but haven't, 
until now, and after my request, put a single source code line, nor of 
the linux kernel, nor of the uclib nor of the squashfs and whatever 
they've there....

http://fwiffo.altervista.org/gigaset.bin contains the firmware of the 
modem in question (known as RTA230 in the dynalink page), the processor 
is a MIPS32, below output from modem's proc filesys:
-----
system type             : RTA230
processor               : 0
cpu model               : BCM6345 V0.0
BogoMIPS                : 92.97
wait instruction        : no
microsecond timers      : yes
tlb_entries             : 32
extra interrupt vector  : no
hardware watchpoint     : no
VCED exceptions         : not available
VCEI exceptions         : not available
-----
As you can see in the gigaset.bin, after exactly 256 bytes begins the 
squashfs (typical big endian style, since we are talking of big endian 
machine), but, at least to my little knowledge of programming and of the 
filesystem in question (I'm very ignorant for that matter, but at least 
I've spotted a few things....) I've seen that this isn't the usual 
output of one of your squashfs tools....
And also, I've taken the squashfs image from the device directly as 
output from the RTA230 's modem, but hadn't any success in using it with 
any of your patch, so, we are in front of a modification maybe?!
...I hope that at least those things will be useful to you...If you also 
look in http://fwiffo.altervista.org even if the page is in italian, you 
will see an image of the modem in the end of the page; that very modem 
is distributed by Telecom Italia S.p.A., a company were I work, and is 
rebranded by Siemens, here the modem's name is: Alice ADSL Gigaset .

If you want to know something else, I'm here to answer.

Puligheddu Karsten

PS: I guess they're also violating GPL....and I guess I will send 
similiar notices to LINUX ML and uclib authors... *
-----------------------------------
# cat /proc/version
Linux version 2.4.17 (michaelc@ADSL_SW1_LINUX) (gcc version 3.1) #1 Mon 
May 10 1
5:30:45 CST 2004
*

                 reply	other threads:[~2004-10-09 13:11 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=4167E3A5.8080807@ircom.org \
    --to=fwiffo@ircom.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox