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: <CAErSpo6Xxq_kcEYACKUsuNDOJDhEDnxWgBUateOJEBcfqufhSg@mail.gmail.com>
Date:	Thu, 21 Jun 2012 21:30:49 -0600
From:	Bjorn Helgaas <bhelgaas@...gle.com>
To:	Stanislaw Gruszka <sgruszka@...hat.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 Tue, May 29, 2012 at 3:21 AM, Stanislaw Gruszka <sgruszka@...hat.com> wrote:
> 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

Kamil, any news on this issue?
--
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/