From: Jun Sun <jsun@mvista.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Ladislav Michl <ladis@psi.cz>, Ralf Baechle <ralf@uni-koblenz.de>,
linux-mips@oss.sgi.com
Subject: Re: [patch] linux: DBE/IBE handling rewrite
Date: Wed, 26 Jun 2002 10:17:28 -0700 [thread overview]
Message-ID: <3D19F728.7020903@mvista.com> (raw)
In-Reply-To: Pine.GSO.3.96.1020626121553.23599A-100000@delta.ds2.pg.gda.pl
I suggest we have a function pointer called board_bus_error_init, which is
initialized to a NULL function. Any board that wishes to override it can do
so in <board>_setup() routine.
With more amd more MIPS boards poping up, the more friendly board interface is
the better.
Jun
Maciej W. Rozycki wrote:
> On Tue, 25 Jun 2002, Maciej W. Rozycki wrote:
>
>
>> This way, the fixup search is invoked first and a system-specific handler
>>can judge whether to let the fixup be invoked or a serious failure
>>happened and the system should act appropriately. The handler can do
>>whatever actions are needed (e.g. clear error status data in system
>>registers, report ECC syndromes, etc.) for the system for both cases.
>>
>
> OK, here is the code. I wrote it a bit differently from what I
> considered yesterday, as fixup doesn't seem useful for a system-specific
> handler. With the following code only a boolean flag is passed informing
> whether a fixup is available and the handler can decide how to treat an
> error, based on the state passed as arguments and possibly additional one
> obtained from system-specific resources. Both MIPS and MIPS64 are handled
> in the same way. For MIPS64 it means a removal of duplicated similar code
> as well. I adjusted some SGI-specific code appropriately, but platform
> maintainers will have to check if bus_error_init() stubs are OK for them.
>
> Ralf, OK to apply?
>
> Maciej
>
>
next prev parent reply other threads:[~2002-06-26 17:20 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-17 11:33 DBE/IBE handling incompatibility Ladislav Michl
2002-06-19 16:47 ` Maciej W. Rozycki
2002-06-25 0:36 ` Ladislav Michl
2002-06-25 11:55 ` Maciej W. Rozycki
2002-06-26 11:51 ` [patch] linux: DBE/IBE handling rewrite Maciej W. Rozycki
2002-06-26 12:05 ` Ralf Baechle
2002-06-26 13:07 ` Maciej W. Rozycki
2002-06-26 17:21 ` Jun Sun
2002-06-27 12:00 ` Maciej W. Rozycki
2002-06-27 17:12 ` Jun Sun
2002-06-27 18:29 ` Maciej W. Rozycki
2002-06-27 19:08 ` Jun Sun
2002-06-27 20:00 ` Maciej W. Rozycki
2002-06-26 20:59 ` [patch] GIO bus support Ladislav Michl
2002-06-26 23:46 ` Ralf Baechle
2002-06-27 10:14 ` FIR problem jeff
2002-06-27 10:14 ` jeff
2002-06-27 12:21 ` [patch] GIO bus support Maciej W. Rozycki
2002-08-04 22:03 ` Ladislav Michl
2002-09-28 19:55 ` Ladislav Michl
2002-06-26 17:17 ` Jun Sun [this message]
2002-06-27 11:51 ` [patch] linux: DBE/IBE handling rewrite Maciej W. Rozycki
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=3D19F728.7020903@mvista.com \
--to=jsun@mvista.com \
--cc=ladis@psi.cz \
--cc=linux-mips@oss.sgi.com \
--cc=macro@ds2.pg.gda.pl \
--cc=ralf@uni-koblenz.de \
/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.