public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Dieter Kiermaier <dk-arm-linux@gmx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] kirkwood openRD-base / PCI support
Date: Fri, 24 Jul 2009 08:09:28 +0200	[thread overview]
Message-ID: <200907240809.31025.dk-arm-linux@gmx.de> (raw)
In-Reply-To: <73173D32E9439E4ABB5151606C3E19E202DE13BE67@SC-VEXCH1.marvell.com>

Am Freitag 24 Juli 2009 05:59:41 schrieb Prafulla Wadaskar:
> 
> > -----Original Message-----
> > From: Dieter Kiermaier [mailto:dk-arm-linux at gmx.de] 
> > Sent: Thursday, July 23, 2009 6:25 PM
> > To: u-boot at lists.denx.de
> > Cc: Prafulla Wadaskar; Simon Kagstrom
> > Subject: kirkwood openRD-base / PCI support
> > 
> > Hi Prafulla, hi list,
> > 
> > is there anywhere pci support available for u-boot on 
> > openrd-base board?
> > I've googled and searched the list archive but aren't 
> > sucessful :-( It looks like there is no PCI support until 
> > now, Are there any plans to do this from marvell side?
> > 
> > I use Simons patches for initial openrd-base support and try 
> > to get up kirkwoods PCI port.
> > u-boot without PCI is running fine on my openrd-base board.
> 
> Dear Dieter
> PCIe port on Kirkwood SOC can be enabled in the u-boot by defining CONFIG_KIRKWOOD_PCIE_INIT in board configuration header file.
> This enables PCIe interface to work from kernel,
> I have tested it for MV88F6281GTW_GE board.
> 
> Apart from this there is no PCIe support yet enabled in u-boot for kirkwood at this moment
> 
Mmh, so I fear I have to wait a while. I've enabled CONFIG_KIRKWOOD_PCIE_INIT allready. And also written an empty
#ifdef CONFIG_KIRKWOOD_PCIE_INIT
void pci_init_board()
{
	printf("kirkwood: pci_init_board() called\n");
}
#endif /* CONFIG_KIRKWOOD_PCIE_IN */
#endif
in cpu.c
The function is called on bootup - nice.
But if I try pci 0 on the u-boot prompt it gives me
Marvell>> pci
Scanning PCI devices on bus 0
BusDevFun  VendorId   DeviceId   Device Class       Sub-Class
_____________________________________________________________
pci_bus_to_hose() failed
pci_bus_to_hose() failed
pci_bus_to_hose() failed
pci_bus_to_hose() failed
pci_bus_to_hose() failed
pci_bus_to_hose() failed
...
What is not really suprisingly.
but then I was a bit confused what else is needed ;-)

It looks like I have to learn about some basic PCI frameworks inside u-boot first.

Also there are a few other tasks on my desk which have to be done first so I stopped working on it for the moment.
But nevertheless, if there are any news regarding PCIe it would be nice if you could keep me up to date!

Dieter

> Regards..
> Prafulla . .
> 
> > 
> > Many thanks,
> > Dieter
> > 
> > 
> > 
> > 

       reply	other threads:[~2009-07-24  6:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <73173D32E9439E4ABB5151606C3E19E202DE13BE67@SC-VEXCH1.marvell.com>
2009-07-24  6:09 ` Dieter Kiermaier [this message]
2009-07-23 12:55 [U-Boot] kirkwood openRD-base / PCI support Dieter Kiermaier

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=200907240809.31025.dk-arm-linux@gmx.de \
    --to=dk-arm-linux@gmx.de \
    --cc=u-boot@lists.denx.de \
    /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