Stephen Hemminger wrote:
On Fri, 01 Dec 2006 20:45:51 +0300
Alexey Starikovskiy <[EMAIL PROTECTED]> wrote:
Linus Torvalds wrote:
On Fri, 1 Dec 2006, Pavel Machek wrote:
So it looks like we need this sequence:
enable_nonboot_cpus() /* INIT */
finish()/* _WAK */
devi
On Fri, 01 Dec 2006 20:45:51 +0300
Alexey Starikovskiy <[EMAIL PROTECTED]> wrote:
> Linus Torvalds wrote:
> > On Fri, 1 Dec 2006, Pavel Machek wrote:
> >
> >
> So it looks like we need this sequence:
>
> enable_nonboot_cpus() /* INIT */
> finish() /* _WAK */
> device_re
Linus Torvalds wrote:
On Fri, 1 Dec 2006, Pavel Machek wrote:
So it looks like we need this sequence:
enable_nonboot_cpus() /* INIT */
finish()/* _WAK */
device_resume()
Can somebody remind me about this immediately after 2.6.19?
Remind. But note that freezer is no
On Fri, 1 Dec 2006, Pavel Machek wrote:
> > > So it looks like we need this sequence:
> > >
> > > enable_nonboot_cpus() /* INIT */
> > > finish() /* _WAK */
> > > device_resume()
> >
> > Can somebody remind me about this immediately after 2.6.19?
>
> Remind. But note that freezer is not yet
Hi,
On Friday, 1 December 2006 11:57, Pavel Machek wrote:
> Hi!
>
> > > > > So it looks like we need this sequence:
> > > > >
> > > > > enable_nonboot_cpus() /* INIT */
> > > > > finish() /* _WAK */
> > > > > device_resume()
> > > >
> > > > Can somebody remind me about this immediately aft
Hi!
> > > > So it looks like we need this sequence:
> > > >
> > > > enable_nonboot_cpus() /* INIT */
> > > > finish()/* _WAK */
> > > > device_resume()
> > >
> > > Can somebody remind me about this immediately after 2.6.19?
> >
> > Remind. But note that freezer is not yet SMP safe... Ra
Hi,
On Friday, 1 December 2006 10:33, Pavel Machek wrote:
> Hi!
>
> > > So it looks like we need this sequence:
> > >
> > > enable_nonboot_cpus() /* INIT */
> > > finish() /* _WAK */
> > > device_resume()
> >
> > Can somebody remind me about this immediately after 2.6.19?
>
> Remind. But note
On Friday, 1 December 2006 02:48, Stephen Hemminger wrote:
> On Wed, 15 Nov 2006 02:03:30 -0500
> Len Brown <[EMAIL PROTECTED]> wrote:
>
> > On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote:
> > > If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2
> > > driver,
> > > t
Hi!
> > So it looks like we need this sequence:
> >
> > enable_nonboot_cpus() /* INIT */
> > finish()/* _WAK */
> > device_resume()
>
> Can somebody remind me about this immediately after 2.6.19?
Remind. But note that freezer is not yet SMP safe... Rafael is working
on that.
On Wed, 15 Nov 2006 02:03:30 -0500
Len Brown <[EMAIL PROTECTED]> wrote:
> On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote:
> > If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 driver,
> > the first interrupt gets misrouted to the original shared IRQ, rather than
> >
On Wed, 15 Nov 2006, Len Brown wrote:
>
> So it looks like we need this sequence:
>
> enable_nonboot_cpus() /* INIT */
> finish() /* _WAK */
> device_resume()
Can somebody remind me about this immediately after 2.6.19?
No way am I going to make that kind of a major ordering change right
On Wednesday, 15 November 2006 08:03, Len Brown wrote:
> On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote:
> > If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 driver,
> > the first interrupt gets misrouted to the original shared IRQ, rather than
> > to the MSI irq exp
On Tuesday 14 November 2006 18:30, Stephen Hemminger wrote:
> If I do a suspend-to-ram then resume on a Sony Vaio laptop with sky2 driver,
> the first interrupt gets misrouted to the original shared IRQ, rather than
> to the MSI irq expected.
>
> During the pci_restore process, the MSI information
13 matches
Mail list logo