linux-kernel - Re: getting configuration info into a driver at load-time

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 28 Oct 2008 09:21:08 +0000
From:	Alan Cox <alan@...rguk.ukuu.org.uk>
To:	Sebastian Kuzminsky <seb@...hlab.com>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: getting configuration info into a driver at load-time

> I thought about exposing this config structure in /sys or /proc (in a 
> per-board directory), and let the user poke in the config values after 
> the driver has loaded, but I'd really prefer to make the information 
> available at load-time.

Various drivers do load it after load time (and for one that allows you
to change the configuration without a restart which is usually a good
thing). In some cases driver that need a configuration to do sane things
fails other I/O with an error like EIO until a configuration is
established via ioctl or sysfs or similar.
 
> Currently the driver has a module param array of char*, with each 
> board's configuration encoded into an ascii string which gets decoded 
> "by hand" in the driver.  Pretty grotty.
> 
> Is there some easier/cleaner way to do this?

You can always request_firmware() the tables... bit hackish but works

Alan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/