From: "Michael S. Zick" <mszick@morethan.org>
To: parisc-linux@lists.parisc-linux.org
Subject: Re: [parisc-linux] Re: CCIO dma io_command and related io_tlb format questions.
Date: Mon, 16 Oct 2006 09:37:15 -0500 [thread overview]
Message-ID: <200610160937.15846.mszick@morethan.org> (raw)
In-Reply-To: <J788XR$E1A2FE043CF88207AEC13412E82258F2@scarlet.be>
On Mon October 16 2006 06:51, Joel Soete wrote:
>
> ====<>====
>
> May be could we also use some define like:
> #define Mb (1 << 20)
> #define Gb (1 << 30)
>
Joel,
Let me add a bit (no pun intended) from the 53c7xx manuals ...
The transfer offset register is 21 bits - -
So the largest single chunk of memory 7xx can transfer is 2^21
in a single command (single list entry, if passing it lists).
There was a mention somewhere of a special use for the high bit,
I do not recall the details at this moment.
So a limit on the contiguous block size of 2^20 should work.
Larger blocks would have to generate multiple list entries
by the time the code reaches the controller.
Another limit of the transfer hardware in the controller is
that it can not transfer a block which crosses 2^32 boundaries.
(The transfer base register is 32 bits.)
In those cases, you also have to split the block into above/below
2^32 and reprogram the chips interface (HP) hardware inbetween.
Some of the 53c8xx controllers handle 2^64 physical addressing,
but I have not studied those yet.
> Duno yet if it's realted to my pb but tia for your attention,
> Joel
Mike
_______________________________________________
parisc-linux mailing list
parisc-linux@lists.parisc-linux.org
http://lists.parisc-linux.org/mailman/listinfo/parisc-linux
next parent reply other threads:[~2006-10-16 14:37 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <J788XR$E1A2FE043CF88207AEC13412E82258F2@scarlet.be>
2006-10-16 14:37 ` Michael S. Zick [this message]
2006-10-17 5:59 ` [parisc-linux] Re: CCIO dma io_command and related io_tlb format questions Grant Grundler
[not found] <J7AHPO$ED967CCDD9E203D6968EA2045C11A08A@scarlet.be>
[not found] ` <45351637.4070604@computer.org>
2006-10-17 19:07 ` Kyle McMartin
[not found] <J70JNP$255156D3B4F90827118C5EFE40FD3ABF@scarlet.be>
2006-10-12 19:55 ` Grant Grundler
2006-10-13 10:56 ` Joel Soete
2006-10-13 16:44 ` Grant Grundler
[not found] ` <4530DF1F.5060601@scarlet.be>
2006-10-14 14:11 ` Matthew Wilcox
2006-10-14 16:40 ` Michael S. Zick
2006-10-14 23:35 ` Joel Soete
2006-10-15 3:28 ` Grant Grundler
2006-10-11 8:48 Joel Soete
2006-10-12 1:04 ` Grant Grundler
2006-10-12 3:27 ` James Bottomley
[not found] ` <4538BB5F.5040703@scarlet.be>
2006-10-20 15:50 ` Grant Grundler
2006-10-20 16:31 ` Grant Grundler
2006-10-20 17:18 ` Joel Soete
2006-10-21 6:19 ` Grant Grundler
2006-10-21 17:17 ` Joel Soete
2006-10-23 4:34 ` Grant Grundler
-- strict thread matches above, loose matches on Subject: below --
2006-10-09 9:41 [parisc-linux] " Joel Soete
2006-10-10 22:08 ` [parisc-linux] " Grant Grundler
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=200610160937.15846.mszick@morethan.org \
--to=mszick@morethan.org \
--cc=parisc-linux@lists.parisc-linux.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