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 17:52:23 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1006011747570.22519@math.ut.ee> (raw)
In-Reply-To: <201006011437.o51Ebp6f014332@thirdoffive.cmf.nrl.navy.mil>
> >So the current state is that drivers/atm contains the C dump of fore 200
> >firmware in drivers/atm/fore200e_pca_fw.c but this firmware is not built
> >and not installed by make install. It's also not present in
> >linux-firware tree/packages so the fore driver can not load its firmware
> >from anywhere. I guess this is not the intended outcome.
>
> this firmware is in the linux-atm source tree now. the 2.5.1 release
> should have the firmware.
2.5.1 does not seem to contain the firmware.
Even if it will be there in the next release, we should still do
something to distribute it to the user so that any modern distro has the
firmware available (in linux-firmware or via similar means) so the user
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?
What's the licence of the firmware anyway - unknown likely?
And we can probably remove drivers/atm/fore200e_pca_fw.c if we
distribute the firmware out of kernel tree.
--
Meelis Roos (mroos@linux.ee)
next prev parent reply other threads:[~2010-06-01 14:52 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 [this message]
2010-06-01 15:49 ` Chas Williams (CONTRACTOR)
2010-06-01 16:09 ` Meelis Roos
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.1006011747570.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