Hi, On 05. 02. 20 2:01, Jean-Francois Dagenais wrote: > Hi guys, > > Here's a message I sent to a Xilinx executive I met in San Diego last > August... I think it is of general interest and since there are always new > people in the list, I thought I'd post here. It also touches the matter of > github.com/xilinx not being a community space but a delayed mirror of > Xilinx's internal process.
I don't think that anybody really said github as community space. If you look at all comments recommendation is to use xilinx forums or send a patch to [email protected]. Github is used for sharing source code not any place for discussion. If you need to discuss something use xilinx forums where the whole support team will deal with it. > >> [...] >> Remember the discussion we had about Xilinx working in silo for long periods >> on linux-xlnx, then dumping months of work on GitHub? Well, right now we are >> in the process of trying out Lima for the MALI GPU. Unfortunately, Lima only >> made it into the 5.2 kernel and it is now still being worked on actively. >> One needs to mind the userspace part too. >> >> For those reasons, we are considering upgrading our kernel to 5.4 or some >> nearby LTS. Since we are tracking linux-xlnx/master periodically, it is >> quite hard for us to merge a higher version of linus' tree since we >> basically need to port forward (merge conflicts) all the Xilinx additions. This is hard work for us, but not as much for the developers of said changes, i.e. Xilinx devs. linux-xlnx has own rules and it is about sharing code. It is Xilinx SoC vendor tree. As you see Xilinx is upstreaming patches and follows mainline process as much as possible based on internal goals. This is meta-xilinx mailing list and I am surprised that you didn't spot that last year 4.19 rebased tree has been also merged to linux-yocto https://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto/ If you look there you will see that v5.4 version is already there and it is community driven effort and also good place for these discussions. >> >> So can you tell me if and where we could find such ongoing work, even if it >> is WIP. We only use a subset of the changes Xilinx adds to the kernel, so >> maybe your current state of, say, 5.4 would work fine for us and allow us to >> continue development. above. >> >> If you can't share it publicly (which I doubt since all work in the kernel >> is basically GPL'd), could we arrange an alternate sharing strategy? Even if >> it is a one time thing. GPL doesn't mean that you need to share it publicly. But there are no secret version. It just take some time to stabilize and test things. When we are happy with kernel quality it will be pushed as always. >> >> Or maybe what would be simpler would be to create a branch on your >> linux-xlnx github called 5.4-wip for example. This way people know what to >> expect in this branch. Or maybe upstream 5.4 already contains everything we >> need? There was no decision about it. And I personally prefer not to use linux-xlnx for any hacky/untested code. That's why I don't think that there is going to be any branch witch just disappear. Communication was IMHO quite clear about this repository and branches there and that's how it should be. >> >> Thanks for your help, or forwarding this to the right person if needed. >> >> Cheers! > > > Here's one of our earlier mention of this issue > https://lists.yoctoproject.org/g/meta-xilinx/message/4517 > > I was reminded of this earlier today when I visited the list of open MR on > github/xilinx/linux-xlnx and found some other developer had also submitted a > cyclic DMA fix!! Github is not allowing disabling pull requests but soon you will find there similar patch to this one. https://github.com/Xilinx/u-boot-xlnx/commit/4cfcdd18c99fe03aa1a92df521703ff37b6ed3fb It means if you have a patch send it to use via [email protected]. > > The way xilinx runs github right now is broken. I really don't want to be > bitchy about this, I want things to improve and am willing to participate > honestly in the discussion. Today I just want to mention to the new guard > what many have echoed in the past and has never (to my knowledge) been > addressed by Xilinx. (That is until Mark partly did earlier today. > https://lists.yoctoproject.org/g/meta-xilinx/message/4645) Unfortunately github is not allowing to disable pull requests and solution above is the only way how to do it. If you have issue with any code which is already upstream please use appropriate mailing list. If you have any patch to Xilinx SOC vendor tree please send it to [email protected]. If you want to have different discussion go to xilinx forums where team will take care about it. > It would be better for all if work could be done in real time on github (or > some other open platform), possibly in another group perhaps (linux-wip) so > that release following customers know what to expect and community > participators such as us here can be involved during the process. As above. Github shouldn't be use as a place for any discussions like this. Linux kernel or U-Boot projects, which I do maintain, have already well establish mailing lists for contribution. Not sure if [email protected] was advertised properly but that's the place where you should send your patches. > > Hey... my 2 cents. > > Oh, and don't forget about my question regarding linux-xlnx on 5.[45] ;) If you look at Xilinx Linux kernel you could see some consistency and it is not hard to guess how that kernel versions are choose. It means that LTS kernel candidate is chosen. At XDFs were said that next version will be v5.4. in 2019 it was 4.19, in 2018 it was 4.14. For 2021 what will be chosen at https://www.kernel.org/category/releases.html will be there. I hope I covered all your points. Thanks, Michal -- Michal Simek, Ing. (M.Eng), OpenPGP -> KeyID: FE3D1F91 w: www.monstr.eu p: +42-0-721842854 Maintainer of Linux kernel - Xilinx Microblaze Maintainer of Linux kernel - Xilinx Zynq ARM and ZynqMP ARM64 SoCs U-Boot custodian - Xilinx Microblaze/Zynq/ZynqMP/Versal SoCs
signature.asc
Description: OpenPGP digital signature
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4653): https://lists.yoctoproject.org/g/meta-xilinx/message/4653 Mute This Topic: https://lists.yoctoproject.org/mt/70987364/21656 Group Owner: [email protected] Unsubscribe: https://lists.yoctoproject.org/g/meta-xilinx/unsub [[email protected]] -=-=-=-=-=-=-=-=-=-=-=-
