linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Kumar Gala <kumar.gala@freescale.com>
To: "Takeharu KATO" <takeharu1219@ybb.ne.jp>
Cc: Glenn Burkhardt <glenn@aoi-industries.com>,
	"Gala Kumar K.-galak" <galak@freescale.com>,
	linuxppc-embedded@ozlabs.org
Subject: Re: [PATCH] BOOKE_WDT Part 1/2 (Re: PPC 44x Watchdog timer)
Date: Mon, 16 May 2005 20:21:22 -0500	[thread overview]
Message-ID: <63792af268f18c480d5ecf218a4e61af@freescale.com> (raw)
In-Reply-To: <42884448.6040505@ybb.ne.jp>

No problem, can you replace all the cmd line parsing with early_param()=20=

code in arch/ppc/kernel/setup.c.  Take a look at=20
arch/ppc64/kernel/setup.c for an example.  We still need to add a call=20=

to parse_early_param() in setup_arch().

Matt & I need to talk about the driver patch.  Once I have more=20
feedback on that I'll let you know.  The major issue I have is having=20
the interrupt handler in drivers/char/watchdog/.. instead of=20
arch/ppc/kernel/traps.c.  However, I dont have a good idea how to=20
structure the changes.

- kumar

On May 16, 2005, at 1:57 AM, Takeharu KATO wrote:

> Hi Kumar:
>
> I'm sorry that the reply becomes slow.
>
> Kumar Gala wrote:
>  >>
>  >
> > Any reason you moved this code into DecrementerHandler?
> >
> >>=A0=A0 /* 0x1000 - Programmable Interval Timer (PIT) Exception */
>  >>=A0=A0=A0=A0=A0=A0=A0=A0=A0 START_EXCEPTION(0x1000, Decrementer)
>  >>=A0 -=A0=A0=A0=A0=A0=A0 NORMAL_EXCEPTION_PROLOG
> >> -=A0=A0=A0=A0=A0=A0 lis=A0=A0=A0=A0 r0,TSR_PIS@h
> >> -=A0=A0=A0=A0=A0=A0 mtspr=A0=A0 SPRN_TSR,r0=A0=A0=A0=A0=A0=A0=A0=A0=A0=
=A0=A0=A0 /* Clear the PIT exception=20
> */
>  >>=A0 -=A0=A0=A0=A0=A0=A0 addi=A0=A0=A0 r3,r1,STACK_FRAME_OVERHEAD
> >> -=A0=A0=A0=A0=A0=A0 EXC_XFER_LITE(0x1000, timer_interrupt)
> >> +=A0=A0=A0=A0=A0=A0 b=A0=A0=A0 DecrementerHandler
> >>
>  Current PIT exception handler is too big.
>  If it is not moved, compilation is failed with relocation error.
>  Because current PIT handler overwrites WDT handler's codes, the=20
> compiler
> can not relocate PIT and WDT handler correctly.

  reply	other threads:[~2005-05-17  1:21 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
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 [this message]
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=63792af268f18c480d5ecf218a4e61af@freescale.com \
    --to=kumar.gala@freescale.com \
    --cc=galak@freescale.com \
    --cc=glenn@aoi-industries.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=takeharu1219@ybb.ne.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).