public inbox for sid@sourceware.org
 help / color / mirror / Atom feed
From: "Frank Ch. Eigler" <fche@redhat.com>
To: Robert Shideleff <bigbob@shideleff.com>
Cc: sid@sources.redhat.com
Subject: Re: GDB/mapper cache problems
Date: Wed, 23 Jun 2004 01:47:00 -0000	[thread overview]
Message-ID: <20040623014739.GA25926@redhat.com> (raw)
In-Reply-To: <200406222050.55129.bigbob@shideleff.com>

[-- Attachment #1: Type: text/plain, Size: 597 bytes --]

Hi -

> The processor is an arm7t with a 32 bit bus. The flash is a 16 bit device. 
> [...] In our actual hardware, we have a mapper that will read and 
> register two 16 bit addresses on the flash and shift/concatenate them to form 
> a single 32 bit word when the processor executes a 32 bit read. [...]

I don't recall exactly now, but it may be that the plain memory mapper
component's optional stride/width syntax might specify exactly this.
Append ",2,2" after your flash address-range string and see what bus
API calls flow downstream.  (See siddoc hw-mapper-basic.)


- FChE

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-06-23  1:47 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-17  1:57 Multiple arm7t processors in pbb causes seg fault Robert Shideleff
2004-06-17 21:54 ` Frank Ch. Eigler
     [not found] ` <20040622024603.GB22793@redhat.com>
     [not found]   ` <200406212319.30979.bigbob@shideleff.com>
2004-06-22 16:08     ` GDB/mapper cache problems Robert Shideleff
2004-06-22 16:23       ` Frank Ch. Eigler
2004-06-23  0:51         ` Robert Shideleff
2004-06-23  1:47           ` Frank Ch. Eigler [this message]
2004-06-23 23:35             ` Robert Shideleff

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=20040623014739.GA25926@redhat.com \
    --to=fche@redhat.com \
    --cc=bigbob@shideleff.com \
    --cc=sid@sources.redhat.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 read-only IMAP folder(s) and NNTP newsgroup(s).