From: Meelis Roos <mroos@linux.ee>
To: chas3@users.sourceforge.net
Cc: netdev@vger.kernel.org
Subject: Re: Fore 200 firmware
Date: Tue, 1 Jun 2010 19:09:17 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1006011902490.22519@math.ut.ee> (raw)
In-Reply-To: <201006011549.o51FnZFk028507@thirdoffive.cmf.nrl.navy.mil>
> >does not have to redo the detective work I am doing. Packaging it along
> >with linux-atm packages (atm-tools in Debian) does not seem correct, so
> >do we need to make a special firmware package out of it or just add to
> >some other firmware repo that is packaged already?
>
> i dont care which happens really. i would to think it is part of
> atm-tools since the fore200e driver really isnt useful with the
> atm tools.
OK, so we should push the distro maintainers of it to create a suggested
firmware package or just include the fore firmware unconditionally -
once it is in released linux-atm.
> >What's the licence of the firmware anyway - unknown likely?
>
> it says the firmware is gpl. look at fore200e_firmware_copyright
> in one of the old kernel distros.
Well, there is no source to fulfill the GPL... but there also should be
no problem redistributing it.
> >And we can probably remove drivers/atm/fore200e_pca_fw.c if we
> >distribute the firmware out of kernel tree.
>
> i dont think it is in the current net-next-2.6 tree?
Oops, you are right - I have updated my tree over several years and the
old files were just not removed from disk. But theay are gone from the
git, yes.
Thnak yo for your work on ATM - I intend to get a demo ATM network
running here in my computer museum.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2010-06-01 16:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 8:06 Fore 200 firmware Meelis Roos
2010-06-01 14:37 ` Chas Williams (CONTRACTOR)
2010-06-01 14:52 ` Meelis Roos
2010-06-01 15:49 ` Chas Williams (CONTRACTOR)
2010-06-01 16:09 ` Meelis Roos [this message]
2010-06-01 17:12 ` Ben Hutchings
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=alpine.SOC.1.00.1006011902490.22519@math.ut.ee \
--to=mroos@linux.ee \
--cc=chas3@users.sourceforge.net \
--cc=netdev@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