From: Antony Pavlov <antonynpavlov@gmail.com>
To: Lucas Stach <dev@lynxeye.de>
Cc: barebox@lists.infradead.org
Subject: barebox qemu-malta pci problem
Date: Thu, 2 Apr 2015 00:54:57 +0300 [thread overview]
Message-ID: <20150402005457.b05ee70d5a92c4a403ea13a1@gmail.com> (raw)
Hi!
It looks like qemu-malta barebox pci support is broken since
commit b8a1bb1dd215770670108fe5b0de0e5e137bf8fd
Author: Lucas Stach <dev@lynxeye.de>
Date: Sat Oct 4 19:40:12 2014 +0200
pci: defer device registration until after bridge setup
Otherwise the drivers for a device may probe before the
devices parent bridge is fully configured, which leads
to errors when accessing the BARs.
How to reproduce the problem:
$ cd barebox.git
$ export ARCH=mips
$ export CROSS_COMPILE=<your favorite mips cross-compiler prefix>
# first let's see working state
$ git checkout b8a1bb1dd215770670108fe5b0de0e5e137bf8fd^
$ make qemu-malta_defconfig && make clean && make
$ qemu-system-mips -nodefaults -M malta -m 256 -nographic -serial stdio -monitor null -bios barebox-flash-image -net nic,model=rtl8139
...
barebox:/ devinfo
...
`-- i2c
`-- pci
`-- pci0
`-- pci1
`-- pci2
`-- pci3
`-- pci4
`-- eth0
`-- miibus0
`-- fs
<stop qemu emulation (ctrl-c)>
# devinfo shows eth0 device on pci4. good.
# now let's see broken state
$ git checkout b8a1bb1dd215770670108fe5b0de0e5e137bf8fd
$ make qemu-malta_defconfig && make clean && make
$ qemu-system-mips -nodefaults -M malta -m 256 -nographic -serial stdio -monitor null -bios barebox-flash-image -net nic,model=rtl8139
...
barebox:/ devinfo
...
`-- i2c
`-- pci
`-- fs
# As you can see there is no pci devices on pci bus.
--
Best regards,
Antony Pavlov
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
next reply other threads:[~2015-04-01 21:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-01 21:54 Antony Pavlov [this message]
2015-04-02 8:57 ` barebox qemu-malta pci problem Lucas Stach
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=20150402005457.b05ee70d5a92c4a403ea13a1@gmail.com \
--to=antonynpavlov@gmail.com \
--cc=barebox@lists.infradead.org \
--cc=dev@lynxeye.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.