Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751613AbdLBGjL (ORCPT ); Sat, 2 Dec 2017 01:39:11 -0500 Received: from gherkin.frus.com ([192.158.254.49]:44070 "EHLO gherkin.frus.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751367AbdLBGjK (ORCPT ); Sat, 2 Dec 2017 01:39:10 -0500 Date: Sat, 2 Dec 2017 00:39:09 -0600 From: Bob Tracy To: linux-kernel@vger.kernel.org Subject: 4.14.0: built-in drivers now require built-in firmware? Message-ID: <20171202063909.GA25253@gherkin.frus.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.6.1 (2016-04-27) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1647 Lines: 33 The subject question is due to trouble encountered on a DEC Alpha getting the 4.14.0 kernel to see the machine's SCSI disks at boot time. I'm using the standard kernel source tree, and have long made it a practice to build-in the drivers for devices required at boot time (such as for the video card and local disks). For as far back as I can remember, I've had to build-in the firmware for the video card to get the console working properly. Up through kernel version 4.13, I had not had to build-in the firmware for my machine's Qlogic ISP1020 host adapter. Beginning with 4.14, the host adapter was no longer being detected and initialized. Adding the appropriate firmware file to the list of built-in firmware fixed the issue. Is there a way to adjust the kernel configuration process to account for this evidently new dependency? The immediate problem I see is the mapping between drivers and associated firmware files is not necessarily one-to-one. In the case of the "qla1280" driver, there are three associated firmware images: the image corresponding to the host adapter present at boot time is required to be built-in if the "qla1280" driver is built-in. The "radeon" video driver has a *much* longer list of firmware files to select from. Since the presence of appropriate firmware files on the kernel build system isn't guaranteed, perhaps the best thing to do is have the configuration script/program issue a warning message about firmware for devices whose drivers are built-in rather than built as modules. This is presumably a non-issue for people who run distro-provided kernels where everything is modularized. --Bob