linux-kernel - Re: Initializing iwl3945 error

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]

Message-ID: <20120529092154.GA2441@redhat.com>
Date:	Tue, 29 May 2012 11:21:56 +0200
From:	Stanislaw Gruszka <sgruszka@...hat.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	Kamil Grzebien <ciptok@...il.com>, linux-pci@...r.kernel.org,
	linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: Initializing iwl3945 error

On Mon, May 28, 2012 at 12:21:34PM -0600, Bjorn Helgaas wrote:
> linked in vs. loaded as a module after boot?  What if you add a long
> delay in the driver probe routine?

I'm attaching patch which add 200 ms delay after pci_enable_device() in
->probe routine.

Stanislaw

View attachment "iwl3945_pci_probe_delay.patch" of type "text/plain" (446 bytes)