search for: coreboot

Hi, I am looking into using coreboot to speed up the booting of my HTPC, while looking at the payloads they offer I thought that perhaps a syslinux derivative would be nice to have as a payload due to it's flexibility. Is this possible? or something you would be interested in adding support for? Regards, Ryan

...s Model comes from this fairly simple question : What is the value-added from an OEM point of view to need 3rd parties to provide an Hypervisor Layer knowing that Virtualization is a feature from the Hardware (so it belongs to the CPU / Chipset / OEM World) and they are not necessary to enable it (coreboot AVATT prototype is the most successful example [1]), however they are making the greatest benefits from it ? To quote [2] : "There's actually a lot to be said for the embedded hypervisor. Lots of IT environments--especially enterprise ones--do indeed have a mix of operating systems an...

...s Model comes from this fairly simple question : What is the value-added from an OEM point of view to need 3rd parties to provide an Hypervisor Layer knowing that Virtualization is a feature from the Hardware (so it belongs to the CPU / Chipset / OEM World) and they are not necessary to enable it (coreboot AVATT prototype is the most successful example [1]), however they are making the greatest benefits from it ? To quote [2] : "There's actually a lot to be said for the embedded hypervisor. Lots of IT environments--especially enterprise ones--do indeed have a mix of operating systems an...

I was doing a laptop repair job today and needed to boot from a USB thumb drive, in order to free up the CD/DVD burner. Fortunately, the laptop to be repaired permitted one to boot from a USB thumb drive. However, there are still PCs out there that can't boot from a thumb drive (I have two), so I was wondering if it's pos to use the CHAIN module to boot from a thumb drive ? I looked at

...After an analysis of the various solutions (Citrix, VMware and Microsoft), it seemed natural to our eyes, to enable a true bare-metal hypervisor, to go as close as possible to the hardware, hence the BIOS. That's why we are currently going further since the first successful prototype of the coreboot GSOC project AVATT (All Virtual All The Time) [1] [2]. Coreboot is an open source hardware initialization firmware. It does some basic hardware init, then hands over control to one of many possible payloads. This Google Summer of Code sponsored project suggested the idea of implementing a Linux k...

[CC?ing coreboot, GRUB, SeaBIOS, Syslinux project and Linux kernel] Am Montag, den 16.03.2015, 11:38 +0100 schrieb Kay Sievers: > On Mon, Mar 16, 2015 at 11:29 AM, Umut Tezduyar Lindskog wrote: > > I would like to pass the time it was spent in bootloader to systemd. > > Is there a kernel command lin...

...rmware-jenkins edk2.git-arm.noarch 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins edk2.git-ovmf-x64.noarch 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins edk2.git-tools.x86_64 0-20180612.181.g2aedaaef8a @qemu-firmware-jenkins coreboot.git.x86_64 4.8-599.333.g1bf411c743 @qemu-firmware-jenkins coreboot.git-tools.x86_64 4.8-599.333.g1bf411c743 @qemu-firmware-jenkins qemu-common.x86_64 2:2.0.0-1.el7.6 @epel qemu-guest-agent.x86_64...

...rive using standard BIOS > > or EFI interfaces. > > > > Now, if you are using EFI, you might just want to consider just running > the kernel itself as an EFI executable. > > If with "bootloader in memory" you mean the whole firmware package, > look at EDK2, Coreboot, or uboot. > > -hpa > Hi Thanks a lot for the answers given. I think I should change this conversion topic to "storing the bootloader inside the BIOS chip" or something similar. I now understand a little bit more about the boot process and see that it is more complicated tha...

On 01/13/16 00:13, Tal Lubko via Syslinux wrote: > > OK. I'll try that. > Any thoughts regarding the requirement to store the bootloader inside the BIOS chip? > That is fundamentally up to your BIOS. The best is to expose the bootloader in the BIOS as a (readonly) disk drive using standard BIOS or EFI interfaces. -hpa

Hello, on my journey to debug some things i stumbled over this. Perhaps this could be usefull. just a suggestion for a feature to implement: EHCI Debug Port As more and more pc?s are legacy free.. so no serial port for debuging, this could be interesting, http://www.coreboot.org/EHCI_Debug_Port It is already used in the linux kernel and there is also a linux module that acts as a debug monitor/device on the other side. So you can use your linux workstation to get those logs. https://www.kernel.org/doc/Documentation/x86/earlyprintk.txt and http://www.coreboot.or...

I've tracked down the issue to the seabios package being updated to 1.7.4-1 from 1.7.3-3. When Xen is built with the older version, everything works fine. In fact, I bisected the issue down to the following SeaBIOS commit: http://review.coreboot.org/gitweb?p=seabios.git;a=commit;h=e144bb7af49ca8756b7222a75811f3b85b0bc1f5 I don't know if this group is interested in tracking down the regression, but you should be aware that any rebuilding of the Xen packages (even with the current source) will pull in this regression since seabios-1.7.4...

