Telegent TG100: no source, no gpl copy, no response

Glenn L. McGrath bug1 at iinet.net.au
Wed Oct 5 13:20:19 CEST 2005


On Wed, 5 Oct 2005 18:47:01 +1000
"Glenn L. McGrath" <bug1 at iinet.net.au> wrote:

> $ dd if=20050520_V10000_MA100TV.img of=out2 bs=1 skip=658432
> 5404672+0 records in
> 5404672+0 records out
> 5404672 bytes (5.4 MB) copied, 21.4171 seconds, 252 kB/s
> 
> $ file out2
> out2: Linux Compressed ROM File System data, little endian size 65536
> CRC 0x7d4079ca, edition -1598284684, 601355551 blocks, 1693651130 files
> 
> Guess i need to rebuild my kernel to support compressed romfs so i can
> mount this and look at it.

well, this was just a small file, not the main filesystem. It contains
web pages and images, also CVS files, so maybe it uses cvs to update
itself from the local server.

# cat CVS/Root
:pserver:erin at 192.168.210.221:/home/cvsadmin


Turns out i didnt really need to compile cramfs support itno my kernel,
i can get a list of the contents of the Compressed RomFS and their
offsets by doing

# cramfsck -vv out2

It shows the last file ends at offset 620691.

The next file in the firmware should start at 1279123 (658432 + 620691)

Sure enough, there is a heap of zero's and then same weird data as
before the first and second firmware entries.

$ dd if=20050520_V10000_MA100TV.img of=out3 bs=1 skip=1282048

Its another small cramfs with shared libraries and what looks like some
data,
 - libfreetype.so (freetype is GPL or BSD)
 - libmwfonts.so (microwindows is GPL or MPL)

Same principle as before gives me the last file

# dd if=20050520_V10000_MA100TV.img of=out4 bs=1 skip=1917952

This is the root filesystem, it contains
 - busybox (GPL)
 - tinylogin (GPL)
 - udhcp (GPL)
 - uClibc (LGPL)
 - lufs (GPL?)
 - more microwindows/nano stuff (MPL or GPL)
 - ihttpd (looks like BSD, not sure)
 - a heap of graphics type libraries i dont recognise.
 - realmagic kernel modules (binary only i assume)
 - lufs kernel module
 - IPN2220STA kernel module (wireless lan driver i think)
 - some wireless binaries
 - what looks like a few custom binaries.


So i suspect telegent might be a reseller for cybertan, who get their
hardware from micrel.

I am one of the copyright holders of busybox, i will inform the project
about it (generally the same same people involved with tinylogin,
uClibc and udhcp).

I think its hard to enforce anything in .tw so it might be a waste of
time talking to cybertan, but in theory if telegent is violating the
GPL in germany a recipient or copyright holder can make them withdraw
the product from sale if they refuse to comply. (to the best of my
knowledge)

To be sure Telegent is doing the wrong you really need to check the
documentation to make sure there isnt an offer of the source code
buried in ther somwhere.

Busybox started to create a list of violaters, but unfortunately in the
embedded world there are very few companies who honour the GPL :(

http://www.busybox.net/shame.html



Glenn




More information about the legal mailing list