linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Sangmoon Kim" <dogoil@etinsys.com>
To: "xavier grave" <grave@ipno.in2p3.fr>,
	<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PCI mapping for a MVME5500
Date: Fri, 24 Oct 2003 20:18:39 +0900	[thread overview]
Message-ID: <003d01c39a20$9403bdd0$212d4cdc@smkim> (raw)
In-Reply-To: 20031023160100.GA8653@ipnpcu9.acq.ami


Hi,

Tundra's Universe II doesn't used the  memory area allocated by the system
as a VME area.
There are sets of registers which allocate VME area seperately.
PCI autoconfig rotine does not allocate it.
You should allocate it on driver code.
Visit www.vmelinux.org for more information.

Or try our product called Multiverse,
which is allocated by PCI autoconfig.
We are selling a vme board which uses Multiverse and MPC8245 (the board name
is KVME-080).
For more information visit www.etinsys.com.

Oops, It's not an advertisement...
I'm just the developer of the Multiverse and the board.

Regards,
Sangmoon Kim

----- Original Message -----
From: "xavier grave" <grave@ipno.in2p3.fr>
To: <linuxppc-embedded@lists.linuxppc.org>
Sent: Friday, October 24, 2003 1:01 AM
Subject: PCI mapping for a MVME5500


>
> Hi everybody,
>
> We just have received a new mvmv5500 from motorola.
> It runs with linux-2.4.20 kernel (std tree) + motorola patches.
>
> I have a driver for the universe chip (which runs for mvme2300 &
> mvme5100). But here it cant allocate pci memory space because the pci
> bridge (upon the tundra chip depends) had only 1 MB memory allocate by
> the system. For my VME spaces I need many more, does anybody know where
> I can try to modify this 1MB allocation ?
>
> Thanks in advance, xavier
>
>
>


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2003-10-24 11:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-23 16:01 PCI mapping for a MVME5500 xavier grave
2003-10-24 11:18 ` Sangmoon Kim [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='003d01c39a20$9403bdd0$212d4cdc@smkim' \
    --to=dogoil@etinsys.com \
    --cc=grave@ipno.in2p3.fr \
    --cc=linuxppc-embedded@lists.linuxppc.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).