Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fsbl: inject an appropriate DTS string for the microchip expansion board #1

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

terpstra
Copy link

Unfortunately, these boards shipped without an embedded DTB of their own.
Detect these boards by the absence of a ChipLink DTB and the presence of
the Microsemi PCIe controller in ECAM space.

When detected, switch the board DTB for a DTB which includes the Microsemi
root complex.

Unfortunately, these boards shipped without an embedded DTB of their own.
Detect these boards by the absence of a ChipLink DTB and the presence of
the Microsemi PCIe controller in ECAM space.

When detected, switch the board DTB for a DTB which includes the Microsemi
root complex.
Copy link
Contributor

@tmagik tmagik left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What is the downside (until we have proper overlay support, or a new bitstream) to just assume a Microsemi board exists, and letting Linux probe for the PCI root complex, rather than including two complete dtb blobs which only differ by whether they have the Microsemi entry or not?

I can't really test it anyway, as from what I can tell the image that shipped on the expansion boards has something wrong with it, so a new bitstream is going to be required to do anything useful.

@terpstra
Copy link
Author

terpstra commented Sep 4, 2018

Don't merge this. It's not ready yet.

@terpstra
Copy link
Author

terpstra commented Sep 4, 2018

We should also try as you suggest: let the driver probe for the Microsemi PCIe if the board doesn't say anything different via ChipLink.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants