[coreboot] Re: What should we do about freenode IRC services?
On Tue, May 25, 2021 at 6:01 AM Patrick Georgi via coreboot < coreboot@coreboot.org> wrote: > Hi everybody, > > you might have heard that freenode.org recently changed management under > weird circumstances. Given that we use their services for our project > chat, this concerns us as well. > > In last week's leadership meeting we had a wide variety of opinions: To > go for libera.chat (a network created by former freenode staff), some > other IRC network, to leave IRC behind and go for something newer and > Matrix and Mattermost have been brought up as examples of where this > might lead. Of course, we could also decide to stay on freenode, > although from what transpires that option seems less and less attractive > every day. > > So, what should we do? > As we are present on a number of social media, I want to throw in another option - which some folks will love, and others will hate - and that's perfectly fine. This community has grown enough that there will never be a one size fits all again: Discord It can both be accessed in a web browser or through a mobile app. I started a "Discord Server" for us there. If you want to come check it out, join us through https://discord.gg/JqT8NM5Zbg Stefan > > > Regards, > Patrick > ___ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org > ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: cgit on review.coreboot.org
> why can't you use the gerrit 'download' button to either cherry pick the > patch or pull the stack? I want to download the raw file, not the Git patch. I want to be able to tell someone who needs this blob "just click this link to download it". Right now I have to say "click this link to download a tarball and then extract this file from it" which is a bit more annoying. ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: failure cherry-picking patches from https://review.coreboot.org/coreboot
Thanks Peter, yes we implemented something similar in out GitHub repo. I'll keep monitoring. Thanks again for your time! Selma. -Original Message- From: Peter Stuge Sent: Tuesday, May 25, 2021 4:56 PM To: coreboot@coreboot.org Subject: [coreboot] Re: failure cherry-picking patches from https://review.coreboot.org/coreboot Hi Selma, Bensaid, Selma wrote: > FYI, we are observing the same issue today on chromium coreboot repo > https://chromium-review.googlesource.com/admin/repos/chromiumos/third_ > party/coreboot I think we need to figure out a proper solution. Thanks for providing the debug output! So since the issue does stem from a large distance between branches and hitting network communication limits maybe an effective workaround would be to maintain a local clone of the upstream repo (in a separate repo) and using a file:// URL pointing to that repo for the origin remote in your working repo? The upstream clone must be on the same machine, so it's more overhead, but file:// should be reliable. HTTP, regardless of version, is really inappropriate for applications. //Peter ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: cgit on review.coreboot.org
Julius, why can't you use the gerrit 'download' button to either cherry pick the patch or pull the stack? -vb On Tue, May 25, 2021 at 5:14 PM Julius Werner wrote: > Hi Patrick, Martin, > > I just noticed that we seem to have dropped support for cgit on the > coreboot Gerrit. I don't exactly remember how it worked, but I seem to > have been able to get a link like > > https://review.coreboot.org/cgit/qc_blobs.git/plain/sc7180/qtiseclib/libqtisec.a > some time last year. Now that just redirects to Gitiles. > > The problem with Gitiles is it's impossible to just get a direct > download link to a file -- you can only see source files in the > browser view (with the Gitiles UI on the side), but you can't download > the raw file exactly as it is in the repo. This is especially > problematic for binary files where there is (as far as I can tell? > Maybe I just can't find it...) no way to get their contents at all > without downloading a whole tarball of a directory and extracting it > (which is pretty cumbersome). > > Do you guys know why this happened and is there any chance we could > get cgit back? > > Thanks, > Julius > ___ > coreboot mailing list -- coreboot@coreboot.org > To unsubscribe send an email to coreboot-le...@coreboot.org > ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: link time optimization testing
Dear Branden, Am 26.05.21 um 04:25 schrieb Branden Waldner: On 5/25/21, Paul Menzel wrote: Am 22.05.21 um 20:03 schrieb Branden Waldner: On 5/21/21, Arthur Heymans wrote: Thanks for sharing your findings. The flash is 256K big, which is quite small these days. When building coreboot with default settings but without a payload I find that there is 69K empty space left for payloads. Some future developments I have been working on might give a bit more breathing space. - I want to make romstage optional and include the sources in the bootblock: That should shave off roughly 10K of romstage. - I have compressing postcar working (maybe you can also disable the postcar console to reduce size). That's also 2-3k size gains at likely the const of a tiny bit of boot performance on this platform. - I also have some WIP code to merge postcar into ramstage which would save 15k. Maybe on coreboot release 4.15 you will have a better time building a fully working image with the default configuration. I didn't realize there was development going on to save rom space, that's good to know. I just built the asus/p2b from commit d981c490 (mb/google/mancomb: Enable some PCIe power saving features) with the Debian sid/unstable toolchain (gcc (Debian 10.2.1-6) 10.2.1 20210110). There, wasn’t enough space to add SeaBIOS’ configuration file to CBFS. Not setting `INCLUDE_CONFIG_FILE`, there wasn’t any error, the coreboot image built fine. ``` FMAP REGION: COREBOOT Name Offset Type Size Comp cbfs master header 0x0cbfs header32 none fallback/romstage 0x80 stage 17336 none cpu_microcode_blob.bin 0x44c0 microcode 83968 none fallback/ramstage 0x18d00stage 53376 LZMA (112168 decompressed) build_info 0x25e00raw89 none fallback/dsdt.aml 0x25e80raw 5514 none cmos_layout.bin0x27440cmos_layout 704 none fallback/postcar 0x27740stage 16888 none fallback/payload 0x2b980simple elf 69886 none (empty)0x3cac0null 1956 none bootblock 0x3d280bootblock 11088 none ``` Building with Jacob’s link time optimization changes [1], which he thankfully rebased, saved 13 kB, so the configuration file would fit in too. ``` FMAP REGION: COREBOOT Name Offset Type Size Comp cbfs master header 0x0cbfs header32 none fallback/romstage 0x80 stage 14752 none cpu_microcode_blob.bin 0x3ac0 microcode 83968 none fallback/ramstage 0x18300stage 46277 LZMA (95496 decompressed) build_info 0x23840raw89 none fallback/dsdt.aml 0x238c0raw 5514 none cmos_layout.bin0x24e80cmos_layout 704 none fallback/postcar 0x25180stage 14872 none fallback/payload 0x28c00simple elf 69886 none (empty)0x39d40null15012 none bootblock 0x3d800bootblock9664 none ``` (If you have a recovery option and some spare time, it’d be great if you tested the LTO patches.) I could probably test them out, though I'm not sure I'll get around to it right away. No hurry. Does the patch set require anything special? It looks like it just uses a Kconfig to add the choice to use the LTO compiler options. Sorry, I only noted “(whole series)” below at the reference. You need the changes listed on the right side in Gerrit. Gerrit’s download options allow you to fetch those with one command. Does it work with the coreboot crossgcc or should I try using the system compiler on the build machine like you did (Debian sid x86_64), or maybe it would be best to try both? More tests are always welcome, but coreboot’s crossgcc should work. My recovery method isn't very good right now though. If I've got a boot failure I change the rom to a known good one and hot swap back to the chip with the bad rom to reflash it. It's pretty annoying, but I haven't messed up yet. Speaking from experience, three chips would be better. ;-) But, I used the same method for years, and there are worse methods (if no socket is there). I did try to get some (cheap) zif adapter sockets, but they didn't work out for me - not enough space and they don't seat in a socket, they seem to be meant to be soldered to a board, not used in a socket. Sorry, I do not know anything about that. I haven't had much luck in finding options for recovery. Ideally I'd like something like the dual switched bios in the old wiki but toggle-able electronically ie. gpio pin from spare router w/ Openwrt. That sounds like
[coreboot] Re: What should we do about freenode IRC services?
Dear coreboot folks, Am 26.05.21 um 08:38 schrieb Felix Singer: […] Currently, on libera there are 46 people and on OFTC 2 people (me included). So I would say let's move to libera. Agreed. Let’s do what most members in #coreboot users already did. Kind regards, Paul ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: What should we do about freenode IRC services?
On Wed, 26 May 2021 06:38:58 +, Felix Singer wrote: >- The Matrix bridge for libera is WIP. I am not sure if OFTC has > one. I couldn't find anything on their website. OFTC has a working matrix bridge. But I guess given the current situation, libera will have one soon, too (but I don't know). -- Merlin Büge ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: What should we do about freenode IRC services?
On Wed, 26 May 2021 00:03:34 +, Peter Stuge wrote: > I don't think it's a horrible idea to just chill and see what happens. I > find it interesting that christel seems invested in the Handshake project. IMO we have chilled enough to see what happens. Currently most channels which mention libera in their topic get forcibly taken over be the new freenode staff and moved to the ## namespace, like here[0]. Personally, I want to move away from this network ASAP. Regards, -- Merlin Büge [0] https://news.ycombinator.com/item?id=27285774 ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: What should we do about freenode IRC services?
On Tue, 2021-05-25 at 15:00 +0200, Patrick Georgi via coreboot wrote: > So, what should we do? In my opinion, we should move away as long as we are able to. They are taking over channels which mention or reference any other chat service in their topic. See [1][2][3][4]. They might get other crazy ideas in the future (or maybe already have), who knows. I would still like to have the possibility to chat over IRC. We shouldn't do a "hard" move to another chat service, like Matrix or Mattermost, since I think there is not enough time to evaluate all non- IRC options and we shouldn't wait much longer. We should rather remain on IRC and use a bridge. This way, people will have enough time to get familiar with the alternative chat service, if we decide (at some later point) to move away from IRC completely. Some thoughts regarding libera <-> OFTC: - The services on libera work like the ones on freenode, while OFTC works a bit different afaik. - The Matrix bridge for libera is WIP. I am not sure if OFTC has one. I couldn't find anything on their website. I am registered on libera and OFTC and I am fine with both, but I don't really use OFTC. Both networks already have a coreboot channel created by people related to the project. Currently, on libera there are 46 people and on OFTC 2 people (me included). So I would say let's move to libera. // Felix [1] https://twitter.com/GrapheneOS/status/1397401277072646145 [2] https://twitter.com/GrapheneOS/status/1397402818324140033 [3] https://twitter.com/mjg59/status/1397389042619097095 [4] https://twitter.com/andy_kelley/status/1397388932367601665 ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
[coreboot] Re: What should we do about freenode IRC services?
Hi all, On Tue, 25 May 2021 15:00:51 +0200, Patrick Georgi via coreboot wrote: > So, what should we do? I'm not a dev but long-time user of coreboot. I would be happy with staying on IRC (OFTC or libera) or switching to something that could easily be bridged to IRC. I also think that would fit nicely with coreboot's philosophy (simplistic, no-frills, etc.). Regards, -- Merlin Büge ___ coreboot mailing list -- coreboot@coreboot.org To unsubscribe send an email to coreboot-le...@coreboot.org
