Evening!
Alright so I built against the latest master, enabled all the root ports
(0-12), disabled the NVME (root port 8)? for good measure (although I also
tried with it remaining enabled).
I still don't see the device under either "pci" in the EFI shell or under
"lspci" once Ubuntu is booted.
On Mon, 9 Dec 2019 18:54:18 +0200
Kyösti Mälkki wrote:
[f2a85m-pro broken on master]
> Weird. Seems like I let the devicetree in a bit of a bad shape back
> in 2015. Try if this makes any difference:
> https://review.coreboot.org/c/coreboot/+/37619
I tried that through the normal/fallback
On Mon, 9 Dec 2019 02:20:29 +0200
Kyösti Mälkki wrote:
[E350M1]
> You want to rebase your changes on pcengines/apu1 transition [1]
> which is the first fam14 board to drop ROMCC_BOOTBLOCK.
>
> [1] https://review.coreboot.org/c/coreboot/+/37332/11
I've done that, and after build it, flashing it
On Mon, 9 Dec 2019 02:20:29 +0200
Kyösti Mälkki wrote:
> On Mon, Dec 9, 2019 at 1:53 AM Denis 'GNUtoo' Carikli
> wrote:
> > I've tried to do the same for the E350M1 and I end up with:
> > > [...]/i386-elf-ld.bfd: build/bootblock/arch/x86/bootblock_crt0.o:
> > > in function `enable_sse':
> > >
The 1.13.0 version of SeaBIOS has now been released. For more
information on the release, please see:
http://seabios.org/Releases
New in this release:
* Support for reading logical CHS drive information from QEMU
* Workaround added for misbehaving optionroms that grab "int19"
* The TPM 2 "PCR
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
Hi Seth,
On Mon, Dec 9, 2019, 19:02 Seth Rosenblatt wrote:
> 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 from
> Coreboot if you
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 from
Coreboot if you want to send one over.
On Sun, Dec 8, 2019 at 1:40 PM David Hendricks
On Mon, Dec 9, 2019 at 5:48 PM Denis 'GNUtoo' Carikli
wrote:
>
> On Sun, 8 Dec 2019 18:49:26 +0200
> Kyösti Mälkki wrote:
> > > - What to do if the board doesn't boot anymore with master
> > > (f2a85m-pro)? Should I bisect the issue first? Or would the
> > > conversion be able to fix the
On 09.12.2019 05:36, Matt B wrote:
> Hi,
Hi Matt,
>
> Thanks for the pointer.
>
> I need a bit more context here, being completely unfamiliar with how
> coreboot works.
> I've never done any non-userspace programming, and this is the first
> time I've gotten a freshly-compiled coreboot to actually
On Sun, 8 Dec 2019 18:49:26 +0200
Kyösti Mälkki wrote:
> > - What to do if the board doesn't boot anymore with master
> > (f2a85m-pro)? Should I bisect the issue first? Or would the
> > conversion be able to fix the issue?
>
> Bisect first and return master to a working state please. There
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.
Yes, I have it configured globally using ~/.gitconfig file
[http]
sslVerify = false
proxy =
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
Hi,
I'm still stuck with the same error trying to push anything.
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
16 matches
Mail list logo
