2012/11/11 Olof Kindgren <[email protected]>: > 2012/11/10 Franck Jullien <[email protected]>: >> Hi, >> >> I'm starting this discussion because I think we have a lack of >> maintenance for IP cores. >> >> Opencores provides free hosting for projects. There is no moderator >> filter applied. So we can >> have very good, good, bad or empty projects. >> >> When an IP is hosted at opencores, it's not easy for a contributor to >> send patch for it. >> The only way to get patch applied is to contact the author (am I wrong >> ?). However, sometimes >> cores are very old and the author is not taking care of it anymore.... >> >> I think we should have a special category in opencores projects where >> we could have "under >> control projects". Those projects would have active maintainers and >> patch would be send on >> the mailing list. >> >> IP core that have a driver in the Linux mainline should of course be >> in this category. >> >> Core in this new category should also strictly follow coding style >> rules and core files organization >> but that another story (we already have this >> http://cdn.opencores.org/downloads/opencores_coding_guidelines.pdf). >> >> What do you think about this ? Is it feasable at opencores ? >> >> Franck. >> _______________________________________________ >> OpenRISC mailing list >> [email protected] >> http://lists.openrisc.net/listinfo/openrisc > > Hi, > > Yes, I agree that it is a bit problematic right now. I've been > planning to step up as a proxy maintainer for a bunch of the cores. > Mainly the ones that will be used in orpsocv3. It would be great if > more people could do that too.
Great news. I know that Stefan got commit rights to > the ac97 repo a while ago and sent in some patches there. > > As for sending patches, there is a bug tracker for each project. but > I'm not sure if it's possible to attach patches there. It might be > interesting to consider using bugzilla for more products than the > OpenRISC. > > There is also the OCCP (OpenCores Certified Project) stamp on some > projects, which is supposed to indicate that it is actively used. It > could be a good thing to just notify the OpenCores maintainers if a > new project should have this status, or if an old project should be > demoted. Ok I agree on this. May be that we can stick to the OCCP stamp and do not create a new section. > > As for the linux support, that would be a good thing to make more > visible. Just adding a penguin symbol to cores that have linux drivers > would be fine with me. > I also agree on this. > Regarding coding style, I think the sad truth is that it would take a > lot of work to verify and change all cores, but it is definitely > something that we should try to do in the long run > Well this work should have been done before. However, projects with the OCCP stamp might be checked again. And new projects should be reviewed before getting their OCCP stamp. As I told you when we met, the tiny SPI core is a good example. This core as a driver in the Linux mainline (spi-oc-tiny.c). However, on the opencores website, it doesn't have a OCCP stamp. This should not be possible....Plus, the official maintainer should be opencores because the core has to remain very stable. Any change in the core should be acked by opencores gurus and checked against the linux driver. I know this is a lot of work and I'm not going to change everything :) As a first step, I'll try to work on the tiny SPI core. PS: is it difficult for opencores.org to create an opencores mailling list ? Franck. _______________________________________________ OpenRISC mailing list [email protected] http://lists.openrisc.net/listinfo/openrisc
