From: john stultz <johnstul@us.ibm.com>
To: Tsutomu OWA <tsutomu.owa@toshiba.co.jp>
Cc: linuxppc-dev@ozlabs.org, mingo@elte.hu,
Paul Mackerras <paulus@samba.org>,
linux-kernel@vger.kernel.org, tglx@linutronix.de
Subject: Re: [RFC PATCH 1/4] powerpc 2.6.16-rt17: to build on powerpc w/ RT
Date: Fri, 11 Aug 2006 10:56:23 -0700 [thread overview]
Message-ID: <1155318983.5337.2.camel@localhost.localdomain> (raw)
In-Reply-To: <yyiac6biz3c.wl@forest.swc.toshiba.co.jp>
On Fri, 2006-08-11 at 15:08 +0900, Tsutomu OWA wrote:
> > On Fri, 11 Aug 2006 15:11:47 +1000
> > Paul Mackerras <paulus@samba.org> said:
>
> > I would be very surprised if this is all that is required for
> > CONFIG_GENERIC_TIME to work correctly on powerpc. Have you verified
> > that the CONFIG_GENERIC_TIME stuff works correctly on powerpc and
> > provides all the features provided by the current implementation?
>
> Well, probably no as you say so.
>
> What I did for CONFIG_GENERIC_TIME is just to fix a compile
> error and to see if the kernel boots or not. As I mentioned,
> it's experimental and is posted to see whether I'm moving in the
> right direction or not.
>
> I'm afraid I have not yet looked into any generic time related
> features/implementations. Looks like generic time related things
> should be on the ToDo list.
You might take a peek at the patch set here:
http://sr71.net/~jstultz/tod/ for a somewhat rough powerpc conversion to
CONFIG_GENERIC_TIME.
thanks
-john
next prev parent reply other threads:[~2006-08-11 17:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-11 2:01 [RFC PATCH 1/4] powerpc 2.6.16-rt17: to build on powerpc w/ RT Tsutomu OWA
2006-08-11 5:11 ` Paul Mackerras
2006-08-11 6:08 ` Tsutomu OWA
2006-08-11 17:56 ` john stultz [this message]
2006-08-16 23:38 ` Benjamin Herrenschmidt
2006-08-17 0:00 ` john stultz
2006-08-17 0:26 ` Benjamin Herrenschmidt
2006-08-17 0:56 ` john stultz
2006-08-17 4:43 ` Benjamin Herrenschmidt
2006-08-21 10:01 ` Tsutomu OWA
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=1155318983.5337.2.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=mingo@elte.hu \
--cc=paulus@samba.org \
--cc=tglx@linutronix.de \
--cc=tsutomu.owa@toshiba.co.jp \
/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).