From: Luke -Jr <luke@dashjr.org>
To: ecos-maintainers@ecos.sourceware.org
Subject: Copyright infringement: Scientific-Atlanta WebStar DPC2100
Date: Sun, 15 Jun 2008 04:37:00 -0000 [thread overview]
Message-ID: <200806142336.35465.luke@dashjr.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 584 bytes --]
FYI: Just sent this off to gpl-violations.org
http://wiki.openwrt.org/OpenWrtDocs/Hardware/Scientific-Atlanta/DPC2100
Just got access to this cable modem's serial port, and it appears to be
running eCos (GPL'd). I did not receive a copy of the GPL, nor source code or
an offer for such. I also have not located any sign of said source after a
few minutes of Googling around.
My goal is to port Linux to this cable modem, so please keep me informed and
possibly involved to some extent in enforcement, as I will be able to benefit
from the eCos code for my port.
Thanks,
Luke
[-- Attachment #2: Luke -Jr <luke@dashjr.org>: Scientific-Atlanta WebStar DPC2100 --]
[-- Type: message/rfc822, Size: 1064 bytes --]
From: Luke -Jr <luke@dashjr.org>
To: license-violation@gpl-violations.org
Subject: Scientific-Atlanta WebStar DPC2100
Date: Sat, 14 Jun 2008 22:01:02 -0500
Message-ID: <200806142201.04839.luke@dashjr.org>
http://wiki.openwrt.org/OpenWrtDocs/Hardware/Scientific-Atlanta/DPC2100
Just got access to this cable modem's serial port, and it appears to be
running eCos (GPL'd). I did not receive a copy of the GPL, nor source code or
an offer for such. I also have not located any sign of said source after a
few minutes of Googling around.
My goal is to port Linux to this cable modem, so please keep me informed and
possibly involved to some extent in enforcement, as I will be able to benefit
from the eCos code for my port.
Thanks,
Luke
next reply other threads:[~2008-06-15 4:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-15 4:37 Luke -Jr [this message]
2008-06-15 9:30 ` Jonathan Larmour
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=200806142336.35465.luke@dashjr.org \
--to=luke@dashjr.org \
--cc=ecos-maintainers@ecos.sourceware.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).