From: robinpv <robinpv@aiware.co.jp>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] u-boot porting problem (Execution after code relocated to sdram)
Date: Mon, 12 Jun 2006 10:37:20 +0900 [thread overview]
Message-ID: <448CC550.6040602@aiware.co.jp> (raw)
Hi ,
In u-boot porting, i am facing a problem.
Here after the relocation of the code to the sdram, the code is
executed from sdram,
at some point we have to do the pci initialization. so we are storing
the configuration
function in a structure based on the device we want to configure. I am
able to detect
the device. After dectecting device, when the configuration function
if being called,
the flash address is loaded and control is jumping it to flash address.
At that flash address there is no valid code, but "uboot.dis"
disassemble file shows the
valid code at that address.
Shouldn't the control jump to relocated sdram address of the
configuration function ?
--------------------------------------------------------------
File: drivers/pci.c
In pci_hose_scan_bus()
if (cfg) {
cfg->config_device(hose, dev, cfg);
#ifdef CONFIG_PCI_PNP
} else {
int n = pciauto_config_device(hose, dev);
sub_bus = max(sub_bus, n);
#endif
--------------------------------------------------------------
In my board related file:
static struct pci_config_table pci_tb0286_config_table[] = {
{ 0x126F, 0x0501, PCI_ANY_ID, PCI_ANY_ID, PCI_ANY_ID,PCI_ANY_ID,
pci_cfgfunc_config_device, { PCI_ENET0_IOADDR,
PCI_ENET0_MEMADDR,
PCI_COMMAND_MEMORY |
PCI_COMMAND_MASTER }},
{ }
};
---------------------------------------------------------------
Please provide your feedback on this.
Thanks & Regards
Robin
next reply other threads:[~2006-06-12 1:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-12 1:37 robinpv [this message]
2006-06-12 7:11 ` [U-Boot-Users] u-boot porting problem (Execution after code relocated to sdram) Wolfgang Denk
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=448CC550.6040602@aiware.co.jp \
--to=robinpv@aiware.co.jp \
--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 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.