From: Ian Stirling <root@mauve.demon.co.uk>
To: robert@schwebel.de (Robert Schwebel)
Cc: linux-kernel@vger.kernel.org
Subject: Re: Accessing odd bytes
Date: Fri, 14 Jun 2002 15:40:37 +0100 (BST) [thread overview]
Message-ID: <200206141440.PAA11680@mauve.demon.co.uk> (raw)
In-Reply-To: <20020614143140.A7467@schwebel.de> from "Robert Schwebel" at Jun 14, 2002 02:31:40 PM
>
> I have a strange effect on an embedded system (AMD Elan SC410,
> Linux-2.4.18) while accessing a static RAM. The RAM is mapped to the bus
> at 0x0200'0000. If I map it to user space this way:
<snip>
> Now I'm wondering how the kernel/processor handles odd byte access
> exceptions. Can anybody give me a pointer where I could search or what my
> problem could be?
It has been a while, but I believe you may need to setup the SC410s MMU
to tell it it's an 8 bit (or whateve) RAM.
Reading the manuals may reveal details that I've forgotten.
prev parent reply other threads:[~2002-06-14 14:40 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-06-14 12:31 Robert Schwebel
2002-06-14 14:02 ` Richard B. Johnson
2002-06-14 14:40 ` Ian Stirling [this message]
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=200206141440.PAA11680@mauve.demon.co.uk \
--to=root@mauve.demon.co.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=robert@schwebel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®