[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CANHD2=o-eyd2JR7oK4gJgQi3Mi-a=R1RKuGsuWzzR_WosQaNEA@mail.gmail.com>
Date: Sun, 1 Jul 2012 19:01:58 +0100
From: Kamil Grzebien <ciptok@...il.com>
To: Bjorn Helgaas <bhelgaas@...gle.com>
Cc: Stanislaw Gruszka <sgruszka@...hat.com>, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-wireless@...r.kernel.org
Subject: Re: Initializing iwl3945 error
Hi Bjorn,
Sorry for delay, was is almost one month holiday.
I haven't tried your patch yet, but wanted to share with one thing.
Currently I use new kernel 3.4.3, where the problem doesn't exist
anymore. However I still would like to know what was the cause and
which change brought the solution. Is there anything which comes to
your mind in terms of recent changes in kernel? I also added logs from
the newest kernel, so it might be easier for track it.
Best Regards,
Kamil Grzebien
On Fri, Jun 22, 2012 at 4:30 AM, Bjorn Helgaas <bhelgaas@...gle.com> wrote:
> 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?
Download attachment "iwl3945_kernel-3.4.3.tar.gz" of type "application/x-gzip" (21110 bytes)
Powered by blists - more mailing lists