Am Mi., 17. Juni 2020 um 02:47 Uhr schrieb Julius Werner <
jwer...@chromium.org>:
> Patrick, any further concerns from your side? If not, would you mind
> creating a new repository for this? I can write the patches to move
> blobs and adjust the Makefiles afterwards.
>
I will create a repo for
Am Mo., 15. Juni 2020 um 22:27 Uhr schrieb Gregg Levine <
gregg.drw...@gmail.com>:
> Initialized empty Git repository in /usr/src/lobos/work4/coreboot/.git/
> fatal: https://review.coreboot.org/coreboot.git/info/refs download
> error - The requested URL returned error: 406
>
Am Mi., 10. Juni 2020 um 03:43 Uhr schrieb Julius Werner <
jwer...@chromium.org>:
> > Clearly, the rules should be the same for all blobs, so if
> > some blobs with language like this are already in the repository, it
> > shouldn't be grounds to reject new blobs from landing.
It's not unheard of
Am Di., 2. Juni 2020 um 17:50 Uhr schrieb Jeremy Jackson :
> Below is a patch that does what I want for one of the points I
> mentioned. Comments? Does this interfere with a different use case?
>
I'd say that change is reasonable. Care to push it to review.coreboot.org
or should somebody else
Hi everybody,
Just a quick heads up: the unit tests in tests/ are now built and run on
every commit pushed to review.coreboot.org.
Consider this a good opportunity to improve our stability by contributing
tests! Jan is writing a tutorial on writing tests that you can find for now
at
Hi everybody,
during last week's issue with the resource allocator there have been some
remarks about how the change seemed practically invisible despite being on
Gerrit for 2 months and some people suggested that it would be useful to
have better documentation with such changes on why they're
Peter Stuge schrieb am Sa., 16. Mai 2020, 15:39:
> Holy moly..
>
Indeed...
All I could find was "prepare for 64 bit resources". That is beyond weak.
>
To people dealing both with somewhat modern hardware and coreboot, it is
well known that the resource allocator has a few crucial weaknesses in
Hi Eduardo,
Am Mo., 11. Mai 2020 um 03:24 Uhr schrieb edbatalha--- via coreboot <
coreboot@coreboot.org>:
> About 2 months ago I discovered that it is supported by coreboot so I
> thought it would be fun to experiment with it.
>
Well, welcome!
> 2)
> I then decided to try out Windows XP but
release's document in Documentation/releases!
Best regards,
Patrick Georgi
--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsführer: Paul Manicle, Halimah DeLaine Prado
signature.asc
Description: PGP
Hi Sindhoor,
Welcome to coreboot!
Would you mind spending a few words on what you'll be working on? It's
something about POST codes but there's little more than that available
about your project, and there has been some interest in your work already.
Thanks,
Patrick
--
Google Germany GmbH,
Hi again,
A while I ago I announced my intent to do a new coreboot
release. This is slated to happen next Monday, so we're now at
the "~1 week prior to release" point of our release checklist (at
https://doc.coreboot.org/releases/checklist.html).
So as a reminder: Please test the devices you
Hi everybody,
There's some fine work by Jan on Gerrit on the issue of adding unit testing
infrastructure to our tree and I'd like to see it merged soon.
So far, most feedback was by Google folks so this is a heads up for
everybody (and especially those not at Google) to take a look and offer
ened since 4.11 that you think is noteworthy. If in doubt, push
a change to gerrit and see what your fellow developers think about it.
Thanks,
Patrick Georgi
--
Google Germany GmbH, ABC-Str. 19, 20354 Hamburg
Registergericht und -nummer: Hamburg, HRB 86891, Sitz der Gesellschaft: Hamburg
Geschäftsfü
Hi everybody,
we just had our project leadership meeting and I brought up the Google
Season of Docs[0] programme which is similar to Summer of Code but
for documentation.
(Note to meeting attendants: I mentioned that the application deadline
for projects has already passed, but I was wrong about
Hi Sindhoor,
Am Di., 24. März 2020 um 08:19 Uhr schrieb Sindhoor Tilak <
sindh...@sin9yt.net>:
>This is my first time here applying for GSoC.
>
> I'm interested in couple of ideas posted. I wanted to know if multiple
> proposals are accepted?
>
If you have multiple proposals, feel free to
Am Fr., 6. März 2020 um 12:15 Uhr schrieb Piotr Król :
> If the community keeps our reviews not merged, we
> cannot use that as proof of our engagement and quality.
[...]
> This doesn't contribute to project health.
>
Indeed. Looking into Gerrit, we have >1000 commits open for coreboot.
Some
Hi everybody,
since we're invited to participate in this year's GSoC and since students
can send their project proposals starting next week, I guess now is the
time to register potential mentors with the system, so we can triage and
assign proposals efficiently.
If helping a student get up to
David Hendricks schrieb am Mi., 29. Jan. 2020,
00:51:
> we'd first need to invent a way to
> send an electric shock thru the keyboard to users who complain to (or
> about) Intel when something goes wrong with the code.
>
That may have been necessary in the era of the fdiv bug but I'm not sure
On Mon, Jan 27, 2020 at 04:24:00PM -0600, Matt DeVillier wrote:
> having a src/mainboard/stub/ for **all** SoC might not be a bad idea,
> especially if it were to select less common/non-default options that other
> in-tree boards don't select by default, to ensure full coverage of all SoC
>
Hi everybody,
one thing that became clear to me in the recent (and not-so-recent)
discussions broadly related to coding style, code duplication, code
submission strategies, documentation requirements and similar things
is that there have to be many different styles of approaching coreboot
Am Di., 28. Jan. 2020 um 08:03 Uhr schrieb David Hendricks <
david.hendri...@gmail.com>:
> Please correct me if I'm way off base with that example. The stubs
> Patrick proposed in the other thread might help address the issue,
> however it can also mean adding code which exists only to satisfy
Hi Marshall,
thanks for that cohesive report and insight into your development process
and the trade-offs involved.
Am Mo., 27. Jan. 2020 um 21:12 Uhr schrieb Marshall Dawson <
marshalldawson...@gmail.com>:
> Instead, please give me the opportunity to review any of your changes that
> touch the
Nico Huber via coreboot schrieb am So., 26. Jan.
2020, 02:07:
> Hello again,
>
> so, we have Jenkins that runs build tests on our master branch. That
> makes working together on a huge project much easier. However, do we
> have a rule that all the code should be build tested? and if not,
>
Am Do., 9. Jan. 2020 um 06:46 Uhr schrieb 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.
That's not easily done and I
Am Mo., 9. Dez. 2019 um 19:02 Uhr schrieb Seth Rosenblatt <
s...@the-parallax.com>:
> I wasn't able to find the security@ alias, otherwise would've emailed
> y'all there. I didn't hear back before publication but happy to make any
> corrections if needed. I'm also willing to include a statement
Am Mo., 9. Dez. 2019 um 11:51 Uhr schrieb Jorge Fernandez Monteagudo <
jorg...@cirsa.com>:
> >Note that the setting is per-clone by default, so if you set up coreboot
> to be without sslVerify, that doesn't apply to the board_status repo unless
> you also used --global.
>
> Yes, I have it
Note that the setting is per-clone by default, so if you set up coreboot to
be without sslVerify, that doesn't apply to the board_status repo unless
you also used --global.
Am Mo., 9. Dez. 2019 um 11:11 Uhr schrieb Jorge Fernandez Monteagudo <
jorg...@cirsa.com>:
>
> >We moved the other thread
We moved the other thread off-list, but the issue was that there's a https
proxy in the way that
terminates SSL connections.
I documented the approach to deal with that in
https://review.coreboot.org/c/coreboot/+/37599
Patrick
Am So., 8. Dez. 2019 um 09:39 Uhr schrieb Mike Banon :
> My guess
Am Fr., 6. Dez. 2019 um 17:23 Uhr schrieb Jose Trujillo via coreboot <
coreboot@coreboot.org>:
> Added variable: 0x0, val size: 0
> Found variable: key size: 0x0, val size: 0
>
> Several minutes later boots normal.
> If someone here knows how to fix it or suspect which could be the reason
>
Am Do., 5. Dez. 2019 um 15:22 Uhr schrieb Jorge Fernandez Monteagudo <
jorg...@cirsa.com>:
> One noob question. Can I push a change from a commit
> (f77f2c79c2bb898c123ffe89a0bd1acb5362afc5)
> not the master? From this commit I can make it boot but from the last
> there are
> a lot of changes to
Hi Jorge,
Am Do., 5. Dez. 2019 um 12:53 Uhr schrieb Jorge Fernandez Monteagudo <
jorg...@cirsa.com>:
> and in setting I can see my GitHub user (jorgefm1900), the ID, etc... Then
> under 'HTTP Credentials' I've press
>
the 'GENERATE NEW PASSWORD' button and the string I get is what I use to
>
Am Do., 5. Dez. 2019 um 12:16 Uhr schrieb Jorge Fernandez Monteagudo <
jorg...@cirsa.com>:
> > You can try setting up SSH key on the gerrit account and change the git
> remote to SSH instead of HTTPS.
> Sorry, we only have access to http/https ports... maybe I have a
> certificate's problem...
>
Hi everybody,
in today's leadership meeting we discussed whether we should hire
technical writers to improve our documentation. While the situation
already got a lot better since we moved to the Documentation/ directory
instead of the wiki, it's still painfully obvious (at least to me)
that we're
On Sun, Nov 24, 2019 at 11:00:00AM +, awokd via coreboot wrote:
> Could a Coreboot Coverity admin please re-run the scan against master?
Done.
> Looks like the last analyzed version was from Sep 24, 2019. I would like
> to see what AGESA issues remain.
Thanks for the heads-up!
I'm not quite
It's my pleasure to announce that coreboot 4.11 was just released.
Release notes follow. Note that there are deprecations listed that will
be in effect immediately. The first two (Fam12 and MIPS) probably don't
affect anybody, but the third item has quite a lot of ripple effect.
I was
On Mon, Nov 04, 2019 at 09:30:34AM -0500, Patrick Georgi wrote:
> I'm planning to release coreboot 4.11 two weeks from today, Nov 18th.
This has been deferred to tomorrow, Nov 19th.
My basic functionality tests with current master are looking good,
but there are two issues for which I'm try
So, LinuxBIOS/coreboot v2 is just an older version of the current coreboot,
so it's in the same repository as the current code, so git clone
https://review.coreboot.org/coreboot.git gives you _all_ code, and git
checkout 38cd29ebd7282333650cf11ed50c7f2fd4031e80 (a rather arbitrary
version I
On Thu, Nov 07, 2019 at 12:05:44PM +0100, Nico Huber wrote:
> 1. Few people seem to take the might of Git into account. We have a
Git is rather limited in some respects: For example it has no notion
of a copy (except by using interesting merge hacks: create a branch
where you rename, merge the two
On Wed, Nov 06, 2019 at 12:39:59PM +0100, Nico Huber wrote:
> > Some of the mega patches are copies of a predecessor chip (with the
> > minimum amount of changes to integrate it in the build), that are
> > then modified to fit the new chip.
>
> Ack. I think that is a problem. If this procedure is
On Tue, Nov 05, 2019 at 06:37:02PM +0100, Nico Huber wrote:
> I mean "rubber-stamping of *huge* commits". That huge that it is
> obvious that no review happened, e.g. 1k+ LOC copy-pasta. Also, the
> guidelines say "This means you shouldn't +2 a patch just because you
> trust the author of a patch
On Tue, Nov 05, 2019 at 02:26:25PM +0100, Nico Huber wrote:
> So, we already have Gerrit guidelines [1]. While they are most often
> not worth a look (common sense usually is enough), some people like
> to be reminded of them regularly. The latter is pretty annoying and
> doesn't seem to help.
Hi everybody,
I'm planning to release coreboot 4.11 two weeks from today, Nov 18th.
As usual, it's a snapshot release, not aligned with any specific feature
or development. coreboot releases exist to provide synchronization
points with downstream projects, and simply to keep version numbers
Benjamin Doron schrieb am Mi., 18. Sep. 2019,
12:34:
> Angel, the link you sent is unavailable now, but is the gist of it that I
> attempt to commit and Gerrit automatically puts it into review?
>
> Also, would this (https://doc.coreboot.org/tutorial/part2.html) be where
> the link was moved?
>
On Thu, Sep 12, 2019 at 04:46:00PM +, awokd via coreboot wrote:
> > Drivers needs support to not get in the way of later development,
> > and AGESA is sorely lacking in that department. If you see value
> > in that code, please step up now, not only when we're looking into
> > removing that
On Thu, Sep 12, 2019 at 07:20:49PM +0300, Kyösti Mälkki wrote:
> Would "some people" or these "advocates" be willing to elaborate?
I CC'd Nico and Martin because I seem to remember that we talked
about AGESA (and its quality and/or life cycle). Nico, for example,
seems to advocate scrapping AGESA
Hi everybody,
coreboot is shipping AMD's open sourced AGESA for a few generations
as part of its tree.
Some people advocate dropping the code due to its quality and lack
of maintenance while others are happy with using the code.
So: to help keep this code alive, we'd need maintainers - people
Current UEFI based firmware stores its configuration data in the SPI flash
next to the firmware code. Since you're supposed to copy your firmware
image to somewhere safe to have a way to recover, that will also contain
the latest configuration.
Patrick
Am Fr., 6. Sept. 2019 um 09:35 Uhr schrieb
On Mon, Sep 02, 2019 at 02:50:15PM +1000, Benjamin Doron wrote:
> c) The fans spin up to high and then it stays that way. It does nothing
> else. The display is dark too.
The display is approximately the last thing you'll get to work. Find
yourself some serial console connection to use (I think
Am Mo., 2. Sept. 2019 um 10:17 Uhr schrieb Timothy Pearson <
tpear...@raptorengineering.com>:
> this text needs to be completely rewritten to clearly show where the
> limits are on modern x86 platforms.
>
No, you want it rewritten to be able to better advertise Talos. This
project is not in the
Am Mo., 2. Sept. 2019 um 09:56 Uhr schrieb ron minnich :
> You need fewer adjectives, and simpler words.
>
Maybe we can get there with less bikeshedding by looking at concrete
proposals:
https://review.coreboot.org/c/homepage/+/35209 and
https://review.coreboot.org/c/homepage/+/35210 (and more
Am So., 1. Sept. 2019 um 23:55 Uhr schrieb Timothy Pearson <
tpear...@raptorengineering.com>:
> This is an interesting take on the situation. Can you point to even one
> instance in the past few years where this strategy has yielded less vendor
> proprietary firmware (in terms of percentage of
Am So., 1. Sept. 2019 um 17:30 Uhr schrieb Matt B <
matthewwbradl...@gmail.com>:
> To take an extreme stance, could non-technical users one day be directed
> to coreboot distributions like Librecore or vendors like Purism/System76?
>
Maybe we need to make the visitor segmentation more visible,
Am So., 1. Sept. 2019 um 02:23 Uhr schrieb Timothy Pearson <
tpear...@raptorengineering.com>:
> Another bad analogy: if I start a project for "maximum control" of an
> airliner, but the reality of the situation is the best level of control I
> can ever attain is how far back my seat reclines,
On Fri, Aug 23, 2019 at 10:23:06PM +0300, Kyösti Mälkki wrote:
> Is everything still under non-disclosure about those made
> compromises, or is someone willing to reveal in public what we should
> expect this time?
I don't know timelines, decisions made or agreements under which these were
made
On Fri, Aug 23, 2019 at 05:11:39PM +0300, Kyösti Mälkki wrote:
> Quoting website frontpage; "As an Open Source project it (coreboot)
> provides auditability and maximum control over technology. "
>
> FOSS to blob ratio in coreboot images, when only accounting for x86
> code, is something like 1:8
Hi Kyösti,
you're asking for leadership opinion. Stefan (who you Cc'd) is on
vacation right now.
Depending on how you define leadership, I might be part of it
(in terms of the SFC, I'm part of an adviser group to leadership).
I can't claim to speak for anybody but myself here (although I'm
The 4.10 release covers commit a2faaa9a2 to commit ae317695e3
There is a pgp signed 4.10 tag in the git repository, and a branch will
be created as needed.
In nearly 8 months since 4.9 we had 198 authors commit 2538 changes
to master. Of these, 85 authors made their first commit to coreboot:
Hi everybody,
I'm _really_ late with the 4.10 release and I'm sorry. Too much other
things intervened and then there were a few issues on a couple of targets
that were close to being fixed.
While we don't provide any guarantees for our releases, they're still a
good opportunity to try to wrap
Hi everybody,
you might notice a new column in the Gerrit UI: ACR for All-Comments-Resolved.
For a while, Gerrit allows to "resolve" comments made to changes, and this
field automatically determines if all comments are marked that way.
Another change to our Gerrit install is that changes can
Hi,
On Sat, Jul 13, 2019 at 09:22:54AM +0200, Patrick Rudolph wrote:
> I'm looking for https://review.coreboot.org/18381 which corresponds to
> 03e971cd23e96b9293fc3ecc420f56ad91326cd9.
>
> While the commit is in master I cannot access the change on gerrit.
A similar issue was brought to my
Am Do., 20. Juni 2019 um 21:47 Uhr schrieb Nico Huber :
> That's all true, but it forces an order of the tools you run. e.g.
> don't integrate clang-format into your editor because it might hide
> the problem before the compiler can warn you.
>
So don't integrate clang-format into your editor
Hey everybody,
in today's leadership meeting, the question was brought up if we want
to normalize the coding style in coreboot to _always_ use braces in
if, else and for statements, even if it's just one statement they're
wrapping.
The arguments made in favor were:
1. it's more consistent
2.
Hey Mike,
schrieb am Fr., 14. Juni 2019, 22:12:
>
>Please make sure you have the correct access rights
>and the repository exists.
>Clone of
> 'ssh://review-android.quicinc.com:29418/coreboot/chrome-ec.git' into
> submodule path '3rdparty/chromeec' failed
>
These are because we use
Alex Feinman schrieb am Fr., 14. Juni 2019, 08:46:
> When BSOD hits, you will see 4 hex values - BSOD parameters. For A5
> (ACPI_BIOS_ERROR) they can be decoded using this table:
>
> https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/bug-check-0xa5--acpi-bios-error
>
> This list
Hi Peter,
Peter Lemenkov schrieb am Mo., 27. Mai 2019, 14:58:
> Sulaco ~/work/coreboot (git::lenovo_z61t_no_ctrl_swap): git review
>
You may have to revisit the git review alias. Maybe it hardcodes the
refs/publish path?
Michal is correct in that this path was removed by the Gerrit
Hi everybody,
thanks to all contributors who voted on the issues brought up by
the coreboot leadership team. We had 119 eligible voters and three
questions.
I'll now summarize the results:
# How to handle copyright notices
https://civs.cs.cornell.edu/cgi-bin/results.pl?id=E_9e4f5ea789b9ceb9
59
Hi Denis,
Am Sa., 18. Mai 2019 um 00:19 Uhr schrieb Denis 'GNUtoo' Carikli
:
> As I'm not an expert on the strategic and legal consequences of such
> changes, I've asked around and I was pointed to some references on the
> topic:
>
Hi everybody,
as a reminder:
The voting period for various coding style issues (where to put
copyright information, line lengths, automated code formatting) ends
in a bit more than 26 hours.
So far the system has registered 53 to 60 votes (numbers vary per
question) which, at ~120 eligible
On Tue, May 14, 2019 at 12:49:17PM -0700, Julius Werner wrote:
> One thing I'm missing is an option to maintain clang-format as an
> optional pre-submit hook that people can choose run over only the
> lines their patch is touching if they want to, like I suggested in
> that thread above.
Since
On Tue, May 14, 2019 at 03:50:18PM -0400, Chris Laprise wrote:
> When I look at review.coreboot.org and the patches have logged commits
> (ostensibly, these are at least hashed) and I see "Patrick Georgi" as
> reviewer... there is no assurance of fidelity from those records?
S
On 5/14/19 Chris Laprise wrote:
> There are also several (apparently out-of-tree) patches referenced on
> the G505s howto:
>
> http://dangerousprototypes.com/docs/Lenovo_G505S_hacking
>
> I'll have to get signatures or similar type of verification for these as
> well. Any help in this regard would
Hi,
> These appear in only one place, on the coreboot.org Downloads page, and
> are signed with the key:
>
> D861AB74FB933260193399696B249D77269C04E1
>
> The only problem is there is apparently no mention of the signing key
> anywhere else on the coreboot website. I usually look for some
Hi everybody,
The project leadership asked me to get the developer community's
opinion on a couple of coding style related issues that were under
discussion for a long time without clear resolution.
To that end I just setup three elections on
https://civs.cs.cornell.edu. They're ranked votes
Hi everybody,
with this mail I'm officially starting the 4.10 release process.
As per the first step of our checklist
(Documentation/releases/checklist.md), I hereby announce the intent to
release coreboot 4.10 in about 2 weeks. I'm aiming for May 28th to avoid
releasing into the weekend or on
Hi everybody,
I think we never officially announced it: there's an email alias to post
security issues to, at secur...@coreboot.org. Right now, it's maintained by
Stefan and me, and when issues appear there we will share them with the
affected maintainers for resolution.
Technically it's a
>
> I will work on the project "Adding QEMU/AArch64 Support to Coreboot" as a
> GSoC student.
>
Welcome to coreboot!
Is it ok to communicate with mentors via this mailing list?
> Or, is it better to do it via video chat or direct email to avoid too many
> emails for other members?
>
I don't think
There was some recent cleanup on console.h includes that makes printk only
visible where we thought it was needed.
A change to add an include for console/console.h to resolve the issue here.
Cc'ing Elyes since that's his effort.
As you correctly noticed, x86emu isn't build-tested by default: If
Am Do., 11. Apr. 2019 um 17:21 Uhr schrieb Mike Banon :
> message: "", ""
> and so on.
> Maybe a segmentation fault somewhere?
>
No, it's just python being python. That thing doesn't say "it's crashing at
that position", but "the object I'm printing is at that address" because
apparently the
Am Do., 28. März 2019 um 08:48 Uhr schrieb Asami Doi :
> > We have all the MIPS architecture code in
> > coreboot, but it's falling into complete disrepair because the only
> > supported board is some old aborted Google project that nobody has
> > hardware for anymore.
> However, I couldn't find
Am Di., 19. März 2019 um 21:53 Uhr schrieb Julius Werner :
> I'm not really a fan of auto-formatters because they can just never be
> as good as a human in all cases.
As I understand Ron's argument, the idea is to accept being "less
good" than any single expert person, because it's traded in for
Am So., 17. März 2019 um 12:48 Uhr schrieb Swapnil Rustagi
:
> Hmm, I have a Ubuntu laptop, and I can buy a Raspberry Pi, if you want ARM
> architecture as well,
That's useful as development system, but you will only be able to test
coreboot on emulated targets then. Which brings us to:
> but I
Am Sa., 16. März 2019 um 18:16 Uhr schrieb Ron Minnich :
> > More generally speaking, I don't care on what we agree here, I just don't
> > want to hear about that crap anymore, so please let's agree on something.
>
> yeah.
>
> It's easy. Hand it all off to an automated formatter, don't insist on
Hi Nico,
(I Cc'd a few folks to make sure this bubbles up in their mailboxes because
they engaged in that type of discussion which made this current round
necessary)
Thanks for starting this thread. Let's make sure that it's the last one on
this topic.
Nico Huber schrieb am Sa., 16. März 2019,
Am Sa., 16. März 2019 um 14:51 Uhr schrieb Nico Huber :
> There is a lint test, that so far never did something for me because
> it relies on a `.clang-format-scope` file (that is not in the tree?).
> Still, this check seems to be actively maintained.
The idea was to slowly migrate the tree to
The fastboot functionality mentioned there is most likely part of the
depthcharge payload[0], which is based on the USB device mode drivers
in libpayload[1].
fastboot in coreboot would mix up the responsibilities (coreboot:
initialize hardware, payload: provide boot policy).
Patrick
[0]
It's more reliable to not add special cases and more recently the queue was
never long enough to warrant any such risk.
Mike Banon schrieb am Sa., 23. Feb. 2019, 16:44:
> On Sat, Feb 23, 2019 at 6:38 PM Patrick Georgi wrote:
> >
> > There are a few lint tests that check the
There are a few lint tests that check the commit message.
Patrick
Mike Banon schrieb am Sa., 23. Feb. 2019, 16:31:
> It is guaranteed that, if I changed only the commit message, the
> results of a previous build ("success +1 / failure -1") will be
> repeated for a change. So it is probably a
It's also possible to make Linux (with included ramdisk) into a
payload, so maybe that could be a middle ground: It's still usable by
all payloads that can execute payloads, it's still Linux + userland in
a more or less normal configuration. It has some overhead, but OTOH
brings the peace of mind
Also, there may be users interested in the "whole" UEFI experience,
with secure boot validating binaries loaded from a https server via
their infiniband controllers and IPoIB implemented by on-PCIe firmware
delivered as EBC bytecode. I don't see yabits providing support for
that.
Patrick
Am
Am Do., 14. Feb. 2019 um 18:47 Uhr schrieb Vadim Bendebury
:
> Why does it have to be done by Seabios as opposed to Linux? It is easy to
> create a USB stick which would boot Linux compiled with permissions needed
> and with startup files which will program the new firmware image. This would
>
Am Fr., 8. Feb. 2019 um 11:02 Uhr schrieb Ivan Ivanov :
> If you need Secureboot you could use countless of proprietary UEFI boards.
There are users that put Tianocore-as-payload on top of coreboot, and
while this probably isn't the most common use case, it's just as valid
as any other payload.
Hi everybody,
I just want to remind you that we're applying for GSoC this year and
for planning reasons they want us to state how many mentors we expect
to have.
So if you're interested to potentially help a student get up to speed
on a firmware related topic (coreboot or nearby projects),
fforts for
> coreboot.
>
> On 01/16/2019 04:01 PM, Patrick Georgi via coreboot wrote:
> > Dear coreboot community,
> >
> > I'm preparing the application to have coreboot participate in this
> > year's Google Summer of Code.
> > There are two thin
Dear coreboot community,
I'm preparing the application to have coreboot participate in this
year's Google Summer of Code.
There are two things we should think about until early February for this:
1. We'll need some project proposals, for which I started
Hi everybody,
I took the opportunity of the slow season to make some changes to the mail
server configuration: it's moved to another server and the mailing lists
are now driven by mailman3 (before: mailman2) with hyperkitty as mailing
list archive system (before: pipermail).
I'm still importing
coreboot 4.9 release notes
==
The 4.9 release covers commit 532b8d5f25 to commit 7f520c8fe6
There is a pgp signed 4.9 tag in the git repository, and a branch will
be created as needed.
In the little more than 7 months since 4.8.1 we had 175 authors commit
2610 changes to
Hi everybody,
just a friendly reminder that I plan to do the coreboot 4.9 release on Dec
20th, which is
next Thursday!
Please test master, report or fix issues and be considerate with what
you're merging (ie. maybe don't land the Rewrite Of Everything before the
release). I'd like to avoid the
Hi everybody,
as Martin is swamped by other work, I'm taking over as the release manager
for 4.9.
Based on our schedule, we should have released 4.9 in October or early
November, but since those passed, I'll plan to release 4.9 two weeks from
now, on December 20th.
If you want, consider it an
Hi Werner,
thanks for getting the discussion back on track :-)
Am Fr., 30. Nov. 2018 um 09:23 Uhr schrieb Zeh, Werner <
werner@siemens.com>:
> Speaking of the two chipsets in question in this thread I do not see the
> real demand of getting rid of them yet.
Why is coreboot not able to move
Am Do., 29. Nov. 2018 um 23:07 Uhr schrieb Timothy Pearson <
tpear...@raptorengineering.com>:
> On the POWER9 topic, it might even be possible to skip QEMU and go
> straight to hardware.
QEMU ports have the advantage that they're easier to hook up into boot test
environments.
They're also much
101 - 200 of 1448 matches
Mail list logo
