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

Test with 5.4 kernels #11

Open
shawaj opened this issue Oct 2, 2020 · 8 comments
Open

Test with 5.4 kernels #11

shawaj opened this issue Oct 2, 2020 · 8 comments

Comments

@shawaj
Copy link
Member

shawaj commented Oct 2, 2020

As per this issue...

PiSupply/PaPiRus#215

@ryanteck
Copy link

ryanteck commented Oct 2, 2020

It didn't work and needs fixing.

@ryanteck
Copy link

ryanteck commented Oct 2, 2020

Duplicate of #10 irc

@shawaj
Copy link
Member Author

shawaj commented Oct 2, 2020

@tvoverbeek
Copy link
Contributor

tvoverbeek commented Oct 19, 2020

@shawaj @ChristopherRush Just tested the changes Phil made in raspberrypi/linux@b7d685c#diff-dc041e47200262dfab1ff9f9e0ef64c7.
They make the screen work again. With the current overlay I only get a black screen with back-light off (The point-shoot cam still takes pictures).
The changes are not yet in the normal repository.

For now to disable the current HAT overlay add the line dtoverlay= before any dtparam and dtoverlay lines in /boot/config.txt. This prevents the HAT overlay from loading (No need for soldering the address jumper for address 0x51).
For now you will have to compile the changed overlay your self, copy it to /boot/overlays and put a dtoverlay line in /boot/config.txt
For the future we should use the idea Phil suggested to put only the overlay name in the HAT, so it will always use the current one in /boot/overlays.

@shawaj
Copy link
Member Author

shawaj commented Oct 20, 2020

@tvoverbeek yes I agree, will move to the overlay name method for all production going forward. Need to perform some tests with our production eeprom programmers but relatively trivial to fix if there's an issue anyway

@ryanteck
Copy link

What did we need to do to get this sorted then? Update the script to modify config?

@tvoverbeek
Copy link
Contributor

tvoverbeek commented Nov 11, 2020

@ryanteck
For Media Center Hats with the devicetree fragment in the EEPROM do the following:

  • In /boot/config.txt before any dtoverlay lines put the line dtoverlay=.
    This prevents the loading of the HAT device tree fragment (which does not work due to changes with SPI in the 5.4 kernel)..
  • Further down add the line dtoverlay=media-center. This will load the dtoverlay from /boot/overlays.
    The current one is fixed for the SPI communication with the media-center hat.

This works for me.

@shawaj
Copy link
Member Author

shawaj commented Jan 3, 2021

@ryanteck shall we edit the install script to handle this?

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

No branches or pull requests

3 participants