Bug 242991 - Pull aic94xx firmware out of the kernel.
Summary: Pull aic94xx firmware out of the kernel.
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: kernel   
(Show other bugs)
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Jon Masters
QA Contact: Martin Jenner
Depends On:
Blocks: 425461
TreeView+ depends on / blocked
Reported: 2007-06-06 20:35 UTC by Tom Coughlan
Modified: 2007-12-14 21:30 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-11-12 21:18:53 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Removes firmware, and adds loading support to aic94xx (124.38 KB, patch)
2007-06-06 21:08 UTC, Ryan Powers
no flags Details | Diff

Description Ryan Powers 2007-06-06 20:35:53 UTC
The aic94xx firmware has been removed from the upstream kernel. The ability to
load firmware at boot and install time is being added to RHEL5, so the firmware
here should be removed, and packaged outside of the kernel.

Comment 1 Ryan Powers 2007-06-06 21:08:26 UTC
Created attachment 156391 [details]
Removes firmware, and adds loading support to aic94xx

This is a preliminary patch that I generated to remove the firmware from the
kernel, and add the loading support. These changes all came from upstream.
However, at the time I generated this, and still currently, I do not have a way
to test this, as the only system with an aic94xx device boots from it. There
have been two upstream patches to handle newer firmwares from Adaptec that are
not integrated in this.

Comment 2 Red Hat Bugzilla 2007-10-23 15:30:45 UTC
User rpowers@redhat.com's account has been closed

Comment 3 Red Hat Bugzilla 2007-10-23 15:30:50 UTC
User rpowers@redhat.com's account has been closed

Comment 5 Jon Masters 2007-11-12 21:18:53 UTC
We support external firmware packaging in RHEL5, but not for certain in-box
kernel drivers at this stage. These can still be updated, using the driver
update program to replace the entire driver and firmware (which may be replaced
with an external firmware file, it need not be built into the driver any more)
in one go.

It is planned to address this ahead of the next major product release, and we
are also willing to discuss this issue further if it becomes very serious.


Note You need to log in before you can comment on or make changes to this bug.