Hello!
Peter something else that needs to be mentioned is that the backend
you've mentioned here, and of course is (partially) documented on the
Wiki, is that according to Google Code, it is in archive only status.
That means that everything there is in its final status. Nothing new
will be
On Thu, Oct 5, 2017 at 11:09 PM, taii...@gmx.com wrote:
> I have an H8SCM, but have never successfully booted it with coreboot due to
> being lazy.
>
> I have a test clip and would be willing to test any changes.
Great!
We have this thing called git repository, you know. Please
Hello Nico,
> you might have to accept that adding VGA compatibility for Windows may
> break compatibility with the secondary payloads. That"s not generally
> the case but about the last thing that gets tested.
From what I have learned so far it seems that the usecase Coreboot + Windows is
that
I have an H8SCM, but have never successfully booted it with coreboot due
to being lazy.
I have a test clip and would be willing to test any changes.
--
coreboot mailing list: coreboot@coreboot.org
https://mail.coreboot.org/mailman/listinfo/coreboot
Anshuman Aggarwal wrote:
> Out of curiosity, is this a limitation to what is possible in the BIOS
> or that nobody has found the need to do this sort of remote control
> using the BIOS yet?
There are a few things that you would need to consider.
For legacy compatibility you require a VGA BIOS
I've got a supermicro H8SCM board, although I don't think I've ever tried
to boot it, so I don't know its state. I also suspect that it's got a
family 10h processor, not a fam15.
I can try to get it set up this weekend, and I can bring it to the
conference with me if that would help.
Here's the
Hi
I can remember exactly one user of AGESA fam15 code from the past 5
years or so. He has informed me of having no possibility to test with
the H8QGI he once had access to and as the little discussion on this
list about H8SCM also appears seized now, I have to inform none of the
AGESA fam15
oreboot.org<mailto:coreboot@coreboot.org>
https://mail.coreboot.org/mailman/listinfo/coreboot
-- next part --
An HTML attachment was scrubbed...
URL:
<http://mail.coreboot.org/pipermail/coreboot/attachments/20171005/8f721b2e/attachment-0001.html>
---
Hi Zoran,
Thanks for your suggestion. I’ll try.
-Hilbert
From: Zoran Stojsavljevic [mailto:zoran.stojsavlje...@gmail.com]
Sent: Thursday, October 05, 2017 11:27 AM
To: Hilbert Tu(杜睿哲_Pegatron)
Cc: coreboot@coreboot.org
Subject: Re: [coreboot] Broadwell-DE NS FSP not support
Hello Hilbert,
You
On Thu, Oct 5, 2017 at 2:55 AM Anshuman Aggarwal <
anshuman.aggar...@gmail.com> wrote:
>
>
> @ron, I assume you mean a livecd like alternative which I can connect
> to and use to debug the issue?
>
no, I mean putting the kernel in firmware and using the network as the
equivalent of a serial
Well. well, well... We have here major architectural break?! It seems that
IFWI is after all replacing FSP (as clean cut first stage boot-loader)???
FSP is going to slip to oblivion, don't you all think?
It seems that we have here new, two stage boot-loader approach, with MBR
sector, containing
On 10/05/2017 05:54 AM, Anshuman Aggarwal wrote:
@Taiidan, as much as I love all things libre, my budget doesn't come
close to buying those motherboards :(. I like the idea of using
another machine to view the grub serial. Maybe using a Raspberry Pi
RPI isn't free hardware and the RPI
@Taiidan, as much as I love all things libre, my budget doesn't come
close to buying those motherboards :(. I like the idea of using
another machine to view the grub serial. Maybe using a Raspberry Pi
etc.
@ron, I assume you mean a livecd like alternative which I can connect
to and use to debug
Hi Zoran/Piotr,
Yes, the current available FSP does not support BDX-DE NS. I got same
information from local Intel FAE. So I don’t know the next step to evaluate my
CRB.
@Taiidan,
Thanks for your information, “6 months for skilled person” ☺ Maybe I should try
BIOS/UEFI first.
-Hilbert
14 matches
Mail list logo