From: Murray Jensen <Murray.Jensen@csiro.au>
To: linuxppc-embedded@lists.linuxppc.org
Subject: Re: [PATCH] Hymod board support and related changes ...
Date: Wed, 29 May 2002 12:07:16 +1000 [thread overview]
Message-ID: <23587.1022638036@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from Tom Rini <trini@kernel.crashing.org> of "Tue, 28 May 2002 13:19:57 MST." <20020528201957.GB5997@opus.bloom.county>
On Tue, 28 May 2002 13:19:57 -0700, Tom Rini <trini@kernel.crashing.org> writes:
>On Tue, May 28, 2002 at 01:18:10PM -0700, Tom Rini wrote:
>>
>> On Tue, May 28, 2002 at 03:48:35PM +1000, Murray Jensen wrote:
>>
>> > - Hymod board support
>>
>> For the m8260_gorom() call, try using spin_lock_irqsave() instead of
>> save_flags();cli() ... restore_flags();
>
>Nevermind, spoke too soon here. But did you really need to add in what
>you did or is it just a cleanup?
I needed to add it. When I executed a "halt" on my Hymod board, at the point
where it jumped to the ROM (in my case, this is ppcboot) things went crazy -
it caught an exception and tried to print a message on the console, but it was
really wierd, with only a few of the characters legible, others being
substituted with wierd umlauts or punctuation etc. I couln't see any pattern,
but when I turned off interrupts before executing the "gorom" function it
stopped. Note that this only started happening recently, so something changed
somewhere else which caused this problem.
The idea behind this fix is "correct" anyway. We do not want to take any
exceptions once we have jumped to the boot ROM code. With the code the way it is,
it is possible for interrupts to be enabled at the time the "gorom" function is
executed.
Maybe the proper fix is for "gorom" to ensure interrupts are disabled? Cheers!
Murray...
--
Murray Jensen, CSIRO Manufacturing Sci & Tech, Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
Internet: Murray.Jensen@csiro.au
Hymod project: http://www.msa.cmst.csiro.au/projects/Hymod/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-29 2:07 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 5:48 [PATCH] Hymod board support and related changes Murray Jensen
2002-05-28 19:26 ` Tom Rini
2002-05-29 2:10 ` Murray Jensen
2002-05-28 20:18 ` Tom Rini
2002-05-28 20:19 ` Tom Rini
2002-05-29 2:07 ` Murray Jensen [this message]
2002-05-29 14:36 ` Tom Rini
-- strict thread matches above, loose matches on Subject: below --
2002-05-28 5:45 [PATCH] misc compiler warn/err fixes, typo fixes and aesthetic changes Murray Jensen
2002-05-28 18:35 ` Tom Rini
2002-05-29 1:42 ` Murray Jensen
2002-06-03 15:00 ` Tom Rini
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=23587.1022638036@msa.cmst.csiro.au \
--to=murray.jensen@csiro.au \
--cc=linuxppc-embedded@lists.linuxppc.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 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).