From: "Russell McGuire" <rmcguire@videopresence.com>
To: "'Kumar Gala'" <galak@kernel.crashing.org>
Cc: linuxppc-embedded@ozlabs.org
Subject: RE: 83xx immap_qe.h -> SIR type def error?
Date: Fri, 1 Feb 2008 13:03:00 -0800 [thread overview]
Message-ID: <000301c86515$d4bd6640$6405a8c0@absolut> (raw)
In-Reply-To: <1ADE91E0-282D-4455-9754-886846B3EB90@kernel.crashing.org>
Kumar,
Yes in the main memeory map they are just listed as 1K RAM blocks.
However, in the UM Section 36.6.1 <pg 36-12 or pg 1728 in the PDF>.
It gives the breakout for the RAM, which clearly indicates 16 bit fields.
<Here is a short clip from Figure 36-8>
Access: Read/Write
0 1 2 3 4 5 6 7 10 11 13 14 15
MCC SWTR SSEL 1 SSEL 2 SSEL 3 SSEL 4 SGS CSEL CNT BYT LST
Figure 36-8. SI RAM Entry for UCC
Honest, mistake as if I were writing the header file I'd not have time to
ready all 2000+ pages of the UM. We find these only as somebody goes in an
tries to use them.
And I am guessing not a lot of customers use the SI block.
-Russ
> -----Original Message-----
> From: Kumar Gala [mailto:galak@kernel.crashing.org]
> Sent: Friday, February 01, 2008 6:56 AM
> To: rmcguire@videopresence.com
> Cc: linuxppc-embedded@ozlabs.org
> Subject: Re: 83xx immap_qe.h -> SIR type def error?
>
>
> On Feb 1, 2008, at 5:47 AM, Russell McGuire wrote:
>
> > All Freescale,
> >
> > Not sure if this is the place to post this, but I have run across
> > what I
> > consider to be a possible type error in the immap_qe.h file, for the
> > asm/powerpc branch.
> >
> > In the file immap_qe.h
> >
> > /* SI Routing Tables */
> > struct sir {
> > u8 tx[0x400];
> > u8 rx[0x400];
> > u8 res0[0x800];
> > }
> >
> > Shouldn't these types be defined as __be16 ?
> >
> > According to the Freescale manual this is a 16 bit field, not an 8-bit
> > field.
> >
> > Spent an hour trying to figure out why I couldn't fill this field
> > out with
> > upper 8 bits last night.
> >
> > Thoughts?
>
> I'm guessing it was done this way since they are just looked as base
> offsets. Where in the UM do you see anything about them being 16-bit
> quantities? (I'm really know little about this).
>
> - k
next prev parent reply other threads:[~2008-02-01 21:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3.1201827605.31777.linuxppc-embedded@ozlabs.org>
2008-02-01 11:47 ` 83xx immap_qe.h -> SIR type def error? Russell McGuire
2008-02-01 14:56 ` Kumar Gala
2008-02-01 21:03 ` Russell McGuire [this message]
2008-02-01 21:37 ` Russell McGuire
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='000301c86515$d4bd6640$6405a8c0@absolut' \
--to=rmcguire@videopresence.com \
--cc=galak@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.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).