Re: [RFC net-next 0/3] devconf: New infrastructure for setting pre-load parameters for a module

[Amir Vadai <amirv@mellanox.com>]

On Thu, Jan 8, 2015 at 9:25 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> On Thu, Jan 08, 2015 at 09:14:32PM +0200, Amir Vadai wrote:
>> On Thu, Jan 8, 2015 at 7:47 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
>> > On Thu, Jan 08, 2015 at 07:11:04PM +0200, Amir Vadai wrote:
>> >> On 1/8/2015 6:46 PM, Greg KH wrote:
>> >> > On Thu, Jan 08, 2015 at 05:16:57PM +0200, Hadar Hen Zion wrote:
>> >> >> Hi,
>> >> >>
>> >> >> When configuring a device at an early boot stage, most kernel drivers
>> >> >> use module parameters (the parameters' settings can be determined in
>> >> >> modprobe.d config files).
>> >> >
>> >> > Which is a bad idea, as you have learned :)

[...]

>
> But you are talking about loading config info before the driver is
> loaded, which goes backwards for how we automatically load modules when
> the hardware is found.

I guess you're a busy man and getting tired of my nudges. And it is ok
with us to make it a non-generic solution - so I won't bother you much
more...
I would like to understand the arguments here: Maybe there is a
history that I missed - What are the arguments against having a config
info before the driver is loaded? Assuming, that it will make the
driver loading process simpler and faster.

Thanks,
Amir