[coreboot] Re: "Delete change" Gerrit feature does more harm than good

2020-01-08 Thread Mike Banon
It would be nice if the deleted commits get moved to some archive outside of Gerrit instead of being simply removed, to ensure that if anyone else is interested in these commits, they could be restored. A bit later I discovered that only the "drop ROMCC" ones were removed - so not much has been

[coreboot] Re: Error 404 , can't open change 38107 on Gerrit

2020-01-08 Thread Mike Banon
A bit later I realized that "Switch away from ROMCC" commits weren't deleted, only the other "Drop ROMCC boards" - so not much has been lost. However, it really concerns me that important work could be easily lost in such a way! Wish there was an archive, maybe outside of Gerrit - storage of such

[coreboot] Re: Error 404 , can't open change 38107 on Gerrit

2020-01-08 Thread Idwer Vollering
I think Mike means changesets that are not abandoned but trashed, like https://review.coreboot.org/c/coreboot/+/37815 Op wo 8 jan. 2020 om 19:53 schreef : > > See > https://review.coreboot.org/q/owner:ehaouas%2540noos.fr+Switch+away+from+ROMCC_BOOTBLOCK+status:abandoned > ‌ > De : "Carl-Daniel

[coreboot] Re: "Delete change" Gerrit feature does more harm than good

2020-01-08 Thread Angel Pons
Hi Mike, On Wed, Jan 8, 2020 at 9:09 AM Mike Banon wrote: > > "Delete change" Gerrit feature was available for a limited time, and > I've successfully deleted some 3 year old changes (don't worry, their > work has been merged at newer changes - I've double checked it well > before proceeding -

[coreboot] Re: libgxfinit + latest master gives "static noise" bootscreen (Windows)

2020-01-08 Thread Rafael Send
Hmm. I exported my own vbt on Ubuntu with "cp /sys/kernel/debug/dri/0/i915_vbt vbt.bin", which worked fine in the past, but I still get the noise. Windows 10... R ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to

[coreboot] Re: Error 404 , can't open change 38107 on Gerrit

2020-01-08 Thread ehaouas
See https://review.coreboot.org/q/owner:ehaouas%2540noos.fr+Switch+away+from+ROMCC_BOOTBLOCK+status:abandoned;>https://review.coreboot.org/q/owner:ehaouas%2540noos.fr+Switch+away+from+ROMCC_BOOTBLOCK+status:abandoned ‌ De : "Carl-Daniel Hailfinger" A : "Mike Banon" ,"HAOUAS Elyes"

[coreboot] Re: Error 404 , can't open change 38107 on Gerrit

2020-01-08 Thread Carl-Daniel Hailfinger
Hi Mike, maybe the archives contain some salvageable info: https://mail.coreboot.org/hyperkitty/list/coreboot-ger...@coreboot.org/ On 08.01.20 08:36, Mike Banon wrote: > Same problem with many other "Drop boards with ROMCC_BOOTBLOCK" > changes. So much work has been lost... > > On Wed, Jan 8,

[coreboot] AGESA MMIO Allocation

2020-01-08 Thread awokd via coreboot
Am attempting to resolve one of the last listed High Impact Outstanding AGESA Coverity issues (1376956), but am struggling to determine the programmer's intent. In /src/vendorcode/amd/agesa/f15tn/Proc/CPU/Family/0x15/cpuF15MmioMap.c line 236, Coverity complains about the 12 element MmioRange array

[coreboot] Re: [fam16h AM1I-A] ehci-pci: can't derive routing for PCI INT B. USB 3.0 doesn't work even as USB 2.0

2020-01-08 Thread Michal Zygowski
I have taken a look on the irq_tables files for almost all AMD boards and what I noticed is that the tables define a bridge device 14.4 as a router and old SBXXX device/vendor ID. To me it looks like a copy-paste from very old code base. I am going to look into that soon if I find some spare time.

[coreboot] Re: [fam16h AM1I-A] ehci-pci: can't derive routing for PCI INT B. USB 3.0 doesn't work even as USB 2.0

2020-01-08 Thread Mike Banon
> I think something is messed up with those USB ports on G505s too, > because I have to use irqpoll on them in Qubes. I have the BKDG for AMD > 15h. Where can I find the appropriate IRQ routings for the G505s's chipset? Build a coreboot for G505S with CONFIG_DEBUG_PIRQ and see the warning/error

[coreboot] "Delete change" Gerrit feature does more harm than good

2020-01-08 Thread Mike Banon
"Delete change" Gerrit feature was available for a limited time, and I've successfully deleted some 3 year old changes (don't worry, their work has been merged at newer changes - I've double checked it well before proceeding - so nothing lost). However, someone used the same feature to remove the