Rob Herring wrote:
Changing the firmware is not the only way to modify the DT. Perhaps a
DT overlay would work better than carrying patches if the patches
aren't upstreamable. It kind of depends on how early you'd need to
apply the overlay and whether you'd need external phandles (aka
__symbols__ node, which the base DTB wouldn't support).
Looking at the DT, I think this change might fix it. Can you test this change:
Rob Herring wrote:
Changing the firmware is not the only way to modify the DT. Perhaps a
DT overlay would work better than carrying patches if the patches
aren't upstreamable. It kind of depends on how early you'd need to
apply the overlay and whether you'd need external phandles (aka
__symbols__ node, which the base DTB wouldn't support).
Looking at the DT, I think this change might fix it. Can you test this change:
Hans Verkuil has dropped the overlay support for BTTV TV cards. That means, that tvtime doesn't work anymore.
Hans Verkuil wrote:
Destructive overlay support (i.e. where the video frame is DMA-ed
straight into a framebuffer) is effectively dead. It was a
necessary evil in the early days when computers were not fast enough
to copy SDTV video frames around, but today that's no longer a problem.
It requires access to the framebuffer memory, which is a bad idea and
very hard to do safely. In addition, in drm it is today almost
impossible to get hold of the framebuffer address.
“Rob Herring“ wrote:
Do you have a dmesg log with debug enabled for a successful boot? I searched archives and forum, but couldn't find one. isa-bridge.c has debug enabled so you should get a few messages.
From looking at the DT, the isa node has no ranges, so the difference in parsing code shouldn't even matter. You should be seeing this message:
printk(KERN_ERR "no ISA IO ranges or unexpected isa range, "
"mapping 64k\n");
Rob
“Rob Herring“ wrote:
Commit e4ab08be5b49 ("powerpc/isa-bridge: Remove open coded "ranges" parsing") broke PASemi Nemo board booting. The issue is the ISA I/O range was not getting mapped as the logic to handle no "ranges" was inverted. If phb_io_base_phys is non-zero, then the ISA range defaults to the first 64K of the PCI I/O space. phb_io_base_phys should only be 0 when looking for a non-PCI ISA region.
“Rob Herring“ wrote:
Do you have a dmesg log with debug enabled for a successful boot? I searched archives and forum, but couldn't find one. isa-bridge.c has debug enabled so you should get a few messages.
From looking at the DT, the isa node has no ranges, so the difference in parsing code shouldn't even matter. You should be seeing this message:
printk(KERN_ERR "no ISA IO ranges or unexpected isa range, "
"mapping 64k\n");
Rob
“Rob Herring“ wrote:
Commit e4ab08be5b49 ("powerpc/isa-bridge: Remove open coded "ranges" parsing") broke PASemi Nemo board booting. The issue is the ISA I/O range was not getting mapped as the logic to handle no "ranges" was inverted. If phb_io_base_phys is non-zero, then the ISA range defaults to the first 64K of the PCI I/O space. phb_io_base_phys should only be 0 when looking for a non-PCI ISA region.