public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andrew Morton <akpm@osdl.org>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.11-rc3-mm2
Date: Fri, 11 Feb 2005 10:31:48 +1100	[thread overview]
Message-ID: <1108078309.7733.217.camel@gaston> (raw)
In-Reply-To: <20050210150208.315e9a76.akpm@osdl.org>

> > Without the aty128fb and radeonfb updates, current 2.6.11 is a
> > regression on pmac as it breaks sleep support on previously working
> > laptops.
> 
> Is that worse than the risk of the large patch?

Well, it used to work upstream fine for some time now... The large patch
isn't risky imho, at least in the latest version I sent you. The bulk of
the changes are just code to re-initialize new chip that isn't executed
at all on earlier models. The main radeonfb code changes very little. I
haven't had a failure report with the latest patch yet.

> > If you don't intend to get at least
> > try_to_acquire_console_sem() and aty128fb fix in, in which case i can
> > send you a minimal radeonfb patch, then I'll have to make another patch
> > for 2.6.11 that reverts some of the arch changes to re-enable sleep on
> > those machines.
> 
> Ho hum.  PM and fbdev are regularly broken anyway.  Please always identify
> the patches by name - it helps avoid mistakes.

Ahem ... not that badly broken on releases, I've been careful enough
that at least, powerbook sleep worked fine for some time now.
 
> These?
> 
> add-try_acquire_console_sem.patch
> update-aty128fb-sleep-wakeup-code-for-new-powermac-changes.patch

Those 2 first at least yes

> radeonfb-update.patch
> radeonfb-build-fix.patch

And either the above, or I can do a minimal patch on radeonfb just
restoring sleep on earlier models (adding the pmac_feature call to
notify the arch code that we can wakeup the chip) if you don't want to
merge the bigger update.

Ben.



  reply	other threads:[~2005-02-10 23:33 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-10 10:35 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 13:35 ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-10 20:01   ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-12 22:43   ` 2.6.11-rc3-mm2 Olaf Dietsche
2005-02-10 18:47 ` [patch] inotify for 2.6.11-rc3-mm2 Robert Love
2005-02-18 16:40   ` Robert Love
2005-02-18 17:24     ` Al Viro
2005-02-18 17:48       ` Robert Love
2005-02-10 19:20 ` [2.6.11-rc3-mm2 patch] mxser.c: remove unused variable Adrian Bunk
2005-02-10 22:13 ` 2.6.11-rc3-mm2 Corey Minyard
2005-02-10 22:42 ` 2.6.11-rc3-mm2 Benjamin Herrenschmidt
2005-02-10 23:02   ` 2.6.11-rc3-mm2 Andrew Morton
2005-02-10 23:31     ` Benjamin Herrenschmidt [this message]
2005-02-10 23:17 ` 2.6.11-rc3-mm2 Adrian Bunk
2005-02-11  6:14 ` 2.6.11-rc3-mm2 (compile stats) John Cherry
2005-02-11 16:29 ` 2.6.11-rc3-mm2 Yuval Tanny
2005-02-12 14:53   ` 2.6.11-rc3-mm2 Henning Rohde
2005-02-14 13:22 ` 2.6.11-rc3-mm2 Stefano Rivoir
  -- strict thread matches above, loose matches on Subject: below --
2005-02-10 20:51 2.6.11-rc3-mm2 Jack O'Quin
2005-02-11  0:04 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  0:47   ` 2.6.11-rc3-mm2 Chris Wright
2005-02-11  2:09     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  2:22       ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11  3:26         ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11  3:41           ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11  5:04             ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11  6:34               ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11  6:42                 ` 2.6.11-rc3-mm2 Nick Piggin
2005-02-11  5:09             ` 2.6.11-rc3-mm2 Peter Williams
2005-02-11  6:57             ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  7:54               ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  8:25                 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  8:48                   ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  8:58                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  9:01                       ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  9:04                   ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  9:27                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49                   ` 2.6.11-rc3-mm2 Paul Davis
2005-02-11 19:42                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 19:57                       ` 2.6.11-rc3-mm2 Lee Revell
2005-02-11  8:14       ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  8:22         ` 2.6.11-rc3-mm2 Christoph Hellwig
2005-02-11  8:41         ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  8:59           ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11  9:40             ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11  9:53               ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 17:37                 ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:49                   ` 2.6.11-rc3-mm2 Ingo Molnar
2005-02-11 20:10                     ` 2.6.11-rc3-mm2 Matt Mackall
2005-02-11 17:45           ` 2.6.11-rc3-mm2 Paul Davis
2005-02-14  5:21         ` 2.6.11-rc3-mm2 Werner Almesberger

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1108078309.7733.217.camel@gaston \
    --to=benh@kernel.crashing.org \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox