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  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Date:	Sat, 18 Oct 2014 11:22:20 +0200
From:	Arnd Bergmann <arnd@...db.de>
To:	atull <atull@...nsource.altera.com>
Cc:	Steffen Trumtrar <s.trumtrar@...gutronix.de>,
	Dinh Nguyen <dinguyen@...nsource.altera.com>,
	Philipp Zabel <p.zabel@...gutronix.de>, dinh.linux@...il.com,
	grant.likely@...aro.org, robh+dt@...nel.org,
	devicetree@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH] reset: socfpga: use arch_initcall for early initialization

On Friday 10 October 2014 11:32:35 atull wrote:
> On Thu, 9 Oct 2014, Steffen Trumtrar wrote:
> > Do you have an example where this is really needed?
> 
> My last version of the fpga manager framework 
> (https://lkml.org/lkml/2014/8/1/518)
> added fpga_mgr_firmware_write().  This can be called from a device driver's 
> probe function to request a fpga image be loaded.  I want to support FPGA 
> based functionality being seen pretty similar to really hard hardware.  So 
> the FPGA could have a PCI bus or something else that would want to be 
> early.

Please be more specific. I agree we need a good reason for not just
using deferred probing, and PCI host bridges in general are no longer
something that needs to be probed early.

If you have a particular use case in mind that can't be solved in a
better way, we can talk about making this an earlier initcall (probably
not arch_initcall), but in general we try hard to avoid new ones
like this.

	Arnd
--
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/

Powered by blists - more mailing lists