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 07:49:53 -0700 [thread overview]
Message-ID: <CAPnjgZ3kkungrg8jhoOWxtO0njY-_EXiN21=KD9B5Pm1rtVH7w@mail.gmail.com> (raw)
In-Reply-To: <CAHp75VeVfRnCdRrSkCsZr=osnum+Sdwgp-xuyKOyc8_D=CU62Q@mail.gmail.com>
Hi Andy,
On Wed, 25 Nov 2020 at 06:26, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> On Wed, Nov 25, 2020 at 1:41 AM Simon Glass <sjg@chromium.org> wrote:
> > On Tue, 24 Nov 2020 at 12:46, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > > On Tue, Nov 24, 2020 at 6:54 PM Simon Glass <sjg@chromium.org> wrote:
> > > > On Tue, 24 Nov 2020 at 06:57, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
>
> ...
>
> > > > Did you get the console working?
> > >
> > > Nope. The PCI (framebuffer) driver is not getting probed.
>
> Can you elaborate how Gfx PCI driver is supposed to be enumerated in
> the DM model?
I think you should be more worried about the UART!
If graphics has been started up earlier, then I don't know if you can
do it again, nor how you can find out the video parameters to use.
I'm guessing you are not using the FSP in U-Boot, so fsp_graphics.c is
not being used. Perhaps you have enabled vesa.c but it expects to be
able to run the video ROM. There is also drivers/video/coreboot.c
which reads a coreboot table to find out where the frame buffer is
used. For Broadwell there is a special driver at
drivers/video/broadwell_igd.c
Note that graphics uses lazy init, like everything else in U-Boot, so
unless you have 'vidconsole' in your stdout it won't actually init it.
You can use something like this to force probing video:
struct udevice *dev;
int ret = uclass_first_device_err(UCLASS_VIDEO, &dev);
Regards,
Simon
next prev parent reply other threads:[~2020-11-25 14:49 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 [this message]
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
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='CAPnjgZ3kkungrg8jhoOWxtO0njY-_EXiN21=KD9B5Pm1rtVH7w@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).