All of lore.kernel.org
 help / color / mirror / Atom feed
From: Robert Staven <robert@stopthespam_remove.staven.no>
To: linuxppc-embedded@ozlabs.org
Subject: Allocating (placing) BufferDescriptors in Dual-Port RAM (CPM2)
Date: Sun, 01 Apr 2007 00:26:19 +0200	[thread overview]
Message-ID: <460EE00B.30007@stopthespam_remove.staven.no> (raw)

It's probably basic knowledge, but I still having trouble figure it 
out.... anyway:

Working with a SCC in a CPM (MPC8250 running linux 2.6.13-AM)

I need to place Buffer Descriptors (BD) in the Dual-Port RAM (DPRAM) 
somewhere....
But two FCCs, SMC1 and SCC1 are in use, and they might use some part of 
the DPRAM.

Is there any way to figure out what part of the DPRAM thats free?
And how to reserve the part I need?

Robert

(SCC3 parameter RAM are at 0x8200 in DPRAM so I just place a struct 
there and assume that linux stays away from this memory area and don't 
get mad cause I use it without allocating it. Or have I got this wrong to?)

             reply	other threads:[~2007-03-31 22:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-31 22:26 Robert Staven [this message]
2007-04-02 10:57 ` Allocating (placing) BufferDescriptors in Dual-Port RAM (CPM2) Vitaly Bordug

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=460EE00B.30007@stopthespam_remove.staven.no \
    --to=robert@stopthespam_remove.staven.no \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.