I've attempted to implement something to help, as well as revise the README
files. It's very much still a work in-progress. Look at 'langdale-next' in
meta-xilinx and meta-xilinx-tools.
Specifically in meta-xilinx:
https://github.com/Xilinx/meta-xilinx/commit/51ffcebf0cd804e43c2d8d53bb0709a9480081bb
Other patches in this series cleanup things, as well as work to implement mesa
lima vs the libmali. I've no idea if or when this will go into our regular
tree, but it works (it's just slower then libmali.)
I am looking for feedback on this and the other patches in there.
--Mark
On 11/7/22 12:04 PM, Mark Hatle wrote:
On 11/7/22 9:59 AM, Livius wrote:
I noticed that arhitect problem a half year ago, but nobody care about, it, i
just i got a bullshit not working answer about this things. More over, i could
provided a normal and maintanable style/architect with separated qemu.conf and
generic.conf files to not lose key functionality in the HDF recipe with
automatic HDF_MACHINE assigning, but there were no any review or discussion
about it, that it can bee better and more professional then now.
https://github.com/Xilinx/meta-xilinx/pull/41
<https://github.com/Xilinx/meta-xilinx/pull/41>
I DO care about this. I believe the architecture is right, but I need to fix
the usage around the architecture.
github pull requests get handled, but it's slow. We're much faster at
responding to the mailing list.
Do you know that all of your Xilinx devboard machine configurations
<https://github.com/Xilinx/meta-xilinx/tree/master/meta-xilinx-bsp/conf/machine>
are corrupted in meta-xilinx-bsp
Yes, I know they are mostly broken. We're working on it. I expect to have
something I can share in the next months. We're a small team, and nobody
reported these things were not working (the meta-xilinx-bsp) pieces until we had
no resources to work on them. And I see a completely lack of anyone suggesting
patches for them as well.
<https://github.com/Xilinx/meta-xilinx/tree/master/meta-xilinx-bsp> and not
buildable because of your new hardcoded generic configs like foreign HDF/XSA and
so on? It is little boring that in every half year in every new release need to
deep dive in xilinx machine configurations and fix your mistakes to be able to
use a standard developer board like ZCU104 or any own custom board config which
perfect before.
And this is why I published langdale and master updates _NOW_ and not in 6
months. I WANT feedback, I want patches, and I want discussions on these items.
I expect in the next few days most of the remaining langdale/master updates will
be in a state I can push them to github. Once that is done, the next thing on
my agenda is to try to sync meta-xilinx-bsp and the XSAs.
While I can't promise it, my intention is to merge anything public to github
langdale and master going forward. We're just beginning the process so it's
taking longer then I hoped, but it is a process we're trying to do.
--Mark
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5084):
https://lists.yoctoproject.org/g/meta-xilinx/message/5084
Mute This Topic: https://lists.yoctoproject.org/mt/94844586/21656
Group Owner: [email protected]
Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
