From: Frank Rowand <frank_rowand@mvista.com>
To: trini@mvista.com, linuxppc-dev@lists.linuxppc.org
Cc: frowand@mvista.com
Subject: patch - KGDB read and write of IO registers
Date: Fri, 21 Dec 2001 14:49:47 -0800 [thread overview]
Message-ID: <3C23BC8B.83D8F4DB@mvista.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 558 bytes --]
Tom,
Please apply the attached patch to linuxppc_2_4_devel.
The patch allows IO device registers to be accessed by KGDB via word
(or halfword) loads and stores for word (or halfword) sized objects
when naturally aligned. The previous behaviour was to always do
byte load and stores which can result in side effects when accessing
an IO device register.
A second fix in the patch is to pass the correct address to
flush_icache_range() when writing to memory in hex2mem().
Thanks!
-Frank
--
Frank Rowand <frank_rowand@mvista.com>
MontaVista Software, Inc
[-- Attachment #2: patch_getput_iospace.gz --]
[-- Type: application/x-gzip, Size: 1042 bytes --]
next reply other threads:[~2001-12-21 22:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-21 22:49 Frank Rowand [this message]
2001-12-26 16:24 ` patch - KGDB read and write of IO registers 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=3C23BC8B.83D8F4DB@mvista.com \
--to=frank_rowand@mvista.com \
--cc=frowand@mvista.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@mvista.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;
as well as URLs for NNTP newsgroup(s).