Linux MIPS Architecture development
 help / color / mirror / Atom feed
From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Marc St-Jean <stjeanma@pmc-sierra.com>
Cc: linux-mips@linux-mips.org
Subject: Re: [PATCH 2/5] mips: PMC MSP71xx mips common
Date: Fri, 23 Feb 2007 23:35:32 +0300	[thread overview]
Message-ID: <45DF5014.8020503@ru.mvista.com> (raw)
In-Reply-To: <200702231956.l1NJu4Zd032458@pasqua.pmc-sierra.bc.ca>

Hello.

Marc St-Jean wrote:

> [PATCH 2/5] mips: PMC MSP71xx mips common

> Patch to add mips common support for the PMC-Sierra
> MSP71xx devices.

> These 5 patches along with the previously posted serial patch
> will boot the PMC-Sierra MSP7120 Residential Gateway board.

> Signed-off-by: Marc St-Jean <Marc_St-Jean@pmc-sierra.com>

> diff --git a/arch/mips/Kconfig b/arch/mips/Kconfig
> index 5da6b0d..d512389 100644
> --- a/arch/mips/Kconfig
> +++ b/arch/mips/Kconfig
[...]

> +menu "Options for PMC-Sierra MSP chipsets"
> +	depends on PMC_MSP
> +
> +config PMC_MSP_EMBEDDED_ROOTFS
> +	bool "Root filesystem embedded in kernel image"
> +	select MTD
> +	select MTD_BLOCK
> +	select MTD_PMC_MSP_RAMROOT
> +	select MTD_RAM
> +

    Hm, why not just use initramfs?

> +config PMC_MSP_UNCACHED
> +	bool "Run uncached"
> +	select MIPS_UNCACHED
> +	
> +endmenu
> +

    Erm, was there really a need for separate option?

> diff --git a/arch/mips/kernel/traps.c b/arch/mips/kernel/traps.c
> index 18f56a9..610e169 100644
> --- a/arch/mips/kernel/traps.c
> +++ b/arch/mips/kernel/traps.c
> @@ -70,6 +70,7 @@ extern asmlinkage void handle_reserved(void);
>  extern int fpu_emulator_cop1Handler(struct pt_regs *xcp,
>  	struct mips_fpu_struct *ctx, int has_fpu);
>  
> +void (*board_watchpoint_handler)(struct pt_regs *regs);
>  void (*board_be_init)(void);
>  int (*board_be_handler)(struct pt_regs *regs, int is_fixup);
>  void (*board_nmi_handler_setup)(void);
> @@ -860,13 +861,17 @@ asmlinkage void do_mdmx(struct pt_regs *regs)
>  
>  asmlinkage void do_watch(struct pt_regs *regs)
>  {
> -	/*
> -	 * We use the watch exception where available to detect stack
> -	 * overflows.
> -	 */
> -	dump_tlb_all();
> -	show_regs(regs);
> -	panic("Caught WATCH exception - probably caused by stack overflow.");
> +	if (board_watchpoint_handler) {
> +		(*board_watchpoint_handler)(regs);
> +	} else {
> +		/*
> +		 * We use the watch exception where available to detect stack
> +		 * overflows.
> +		 */
> +		dump_tlb_all();
> +		show_regs(regs);
> +		panic("Caught WATCH exception - probably caused by stack overflow.");
> +	}
>  }

    There was no real need for else and massive change, just add return right 
after calling the handler...

WBR, Sergei

  reply	other threads:[~2007-02-23 20:36 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-23 19:56 [PATCH 2/5] mips: PMC MSP71xx mips common Marc St-Jean
2007-02-23 20:35 ` Sergei Shtylyov [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-02-23 20:53 Marc St-Jean
2007-02-23 21:02 ` Sergei Shtylyov
2007-02-23 21:02 ` David Daney
2007-02-23 21:15 Marc St-Jean
2007-02-23 21:27 Marc St-Jean
2007-02-27  0:12 Marc St-Jean
2007-02-27  0:43 ` Andrew Sharp
2007-02-27 17:09 Marc St-Jean
2007-02-27 17:38 ` Thiemo Seufer
2007-02-28 19:32   ` Ralf Baechle
2007-02-27 18:46 ` Andrew Sharp
2007-02-28 19:42   ` Ralf Baechle
2007-02-27 17:59 Marc St-Jean
2007-02-27 20:03 ` Thiemo Seufer
2007-02-27 21:27 Marc St-Jean
2007-02-28 19:52 ` Ralf Baechle
2007-02-28  0:04 Marc St-Jean
2007-02-28 21:35 Marc St-Jean
2007-02-28 21:43 ` Uhler, Mike
2007-02-28 21:43   ` Uhler, Mike
2007-02-28 22:18 ` Ralf Baechle
2007-02-28 22:35 Marc St-Jean
2007-03-01 20:41 Marc St-Jean
2007-03-07 18:01 Marc St-Jean
2007-03-16  1:58 ` Ralf Baechle
2007-03-16 23:53 Marc St-Jean
2007-03-17  0:46 ` Ralf Baechle

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=45DF5014.8020503@ru.mvista.com \
    --to=sshtylyov@ru.mvista.com \
    --cc=linux-mips@linux-mips.org \
    --cc=stjeanma@pmc-sierra.com \
    /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