Subject: Inprocomm and their module - msg#00013

Previous Message by Date:

GNU/Linux software on Siemens and Da-San ethernet switches

Hello, I am working in a data carrier company in Nairobi, Kenya, and we are currently deploying a metro-ethernet through our contracted partners of Siemens, Germany. Siemens have recently acquired the Korean company Da-San, and they have re-branded Da-San's line of ethernet switches as Siemens Surpass hiD6610 and hiD6625. After having worked with these switches for a while, I noticed that they are running an ordinary Linux kernel and some GPLed software (such as "busybox", plus of course the GNU coreutils), while the user interface and the advanced bridging and routing protocols are implemented via IPInfusion's commercial ZebOS software suite. Now, for various reasons I would like to be able to tweak (you could also say "fix") the switch software, so I've approached various high- and low-level Siemens and Da-San people to provide me with the source code, but to no avail whatsoever. The (very badly written) user manual for the most recent switch Surpass hiD6610-S311 says on its first inside page that the "source code of the GPLed parts of the software" (my paraphrase) will be made available on request. It was a bit hazy about how that request is to be made (the web address actually terminates in an ellipsis, and the whole manual is still in an alpha state), but there was a Korean fax number, to which I have duly faxed my request, again to no avail. I have since learned from the list FAQ that the hardware makers are also meant to release build scripts and such like, and also everything pertaining to the most current version. Since the firmware keeps getting hotfixed, I would be really happy about access to the current develpment tree. But so far all my requests are completely ignored. I would appreciate very much any information on how I can convince Siemens/Da-San to release that source code. Many thanks! Thomas Köppe

Next Message by Date:

Re: GNU/Linux software on Siemens and Da-San ethernet switches

Just for reference to the other readers on the list: I've taken up this issue, it wasn't lost ;) -- - Harald Welte <laforge@xxxxxxxxxxxx> http://gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) pgp18P4CTctoy.pgp Description: PGP signature

Previous Message by Thread:

GNU/Linux software on Siemens and Da-San ethernet switches

Hello, I am working in a data carrier company in Nairobi, Kenya, and we are currently deploying a metro-ethernet through our contracted partners of Siemens, Germany. Siemens have recently acquired the Korean company Da-San, and they have re-branded Da-San's line of ethernet switches as Siemens Surpass hiD6610 and hiD6625. After having worked with these switches for a while, I noticed that they are running an ordinary Linux kernel and some GPLed software (such as "busybox", plus of course the GNU coreutils), while the user interface and the advanced bridging and routing protocols are implemented via IPInfusion's commercial ZebOS software suite. Now, for various reasons I would like to be able to tweak (you could also say "fix") the switch software, so I've approached various high- and low-level Siemens and Da-San people to provide me with the source code, but to no avail whatsoever. The (very badly written) user manual for the most recent switch Surpass hiD6610-S311 says on its first inside page that the "source code of the GPLed parts of the software" (my paraphrase) will be made available on request. It was a bit hazy about how that request is to be made (the web address actually terminates in an ellipsis, and the whole manual is still in an alpha state), but there was a Korean fax number, to which I have duly faxed my request, again to no avail. I have since learned from the list FAQ that the hardware makers are also meant to release build scripts and such like, and also everything pertaining to the most current version. Since the firmware keeps getting hotfixed, I would be really happy about access to the current develpment tree. But so far all my requests are completely ignored. I would appreciate very much any information on how I can convince Siemens/Da-San to release that source code. Many thanks! Thomas Köppe

Next Message by Thread:

Re: Inprocomm and their module

On Sat, Jan 07, 2006 at 12:58:44AM +0100, Carlos Martin wrote: > Hi all, > > I've been trying to get some information about my Inprocomm IPN2220 > wireless card and I've stumbled upon D-Link's GPL source tarball for > it's DI-624M device. It is available from D-Link's and from Are you referring to the DI-634M ? I cannot find a DI-624M. > The files in linux-2.4.x/drivers/net/wireless/inpro2220 in the > tarball are a Makefile, some header files and a binary MIPS file. The > output from file is: > IPN2220: ELF 32-bit MSB MIPS-I relocatable, MIPS, version 1 (SYSV), not > stripped > and upon disassembly I can see that it's actually a Linux module-ish > file. It does contain some Linux functions as .extern references, > although it itself doesn't seem to have module entry/exit functions > (from what I've seen up to now). > > The headers are under a propietary lincense, and _use_ of these files > is prohibited except if you have a license agreement with > inprocomm. > This has become quite hard recently, as the company doesn't > seem to exist anymore. The website went down early 2005 and its domain > (inprocomm.com.tw) stopped resolving some time later. IIRC, they've been bought by another .tw company, though I don't remember their name. > The Makefile references some .o files which should get linked with > the binary blob in order to make the driver, though neither those > files ore their corresponding sources are available. ok, at least those .o files need to be available. > Should their driver be available under the GPL, it being a > derivative work (I think) of the Linux kernel? What can be done now > that the company (apparently) ceased to exist? I am currently downloading the D-Link DI-634M 'GPL' tarball, and I'll investigate it before I can make any further statement. > How far am I allowed to reverse-engineer this binary blob under > current EU regulations? I'd like to create an Open Source driver for > it, but I can't be sure I'm allowed to even look at those header files > and/or the binary blob for me to base it on. That's quite a disputed question. First of all, the technique of reverse engineering matters. If you run the code in an emulator, and look at the emulator, then it's merely observation of a running program and certainly not "decompilation" in the sense of the EU copyright regulations. Whether disassembling the code falls under the "decompilation" rules is also unclear within the legal community. In any way, there is the exception for interoperability. There you first need to ask the vendor for sufficient documentation - and when they don't give it to you in some specified period of time, you're allowed to do re-engineering for interoperability purpose. -- - Harald Welte <laforge@xxxxxxxxxxxx> http://gnumonks.org/ ============================================================================ "Privacy in residential applications is a desirable marketing option." (ETSI EN 300 175-7 Ch. A6) pgpwjO8BKkkgZ.pgp Description: PGP signature