From: Meelis Roos <mroos@linux.ee>
To: Chas Williams <chas@cmf.nrl.navy.mil>
Cc: netdev@vger.kernel.org
Subject: Fore 200 firmware
Date: Mon, 31 May 2010 11:06:31 +0300 (EEST) [thread overview]
Message-ID: <alpine.SOC.1.00.1005311058180.2805@math.ut.ee> (raw)
Hello,
commit 9c54004ea717116a10886e254e26502ffb1136e9 (atm: [fore200e]
convert to use request_firmware()) made the fore driver user
request_firmware() but also removed the building of firmware image.
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.
Should we move the firmware to linux-firmware repository and remove
drivers/atm/fore200e_pca_fw.c or should we convert and install the
firmware in kernel build system?
--
Meelis Roos (mroos@linux.ee)
next reply other threads:[~2010-05-31 8:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-31 8:06 Meelis Roos [this message]
2010-06-01 14:37 ` Fore 200 firmware 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
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.1005311058180.2805@math.ut.ee \
--to=mroos@linux.ee \
--cc=chas@cmf.nrl.navy.mil \
--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