Return-path: Received: from shadbolt.e.decadent.org.uk ([88.96.1.126]:41966 "EHLO shadbolt.e.decadent.org.uk" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752204Ab3LQV1V (ORCPT ); Tue, 17 Dec 2013 16:27:21 -0500 Date: Tue, 17 Dec 2013 21:27:09 +0000 From: Ben Hutchings To: Sander Eikelenboom Cc: Julian Calaby , Arend van Spriel , "Luis R. Rodriguez" , Linus Torvalds , "Berg, Johannes" , "Grumbach, Emmanuel" , "linux-kernel@vger.kernel.org" , "ilw@linux.intel.com" , "netdev@vger.kernel.org" , "linux-wireless@vger.kernel.org" , "John W. Linville" , Avinash Patil Message-ID: <20131217212709.GB5624@decadent.org.uk> (sfid-20131217_222740_650670_8CBC65E8) References: <1342235583.20131211182804@eikelenboom.it> <871324710.20131211191104@eikelenboom.it> <1937118387.20131216122200@eikelenboom.it> <52AEE60B.6030509@broadcom.com> <19210260274.20131216135644@eikelenboom.it> <1534126119.20131217104548@eikelenboom.it> <387552477.20131217213319@eikelenboom.it> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii In-Reply-To: <387552477.20131217213319@eikelenboom.it> Subject: Re: [cfg80211 / iwlwifi] setting wireless regulatory domain doesn't work. Sender: linux-wireless-owner@vger.kernel.org List-ID: On Tue, Dec 17, 2013 at 09:33:19PM +0100, Sander Eikelenboom wrote: [...] > > It's the official Debian package. [...] > > I will report back when i have tested converting the wireless stuff to loadable modules / seeing if i can put the CRDA stuff in initrd. > > With all the wireless stuff switched to loadable modules it *does* work. > > So the problem is that: > The current code blocks all future regulatory domain setting attempts forever (till the next reboot) > when it can't find the CRDA. This can and does happen when the modules are compiled in and the CRDA is not in initrd. > > So from the question department: > > A) Why doesn't the code timeout the processing of a regulatory domain hint and remove the pending request when it aborts ? > B) Why isn't the CRDA treated as firmware and placed in /lib/firmware, which has a much greater chance of automagically appearing in initrd ? [...] It doesn't make any logical sense to put a userland program in /lib/firmware, and it wouldn't have any effect on the initramfs builders I'm familiar with (which look at module metadata to work out which files to include from /lib/firmware). Debian official kernels use modular drivers, and neither initramfs-tools nor dracut includes wireless drivers in the initramfs. If you build a custom kernel with built-in drivers then you most likely don't need an initramfs at all. As maintainer of crda in Debian, I could add an initramfs hook that would include it in an initramfs. But I don't understand why it would be worth doing so. Why is it so useful to have wireless drivers built-in *and* an initramfs? If you think I should do this then open a bug (reportbug crda). Ben. -- Ben Hutchings Life would be so much easier if we could look at the source code.