Re: [coreboot] About Paging, Realmode and what is going on

On Wed, Aug 2, 2017 at 1:38 PM Philipp Stanner wrote: > Dear Patrick, dear Zoran & List, > > thank you, this was *very* helpful. I had some misunderstandings regarding > function and features of the CPU-modes. > > Let me sum it up again and feel free to correct further

Re: [coreboot] how effective is neutralizing Intel ME/AMT/vPro?

On 02/08/17 20:43, ron minnich wrote: > > > On Wed, Aug 2, 2017 at 11:48 AM Daniel Pocock > wrote: > > I understand that with LibreBoot and one of their supported laptops it > is possible to completely eliminate the risk by removing 100% of >

Re: [coreboot] About Paging, Realmode and what is going on

Dear Patrick, dear Zoran & List, thank you, this was *very* helpful. I had some misunderstandings regarding function and features of the CPU-modes. Let me sum it up again and feel free to correct further mistakes. * 16-Bit-Real Mode: No virtual memory, no segmentation. 2^20 addresses of

Re: [coreboot] About Paging, Realmode and what is going on

right, Aaron, you keep reminding me of that and I keep forgetting it :-) so, ok, ramstage it is for paging. The x86 is so darned annoying. We had paging in the bootblock for PPC on linuxbios. On Wed, Aug 2, 2017 at 12:43 PM Aaron Durbin wrote: > On Wed, Aug 2, 2017 at 1:36

Re: [coreboot] how effective is neutralizing Intel ME/AMT/vPro?

On Wed, Aug 2, 2017 at 11:48 AM Daniel Pocock wrote: > I understand that with LibreBoot and one of their supported laptops it > is possible to completely eliminate the risk by removing 100% of > proprietary/hidden code. > I'm glad they did this but ... you need to understand

Re: [coreboot] About Paging, Realmode and what is going on

On Wed, Aug 2, 2017 at 1:36 PM, ron minnich wrote: > > > On Wed, Aug 2, 2017 at 12:08 PM Zoran Stojsavljevic > wrote: >> >> >> >> So, turning on the Virtual Mode (paging ON), you'll also imply that >> Coreboot will initialize and use MMU, don't

Re: [coreboot] About Paging, Realmode and what is going on

On Wed, Aug 2, 2017 at 12:08 PM Zoran Stojsavljevic < zoran.stojsavlje...@gmail.com> wrote: > > > So, turning on the Virtual Mode (paging ON), you'll also imply that > Coreboot will initialize and use MMU, don't you? > sure. > > Am I correct, or you can use paging without MMU?! > MMU must be

Re: [coreboot] About Paging, Realmode and what is going on

2017-08-02 21:08 GMT+02:00 Zoran Stojsavljevic : > And my question is: what for? Or I did not get the idea... Who really needs > to use paging in boot-loaders? Even INTEL, which (on purpose) makes things > way over-dimensioned and over-complicated, does NOT use

Re: [coreboot] About Paging, Realmode and what is going on

Hey Ron, > You can't enter long mode (x86-64) mode without enabling paging. you need long mode if you need to operate on more than 2^36 bytes > of memory. That's coming everywhere. Hence,* the future of coreboot is unambiguously one in which paging is on and at least* *> in my case** I found it's

Re: [coreboot] Broadwell-U hangs at VGA init (update)

On 02.08.2017 15:18, Zheng Bao wrote: > i just replace the bios region with my coreboot and other parts of ibv > image untouched. is it a right way? Is that a fresh image from the IBV? or a backup from a working system? The ME firmware can store some state in its flash region and it doesn't

[coreboot] how effective is neutralizing Intel ME/AMT/vPro?

I've seen various web sites about ME_Cleaner[1] and also the strategies[2] used by Purism to avoid Intel ME/AMT/vPro I understand that with LibreBoot and one of their supported laptops it is possible to completely eliminate the risk by removing 100% of proprietary/hidden code. However, for

Re: [coreboot] About Paging, Realmode and what is going on

I'll try not to mess this explanation up too much, but it's partly from the docs and partly what we've learned over the years. I am assuming that you've at least looked at the coreboot boot block and read some of the x86 docs, although from this note and previous notes you have written I'm still

[coreboot] About Paging, Realmode and what is going on

Hello everybody, following the mailing list about the questions posed by Philipp Stanner I read: "Why does every modern CPU still start in RM? Many industries run on DOS. Many system developers have created in-house BIOS extensions. x86 will never fully lose its 16-bit legacy." I'm agree with

Re: [coreboot] About Paging, Realmode and what is going on

Hello Philipp, There are lot of confusion you have created with your naming convention... So we need here to "Divide and Concur", since this thread really remains me of Spaghetti Bologneze. Here is the partial picture how x86 operates: [image: Inline image 1] So you see here three modes, you

Re: [coreboot] Broadwell-U hangs at VGA init (update)

i just replace the bios region with my coreboot and other parts of ibv image untouched. is it a right way?what kinds of issue do you mean? 2017年8月2日 18:58于 Nico Huber 写道： On 02.08.2017 04:23, Zheng Bao wrote: > src/soc/intel/broadwell/lpc.c > /* Initialize power

Re: [coreboot] About Paging, Realmode and what is going on

On 01.08.2017 16:49, Peter Stuge wrote: Note that PM != paging. Neither coreboot nor proprietary BIOS products used paging traditionally. Ron pushed for paging, there was a bit of support. I don't know the current situation though. Also note that PM != "flat real mode" or "32-bit real mode",

Re: [coreboot] Broadwell-U hangs at VGA init (update)

On 02.08.2017 04:23, Zheng Bao wrote: > src/soc/intel/broadwell/lpc.c > /* Initialize power management */ > //pch_power_options(dev); > //pch_pm_init(dev); > printk(BIOS_INFO, "%s,%d.\n", __func__, __LINE__); > //pch_cg_init(dev); > printk(BIOS_INFO, "%s,%d.\n", __func__,

[coreboot] [RFC] How to deal with unchanged images in board status repository?

Dear coreboot folks, Thanks to Nico’s introduction of “timeless”/“comparable” builds in commit 566dd357 (Add option for "timeless" builds) [1], it’s for example possible to find out, if a commit changed something for a certain board. > Builds with BUILD_TIMELESS=1 shall always give a bit

Re: [coreboot] Fwd: [FWD: Request for Chromebook Authentication Module Development]

On Tue, Aug 1, 2017 at 10:54 PM, David Hendricks wrote: > Hi Victor, > IMO this is really more of a feature for the Out Of Box Experience (OOBE) > rather than coreboot or seabios. > Just to clarify, OOBE refers to a specific set of routines - I believe within the

[coreboot] [Broadwell-U]How the eDP, DDI1, DDI2 are enabled?

- # Enable eDP Hotplug with 6ms pulse register "gpu_dp_d_hotplug" = "0x06" # Enable DDI1 Hotplug with 6ms pulse register "gpu_dp_b_hotplug" = "0x06" # Enable DDI2 Hotplug with 6ms pulse register "gpu_dp_c_hotplug" = "0x06" # Set