QLogic is producing a variant of the standard 4 Gb/S fibre channel card which is about to start shipping. This card uses the standard qla24xx hardware but contains an ethernet router downstream from the Fibre Channel part. The system just sees the standard HBA, but it is identified by a different PCI ID, which requires changing the driver code. The driver changes are simple, mostly handling the different PCI ID. The ioctl module is also changed to provide management, this module is not supported by RedHat. No firmware changes are required.
(In reply to comment #0) > this module is not supported by RedHat. Just FYI, if we ship it we support it. Kernel freeze is today...
So if this is just a PCI ID addition, is this bug only for QE purposes, since this should get dragged in automatically from SourceForge?
It is more then a PCI ID addition. Basically every if statement based on PCI ID also needs to account for this new board. So a new macro was defined to cover this and inserted thru the code. There are also some additional data structures and support code specific to the board, but which shouldn't impact the standard board. Plus there is additional code for the management in the ioctl() module, which RedHat doesn't support.
I *thought* you didn't support ioctl module, sorry. It's confusing...
(In reply to comment #2) > So if this is just a PCI ID addition, is this bug only for QE purposes, since > this should get dragged in automatically from SourceForge? Andrius, PCI IDs show up in two places: in the kernel device drivers, and in userspace. We get the userspace update from SourceForge as one of the last steps in the release. That is easy, and by the way, not critical to the operation of the system (it makes nicer displays in lspci, and the like). The driver part is critical. But out of curiosity, QLogic, are the new IDs registered at SourceForge?
Also, when are we slated to get these cards in house?
The cards are available soon, but they don't work without appropriate switches and those are un- obtainable made by Nuova ( Cisco ), not QLogic.
Re #5: Yes, http://pci-ids.ucw.cz/iii/?i=10778432. Re #6: I believe that was an action item of the QTR. Dave/Sameer are working to make that happen.
Created attachment 301744 [details] ISP84xx support
Created attachment 301745 [details] ISP84xx IOCTL support
Committed in 68.33.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
~~~~~~~~~~~~~~ ~ Attention: ~ Feedback requested regarding this **High Priority** bug. ~~~~~~~~~~~~~~ A fix for this issue should be included in the latest packages contained in RHEL4.7-Snapshot1--available now on partners.redhat.com. After you (Red Hat Partner) have verified that this issue has been addressed, submit a comment describing the passing results of your test in appropriate detail, along with which snapshot and package version tested. The bugzilla will be updated by Red Hat Quality Engineering for you when this information has been received. If you believe this issue has not properly fixed or you are unable to verify the issue for any reason, please add a comment describing the most recent issues you are experiencing, along with which snapshot and package version tested. If you believe the bug has not been fixed, change the status of the bug to ASSIGNED. If you are receiving this message in Issue Tracker, please reply with a message to Issue Tracker about your results and bugzilla will be updated for you. If you need assistance accessing ftp://partners.redhat.com, please contact your Partner Manager. Thank you Red Hat QE Partner Management
~~~~~~~~~~~~~~ ~ Attention: ~ Immediate attention required for this ***High Priority*** bug. ~~~~~~~~~~~~~~ A fix for this issue should be included in the latest packages contained in **RHEL4.7-Snapshot2**, accessible now on http://partners.redhat.com. After you (Red Hat Partner) have verified that this issue has been addressed, submit a comment describing the results of your test in appropriate detail, along with which snapshot and package version tested. The bugzilla will be updated by Red Hat Quality Engineering for you when this information has been received. If this issue has not been properly fixed or you are unable to verify the issue for any reason, please add a comment describing the most recent issues you are experiencing, along with which snapshot and package version tested. If you are sure the bug has not been fixed, change the status of the bug to ASSIGNED. For IssueTracker users, submit verification results as usual; Bugzilla will be updated by Red Hat Quality Engineering for you. For additional information, contact your Partner Manager. Thank you, Red Hat QE Partner Management
These support verified in kernel-2.6.9-73.EL
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2008-0665.html
Partners, I would like to thank you all for your participation in assuring the quality of this RHEL 4.7 Update Release. My hat's off to you all. Thanks.