From: Simon Glass <sjg@chromium.org>
To: u-boot@lists.denx.de
Subject: early stage debugging on a real product
Date: Wed, 25 Nov 2020 10:03:40 -0700 [thread overview]
Message-ID: <CAPnjgZ0AqkVX6L_Os3vtEDB=cZ8xbAsvNG5Hed+JNie68T4_Ww@mail.gmail.com> (raw)
In-Reply-To: <CAHp75Vf68bm5-SG2kdC2-rCiG6HVfOzS-0v0rXaoKat19dzehg@mail.gmail.com>
Hi Andy,
On Wed, 25 Nov 2020 at 09:58, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> On Wed, Nov 25, 2020 at 5:45 PM Simon Glass <sjg@chromium.org> wrote:
> > On Wed, 25 Nov 2020 at 08:35, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > > On Wed, Nov 25, 2020 at 5:23 PM Simon Glass <sjg@chromium.org> wrote:
>
> ...
>
> > > Thanks. But the question is still open why DM PCI et al. is not
> > > getting initialized.
> >
> > PCI should come up so long as you have a PCI driver. See the various
> > other boards - you need a pci-x86 device:
> >
> > pci {
> > compatible = "pci-x86";
> > u-boot,dm-pre-reloc;
> > };
>
> I have so far
>
> pci {
> compatible = "pci-x86";
> #address-cells = <3>;
> #size-cells = <2>;
> u-boot,dm-pre-reloc;
> ranges = <0x02000000 0x0 0x80000000 0x80000000 0 0x40000000
> 0x42000000 0x0 0xc0000000 0xc0000000 0 0x20000000
> 0x01000000 0x0 0x2000 0x2000 0 0xe000>;
> };
>
> pci_init() makes the system hang.
>
> WRT video I will try later when I see PCI initialized successfully.
Probably PCI autoconfig is already done. See CONFIG_PCI_PNP. BTW there
is also ll_boot_init() which disables various init that might already
be done.
Regards,
Simon
next prev parent reply other threads:[~2020-11-25 17:03 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-23 14:05 early stage debugging on a real product Andy Shevchenko
2020-11-23 19:00 ` Andy Shevchenko
2020-11-23 19:08 ` Simon Glass
2020-11-23 19:18 ` Andy Shevchenko
2020-11-23 19:49 ` Andy Shevchenko
2020-11-24 13:58 ` Andy Shevchenko
2020-11-24 16:53 ` Simon Glass
2020-11-24 19:47 ` Andy Shevchenko
2020-11-24 23:41 ` Simon Glass
2020-11-25 11:26 ` Andy Shevchenko
2020-11-25 13:26 ` Andy Shevchenko
2020-11-25 14:49 ` Simon Glass
2020-11-25 15:08 ` Andy Shevchenko
2020-11-25 15:23 ` Simon Glass
2020-11-25 15:36 ` Andy Shevchenko
2020-11-25 15:45 ` Simon Glass
2020-11-25 16:59 ` Andy Shevchenko
2020-11-25 17:03 ` Simon Glass [this message]
2020-11-25 20:43 ` Andy Shevchenko
2020-11-25 15:56 ` Ovidiu Panait
2020-11-25 16:09 ` Andy Shevchenko
2020-11-25 17:11 ` Siarhei Siamashka
2020-11-25 17:34 ` Andy Shevchenko
2020-11-25 18:06 ` Simon Glass
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='CAPnjgZ0AqkVX6L_Os3vtEDB=cZ8xbAsvNG5Hed+JNie68T4_Ww@mail.gmail.com' \
--to=sjg@chromium.org \
--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;
as well as URLs for NNTP newsgroup(s).