From: "Cédric CASTANET" <c_castanet@netcourrier.com>
To: <linuxppc-embedded@lists.linuxppc.org>
Subject: RE: Force 6750 VME Board
Date: Mon, 19 Mar 2001 10:01:29 +0100 [thread overview]
Message-ID: <000501c0b053$30221cd0$02888a8c@INFOINDUS.NET> (raw)
In-Reply-To: <01031511102007.00679@pc-eng24.mc.com>
hi,
yes, it can work quickly whith minor changes on pci slots def and pci IRQ
routing.
in arch/ppc/kernel, replace PowerCoreCPCI6750_pci_IRQ_map and
PowerCoreCPCI6750_pci_IRQ_routes by the folowing def :
#ifdef CONFIG_PCORE6750
/* Force Computers PowerCore PCORE IRQ-map */
/* The first table contains an entry number
for the second table the based on the device number.
The second table describes the INTx interrupt wireing */
static char PowerCoreCPCI6750_pci_IRQ_map[] =
{
0, /* Slot 0 - unused */
0, /* Slot 1 - unused */
0, /* Slot 2 - unused */
0, /* Slot 3 - unused */
0, /* Slot 4 - unused */
0, /* Slot 5 - unused */
0, /* Slot 6 - unused */
0, /* Slot 7 - unused */
0, /* Slot 8 - unused */
0, /* Slot 9 - unused */
0, /* Slot 10 - unused */
0, /* Slot 11 - unused */
0, /* Slot 12 - unused */
0, /* Slot 13 - unused */
0, /* Slot 14 - unused */
0, /* Slot 15 - unused */
0, /* Slot 16 - unused */
0, /* Slot 17 - unused */
0, /* Slot 18 - unused */
0, /* Slot 19 - unused */
0, /* Slot 20 - unused */
0, /* Slot 21 - unused */
0, /* Slot 22 - unused */
0, /* Slot 23 - unused */
1*4+1, /* Slot 24 - UNIVERSE II */
0, /* Slot 25 - unused */
1*4, /* Slot 26 - PCI-ISA */
1*4+0, /* Slot 27 - DEC21143 */
2*4+0, /* Slot 28 - PMC I */
3*4+0, /* Slot 29 - PMC II */
0, /* Slot 30 - unused */
0 /* Slot 31 - unused */
};
static char PowerCoreCPCI6750_pci_IRQ_routes[] =
{
0, 0, 0, 0, /* unused */
9, 10, 11, 12, /* PCI0: INTA,INTB,INTC,INTD orig : 12 Was 15 */
11, 12, 9, 10, /* PMCI: INTC,INTD,INTA,INTB orig : 12 Was 15 */
12, 9, 10, 11 /* PMCII: INTB,INTC,INTD,INTA orig : 12, 11, 15, 9
*/
};
#endif /* CONFIG_PCORE6750*/
I think this change is enough to boot the kernel on the PCORE6750 VME but
you have to add the VME driver too.
I have a tar file of linux 2.2.14 that work basicaly whith the PCORE6750VME
whith vme driver. this is a 17Mo file, and it is not "cleanly modified" for
this board. But if you are interested contact me directly.
----------------------------------------------------------------------------
Mr Cedric CASTANET
SCT DPT INFORMATIQUE INDUSTRIELLE
30 BIS RUE EDMOND ROSTAND
31201 TOULOUSE CEDEX (FRANCE)
Tél 05.61.61.12.34
Fax : 05.61.61.12.22
web Dépt.: http://www.sct.fr.st
adresse e-mail : c_castanet@netcourrier.com
----------------------------------------------------------------------------
-----Message d'origine-----
De : owner-linuxppc-embedded@lists.linuxppc.org
[mailto:owner-linuxppc-embedded@lists.linuxppc.org]De la part de Mark
Salisbury
Envoyé : jeudi 15 mars 2001 17:07
À : linuxppc-embedded@lists.linuxppc.org
Objet : Force 6750 VME Board
I see that the montavista packages support the cPCI version fo the force
6750,
has anyone tried it with the VME version?
any hints on where to begin?
thanks in advance.
Mark
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-03-19 9:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-15 16:06 Force 6750 VME Board Mark Salisbury
2001-03-19 9:01 ` Cédric CASTANET [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='000501c0b053$30221cd0$02888a8c@INFOINDUS.NET' \
--to=c_castanet@netcourrier.com \
--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 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.