On 06/13/2018 04:12 PM, Kyösti Mälkki wrote: > Hi > > Now that we wiped out K8, I'd like to put my eyes on fam10-15 boards. What exactly do you mean by wiped out?
> > Couple questions for board owners: > > First, about asus/kcma-d8 and asus/kgpe-d16: Do these have working S3 > support? I remember rumours they originally worked at some point, but > regressed during the rebase / upstream process. Anyone willing to > bisect/fix it if necessary? > I have a D16 with v4.6 that I regularly use suspend with and it works absolutely fine - I can also suspend a host featuring a guest with IOMMU graphics and then resume that host later on and continue playing video games on the guest. > I am asking, because these are the last two remaining boards with > combination of HAVE_ACPI_RESUME=y and RELOCATABLE_RAMSTAGE=n, and we > have to drag along some back-and-forth memory copy code to keep OS > memory intact for these two. > > Second, I would like to move forwards with AMD fam10 to have > RELOCATABE_RAMSTAGE=y, that would also solve above-mentioned issue and > open up doors for some new features. > > If it was my decision, RELOCATABLE_RAMSTAGE for x86 would be one > criteria to survive the next (October 2018?) release. POSTCAR_STAGE > for May 2019. I am probably too late to make such wishes, but I hope > these will happen in the next two years nevertheless. I again state my for-some-reason controversial opinion that at this rate there will soon be no non-development boards in coreboot due to the choices of the current leadership in determining standards. Removing something from master is in fact removal from coreboot - one of the reasons is as over time the older versions of software required to compile older versions of coreboot will become un-obtainable already to compile master critical old GPL code is only obtainable from one obscure non-US site. -- coreboot mailing list: coreboot@coreboot.org https://mail.coreboot.org/mailman/listinfo/coreboot