...gt; > or EFI interfaces. >> > >> >> Now, if you are using EFI, you might just want to consider just running >> the kernel itself as an EFI executable. >> >> If with "bootloader in memory" you mean the whole firmware package, >> look at EDK2, Coreboot, or uboot. >> >> -hpa >> > > Hi > > Thanks a lot for the answers given. > I think I should change this conversion topic to "storing the bootloader > inside the BIOS chip" or something similar. > I now understand a little bit more about the boot proc...

When using the 4.3.0-3/4.3.0-3+b1 xen packages from the Debian archive, things work fine. However, when we compile the xen=4.3.0-3 source package ourselves, we run into an issue launching an HVM. As soon as the HVM bios is loaded, VCPU0 gets a triple fault and the HVM is destroyed (this is with "loglvl=all guest_loglvl=all hvm_debug=3" boot options). (XEN) HVM1: Multiprocessor

...ry requirements? Menu.c32 fails on a 2MB QEMU system, same for CHAIN.C32, yet Isolinux (and Syslinux) load fine if no com32 is loaded. Memdisk also loads fine (only tested with 360K floppy image). I haven't tried 1MB QEMU (hangs on win32 due to either QEMU or SeaBIOS or bug) nor 0MB system (Coreboot with Cache-As-Ram in theory). * There doesn't seem to be a fallback to text-only mode for the UI parameter in case of low memory situations. Physical systems have 4MB already at the very least, but loading an ISO into RAM followed by booting it can get you into situations where there's...

...t;> > > >> > >> Now, if you are using EFI, you might just want to consider just > >> running the kernel itself as an EFI executable. > >> > >> If with "bootloader in memory" you mean the whole firmware package, > >> look at EDK2, Coreboot, or uboot. > >> > >> -hpa > >> > > > > Hi > > > > Thanks a lot for the answers given. > > I think I should change this conversion topic to "storing the > > bootloader inside the BIOS chip" or something similar. > > I no...

...IOAPIC entry. Then, Xen will do interrupt remapping at least for the SB IOAPIC. I modified the Xen source to ignore this second entry, and get the dmesg shown below. My system seems to run fine after the change. 2) Properly configure the NB IOMMU, even if just as set out in 6.4.1. http://review.coreboot.org/gitweb?p=coreboot.git;a=blob;f=src/vendorcode/amd/cimx/rd890/nbIoApic.c which I understand to be from CIMX, has the necessary code. I suppose if it came down to it, you could add code to Xen to bang in the necessary configuration via the 10 indirect registers for the NB IOMMU to match up with...

...SPICE - Virtual GPU - virtio and vhost, including non-Linux or non-virtualized uses - Hardening and security - New storage features - Live migration and fault tolerance - High availability and continuous backup - Real-time guest support - Emulation and TCG - Firmware: ACPI, UEFI, coreboot, u-Boot, etc. - Testing Management and infrastructure - Managing KVM: Libvirt, OpenStack, oVirt, etc. - Storage: glusterfs, Ceph, etc. - Software defined networking: Open vSwitch, OpenDaylight, etc. - Network Function Virtualization - Security - Provisioning - Performance tuning...

...SPICE - Virtual GPU - virtio and vhost, including non-Linux or non-virtualized uses - Hardening and security - New storage features - Live migration and fault tolerance - High availability and continuous backup - Real-time guest support - Emulation and TCG - Firmware: ACPI, UEFI, coreboot, u-Boot, etc. - Testing Management and infrastructure - Managing KVM: Libvirt, OpenStack, oVirt, etc. - Storage: glusterfs, Ceph, etc. - Software defined networking: Open vSwitch, OpenDaylight, etc. - Network Function Virtualization - Security - Provisioning - Performance tuning...

...iggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources? blkif-drivers-explained.txt? For a start, Grub has a Coreboot port, which is ELF, but the Xen 3.2 domain builder refuses to load it saying: xc_dom_parse_elf_kernel: ELF image has no shstrtab -- Thanks, Feri. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel

...iggybacking the Mini-OS environment usin kexec as I tried. But they need some documentation on the Xen "firmware" to assess the task at least. What could be given to them apart from hvc_xen.c and xen-blkfront.c in the Linux sources? blkif-drivers-explained.txt? For a start, Grub has a Coreboot port, which is ELF, but the Xen 3.2 domain builder refuses to load it saying: xc_dom_parse_elf_kernel: ELF image has no shstrtab -- Thanks, Feri. _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel