Hi,
On 01/21/2017 02:30 PM, Paul Menzel via coreboot wrote:
Dear coreboot folks,
Playing around with the trace feature of the Dediprog EM100Pro, I
noticed several flash ROM accesses until the payload is loaded.
Are there ways or strategies to preload the whole flash ROM chip
content into
On Sat, Jan 21, 2017 at 2:32 PM Paul Menzel via coreboot <
coreboot@coreboot.org> wrote:
>
>
> Are there ways or strategies to preload the whole flash ROM chip
> content into memory for faster access right after RAM is set up for
> example? What does that depend on? Does that make any sense at
Paul Menzel via coreboot wrote:
> Are there ways or strategies to preload the whole flash ROM chip
> content into memory for faster access right after RAM is set up for
> example? What does that depend on? Does that make any sense at all?
That's called BIOS shadowing and was popular at least in
Addressing over 8G is not supported by the chipset used on nehalem thinkpad
laptops (X201)
Stupid limitation, but it is not the CPU fault.
On Sat, Jan 21, 2017 at 5:55 AM, Stefan Tauner <
stefan.tau...@alumni.tuwien.ac.at> wrote:
> Hi Vladimir,
>
> since you have REed the raminit for Nehalem
Dear coreboot folks,
Playing around with the trace feature of the Dediprog EM100Pro, I
noticed several flash ROM accesses until the payload is loaded.
Are there ways or strategies to preload the whole flash ROM chip
content into memory for faster access right after RAM is set up for
example?
Hi Vladimir,
since you have REed the raminit for Nehalem I'd like you to ask if you
have any knowledge, information or pointers about using 8 GB DIMMs with
it or even using more than 8 GB in total. In my case it is about an
Arrandale i5-520M (in a Thinkpad 410s).
I know that an i7-820QM
Logs (thought I would separate them)
ARI-fwd+ on the root port devcap and devctl but it doesn't have ARI
listed in capabilities, I am not sure if lspci should report that on a
root port as there is so little documentation for IOMMU/SR-IOV on the
internet
07:00.3 Ethernet controller: Intel
It seems the PCI-e root ports on the KGPE-D16 have ARI which is needed
for SR-IOV, however it is not reported via # lspci -vv
I assume that is why the VF's are not assigned to IOMMU groups and thus
can't be assigned.
I am running coreboot v4.5 (I forgot to note this as it is another late
Assigning regular devices such as a graphics card to a VM works just
fine, but when I try to assign an intel i350 virtual function I receive
the error
"error: internal error: Invalid device :07:10.0 iommu_group file
/sys/bus/pci/devices/:07:10.0/iommu_group is not a symlink"
The
9 matches
Mail list logo
