linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Segher Boessenkool <segher@kernel.crashing.org>
To: Hollis Blanchard <hollisb@us.ibm.com>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>
Subject: Re: [patch] fix RTC/NVRAM accesses on Maple
Date: Fri, 26 May 2006 01:07:35 +0200	[thread overview]
Message-ID: <0EC3795C-A385-4ACE-9C2C-9F413DAF04AD@kernel.crashing.org> (raw)
In-Reply-To: <1148593014.15517.32.camel@basalt.austin.ibm.com>

>> Care to redo the patch?
>
> After some offline discussion, I think we're in agreement that these
> properties are fine, since Linux's device tree code can't handle
> multiple ranges. Right Segher?

Not fine, but good enough for now, will need more work elsewhere
before we can do "the right thing" here.

> Hollis Blanchard
> IBM Linux Technology Center
>
> Due to a firmware device tree bug, RTC and NVRAM accesses (including
> halt/reboot) on Maple have been broken since January, when an untested
> build fix went in. This code patches the device tree in Linux.
>
> Signed-off-by: Hollis Blanchard <hollisb@us.ibm.com>
Signed-off-by: Segher Boessenkool <segher@kernel.crashing.org>

  reply	other threads:[~2006-05-25 23:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-05-18 21:34 [patch] fix RTC/NVRAM accesses on Maple Hollis Blanchard
2006-05-18 22:58 ` Paul Mackerras
2006-05-19  2:25   ` Hollis Blanchard
2006-05-25 21:36   ` Hollis Blanchard
2006-05-25 23:07     ` Segher Boessenkool [this message]
2006-05-30 10:39     ` jfaslist
2006-05-30 11:38       ` Segher Boessenkool
2006-05-30 13:49         ` jfaslist
2006-05-30 19:21           ` Hollis Blanchard
2006-05-18 23:53 ` Segher Boessenkool

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=0EC3795C-A385-4ACE-9C2C-9F413DAF04AD@kernel.crashing.org \
    --to=segher@kernel.crashing.org \
    --cc=hollisb@us.ibm.com \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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;
as well as URLs for NNTP newsgroup(s).