diff options
| author | Martin Kennedy <hurricos@gmail.com> | 2022-04-26 17:04:06 -0400 |
|---|---|---|
| committer | Hauke Mehrtens <hauke@hauke-m.de> | 2022-05-01 13:23:12 +0200 |
| commit | a142d96ade462e2b9bb922c8e615d3811066e794 (patch) | |
| tree | e216a2eff0c75daf36f8bcd550616cb1b87df56c /target/linux/ath79 | |
| parent | fbd9605a908dc514ebf669589d40ea38c1d25134 (diff) | |
| download | upstream-a142d96ade462e2b9bb922c8e615d3811066e794.tar.gz upstream-a142d96ade462e2b9bb922c8e615d3811066e794.tar.bz2 upstream-a142d96ade462e2b9bb922c8e615d3811066e794.zip | |
mpc85xx: Fix output location of padded dtb
In commit 7e614820a892 ("mpc85xx: add support for Extreme Networks
WS-AP3825i"), we borrowed a recipe convention from apm821xx for device
tree blob padding. Unfortunately, in the apm821xx target, the image
recipes name the device tree blob differently, meaning that in
mpc85xx, the padded dtb is never consumed.
Change the definition of `Build/dtb` so that it outputs the padded dtb
to the correct location for it to be consumed.
Also, rename the recipe to `Build/pad-dtb`, so it is clear we
are building and padding the device tree blob.
This change fixes Github issue #9779 [1].
[1]: https://github.com/openwrt/openwrt/issues/9779
Fixes: 7e614820a892 ("mpc85xx: add support for Extreme Networks WS-AP3825i")
Signed-off-by: Martin Kennedy <hurricos@gmail.com>
(cherry picked from commit 1d06277407d3e294589ecde46328303a9f3803fd)
Diffstat (limited to 'target/linux/ath79')
0 files changed, 0 insertions, 0 deletions