From: Takeharu KATO <takeharu1219@ybb.ne.jp>
To: Glenn Burkhardt <glenn@aoi-industries.com>
Cc: galak@freescale.com, linuxppc-embedded@ozlabs.org
Subject: Re: PPC 44x Watchdog timer
Date: Thu, 05 May 2005 11:07:26 +0900 [thread overview]
Message-ID: <42797FDE.7080909@ybb.ne.jp> (raw)
In-Reply-To: <200504200802.45998.glenn@aoi-industries.com>
Hi
Glenn Burkhardt wrote:
> watchdog exception interrupt isn't used, and it's only configurable for
> PPC405 (although I think that the technique would work for the whole 4xx
> family).
>
> Or am I misreading the code?
>
No, the kernel which I mentioned before is MontaVistaLinux.
IIRC, I look the WDT relevant codes in MontaVistaLinux2.X few years ago.
Of course, It was prepared for PowerPC40X...
> It would also be nice if your patch were applied to the 2.6 kernel tree.
>
Sorry, It's not my jurisdiction.
Matt(Porter) or Kumar(Gala) may be responsible for this work.
#Finally, the patch should be approved by akpm and linus, of course...
Matt or Kumar, would you merge BOOKE_WDT patch to 2.6 kernel tree?
IIRC, This patch has been left under review state about two month.
Is there something to be needed for the patch?
next prev parent reply other threads:[~2005-05-05 2:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-19 1:37 PPC 44x Watchdog timer Glenn Burkhardt
2005-04-20 11:35 ` Takeharu KATO
2005-04-20 12:02 ` Glenn Burkhardt
2005-05-05 2:07 ` Takeharu KATO [this message]
2005-05-05 14:02 ` Kumar Gala
2005-05-05 21:43 ` Takeharu KATO
2005-05-06 21:04 ` [PATCH] BOOKE_WDT Part 1/2 (Re: PPC 44x Watchdog timer) Takeharu KATO
2005-05-12 15:37 ` Kumar Gala
2005-05-16 6:57 ` Takeharu KATO
2005-05-17 1:21 ` Kumar Gala
2005-05-17 5:59 ` Takeharu KATO
2005-05-17 14:47 ` Takeharu KATO
2005-05-17 17:00 ` Kumar Gala
2005-05-17 17:41 ` Takeharu KATO
2005-05-06 21:04 ` [PATCH] BOOKE_WDT Part 2/2 " Takeharu KATO
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=42797FDE.7080909@ybb.ne.jp \
--to=takeharu1219@ybb.ne.jp \
--cc=galak@freescale.com \
--cc=glenn@aoi-industries.com \
--cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.