Fu Wei <tekkamanninja@xxxxxxxxx> 于2021年10月8日周五 上午11:55写道: > > Hi All, > > Great thanks for your explanation, Zamir. > > Zamir SUN <zsun@xxxxxxxxxxxxxxxxx> 于2021年10月7日周四 下午9:55写道: > > > > > > > > On 10/5/21 04:39, Richard W.M. Jones wrote: > > > On Mon, Oct 04, 2021 at 12:07:30PM -0700, Kevin Fenzi wrote: > > >> On Mon, Oct 04, 2021 at 01:03:27PM -0400, Matthew Miller wrote: > > >>> Hi all! I just got back from Open Source Summit, several of the talks I > > >>> found interesting were on RISC-V -- a high-level one about the > > >>> organizational structure, and Drew Fustini's more technical talk. > > >>> > > >>> In that, he noted that there's a Fedora build *, but it isn't an official > > >>> Fedora arch. As I understand it, the major infrastructure blocker is simply > > >>> that there isn't server-class hardware (let alone hardware that will build > > >>> fast enough that it isn't a frustrating bottleneck). > > >> > > >> We have avoided using emulation in the past because we would be chasing > > >> bugs in our emulation that aren't in real hardware and vice versa. > > >> How good is the emulation support? Do we know/have people who can fix > > >> things in it when we hit them? Tools folks: is emulation an option here? > > >> Or do we still forbid it? > > > > > > Qemu support for RISC-V is very good, it's actually used to develop > > > some features (virtualization and SBI). We do know people who can fix it. > > > If you have the money real hardware is also available now. > > the early next spring, we may can have RISC-V laptop. :-), Hardware > won't be a problem anymore > > > > > > > Personally speaking I think the real barrier is someone with a large > > > colourful hat putting up the money to hire a full time developer to > > > work on the project. > > > > > > > I know Wei FU(FAS: tekkamanninja) is actively working on porting Fedora > > to RISC-V. He has his BSP for D1 which he already put up a wiki[1]. I'm > > about to help him get LXQt desktop up on D1 soon. > > > > In current situation maybe it makes more sense to start thinking about > > making all RISC-V contributors work together rather than doing > > everything on each own, which would be much efficient. > > > > [1] https://fedoraproject.org/wiki/Architectures/RISC-V/Allwinner > > > > > Rich. > > We are NOT ONLY working on D1, but also continually release Fedora > Image for StarFive Soc, currently JH7100, will focus on JH7110 later. > > https://fedora.starfivetech.com/pub/downloads/BeagleV-release/ > > we have several Koji systems can be used : > https://koji.oepkgs.net/koji/ (we will start to use it to build all > the Fedora packages later) > https://openkoji.iscas.ac.cn/koji (Our main playground ) > https://fedora.starfivetech.com/koji (StarFive koji system for Fedora on JH Soc) > > Our extra REPO for fedora RISC-V: > https://repo.oepkgs.net/people/extra-repos/rv64-ext-repo/ > > for now , I am also working upstream opensbi/uboot/linux kernel > patches for RISC-V > > > > > > > >>> So, one question is: if we used, say, ARM or x86_64 Amazon cloud instances > > >>> as builders, could we build fast enough under QEMU emulation to work? We > > >>> have a nice early advantage, but if we don't keep moving, we'll lose that. > > yes, that could work, if we have more then 100 builder( 4~9-core , > 32GB) on the cloud, > that would be enough, I think > > > >>> > > >>> But beyond that: What other things might be limits? Are there key bits of > > >>> the distro which don't build yet? Is there a big enough risc-v team to > > >>> respond to arch-specific build failures? And, do we have enough people to do > > >>> QA around release time? > > QA is a problem. I and my colleagues can work on engineering side, > but we also need QE/QA. > > > >> > > >> Well, one big thing is that it's been a while since we had any secondary > > >> arches and it's unclear how they would work today. In the distant past > > >> secondary arches had their own koji and builders and composes and > > >> releases and used koji-shadow to try and match up with primary koji. > > >> This was basically more than a full time job for someone and I am sure > > >> koji-shadow has atrophied in recent years, but perhaps at least some > > >> subset could be made to work again. > > >> > > >> On the other hand we could just add it into primary koji, but then it > > >> really really has to keep up or it's going to block everything else. > > >> > > >> So, probibly a 'secondary' koji and builders to start with to bootstrap > > >> and to gather info on how hard it is to keep up and good emulation is > > >> would be worthwhile, but it's gonna need some dedicated work. > > any other info you need , other than the koji info above > > > >> > > >> Perhaps we could get a up to date status report from folks working on > > >> this, answering such questions as: > > >> > > >> * How good is emulation support > > Good enough as builders :-) please check our kojis in China > > > >> * What would it take to keep up with the other arches? Is that possible? > > yes, need more packages to build, but it is definitely possible > > > >> * What device(s) would we want to target and could we get sufficent > > >> numbers of them for QA and devel folks to debug problems and test? > > QEMU/Allwinner D1/StarFive JH Soc board/ SiFive unmatched/ > > > >> * Are there folks who can bootstrap/shepard the koji shadowing process? > maybe we can have a try ? > > > >> > > >> I think RISC-V is pretty exciting, and I am happy to help as much as I > > >> can with adding it in. I think there's likely to be a lot of > > >> interest/growth in coming years for it. > > Great thanks > > > >> > > >> kevin > > > > > > > > > > > >> _______________________________________________ > > >> devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > > >> To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx > > >> Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ > > >> List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > > >> List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx > > >> Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure > > > > > > > > > > -- > > Zamir SUN > > GPG : 1D86 6D4A 49CE 4BBD 72CF FCF5 D856 6E11 F2A0 525E > > Want to know more about Fedora? > > Visit https://fedoraproject.org/wiki/ > > Ready to contribute? See https://whatcanidoforfedora.org/ > > 想了解更多中文资讯,访问 https://zh.fedoracommunity.org/ _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure