+1 for all that, will make stuff easier for sure. Best Regards Peter
On Wed, 5 Feb 2020 at 16:02, Mark Hatle <[email protected]> wrote: > > > On 2/4/20 7:01 PM, 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. > > > >> [...] > >> 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. > >> > >> 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. > >> > >> 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. > >> > >> 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? > >> > >> 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!! > > > > 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) > > > > 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. > > Frankly, I agree.. I'm working toward this goal.. but it's going to be > April > before I can make any progress moving closer to this approach. (Part of > the > reason I was hired by Xilinx, was specifically to push for this change and > workflow.. but there are other business realities in play that is making > it go > slower then I wanted.) > > Sorry, I don't have further roadmap to share on how we're going to get > there.. > but after/during April is the current plan. > > --Mark > > > Hey... my 2 cents. > > > > Oh, and don't forget about my question regarding linux-xlnx on 5.[45] ;) > > > > Cheers! > > > > > > > > > >
-=-=-=-=-=-=-=-=-=-=-=- Links: You receive all messages sent to this group. View/Reply Online (#4652): https://lists.yoctoproject.org/g/meta-xilinx/message/4652 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]] -=-=-=-=-=-=-=-=-=-=-=-
