search for: bootmode

...C device has failed to reset. + + When written, this sysfs entry triggers different state change + operations depending upon the current state of the card OS. + Acceptable values are: + "boot" - Boot the card OS image specified by the combination + of firmware, ramdisk, cmdline and bootmode + sysfs entries. + "reset" - Initiates device reset. + "shutdown" - Initiates card OS shutdown. + +What: /sys/class/mic/mic(x)/shutdown_status +Date: August 2013 +KernelVersion: 3.11 +Contact: Sudeep Dutt <sudeep.dutt at intel.com> +Description: + An Intel MIC devic...

...ram also check the registry for the boot media. I tried to manually change it from Ramdisk to CDROM, but before it check the registry it call a program named wpeutil and this change the registry back to Ramdisk. I also can't rename the wpeutil because than the program fail. I tried to set the bootmode to legancy and was able to boot and run the program, but before start to recover the system it checks the boot mode and than it fails with the message that it isn't set to EFI. The previos version of the recovery CD (WinXP and Win7) use a similar script, but doesn't require EFI. I also ca...

...registry for the boot media. > I tried to manually change it from Ramdisk to CDROM, but before it check the registry it call a program named wpeutil and this change > the registry back to Ramdisk. I also can't rename the wpeutil because than the program fail. > > I tried to set the bootmode to legancy and was able to boot and run the program, but before start to recover the system it checks the > boot mode and than it fails with the message that it isn't set to EFI. > > The previos version of the recovery CD (WinXP and Win7) use a similar script, but doesn't require E...

Am 12. Juli 2013 15:06:54 schrieb Matt Fleming <matt at console-pimps.org>: > Which installer? I would hazard a guess that the installer is also bios > specific and is going to need to be tailored for EFI boot anyway. > > -- > Matt Fleming, Intel Open Source Technology Center It's a little be complex. It's a DVD based installer where I try to change this to be

...block diagram: a) Boots and shuts down the card via sysfs entries. b) Allocates and maps a device page for communication with the card driver and updates the device page address via scratchpad registers. c) Provides sysfs entries for shutdown status, kernel command line, firmware, ramdisk, bootmode and log buffer information. Patch 4: This patch introduces the "Intel MIC Card Driver" in the block diagram which does the following: a) Initializes the Intel MIC X100 platform device and driver. b) Sets up support to handle shutdown requests from the host. c) Maps the device page after...

...block diagram: a) Boots and shuts down the card via sysfs entries. b) Allocates and maps a device page for communication with the card driver and updates the device page address via scratchpad registers. c) Provides sysfs entries for shutdown status, kernel command line, firmware, ramdisk, bootmode and log buffer information. Patch 4: This patch introduces the "Intel MIC Card Driver" in the block diagram which does the following: a) Initializes the Intel MIC X100 platform device and driver. b) Sets up support to handle shutdown requests from the host. c) Maps the device page after...

...block diagram: a) Boots and shuts down the card via sysfs entries. b) Allocates and maps a device page for communication with the card driver and updates the device page address via scratchpad registers. c) Provides sysfs entries for shutdown status, kernel command line, firmware, ramdisk, bootmode and log buffer information. Patch 4: This patch introduces the "Intel MIC Card Driver" in the block diagram which does the following: a) Initializes the Intel MIC X100 platform device and driver. b) Sets up support to handle shutdown requests from the host. c) Maps the device page after...

...block diagram: a) Boots and shuts down the card via sysfs entries. b) Allocates and maps a device page for communication with the card driver and updates the device page address via scratchpad registers. c) Provides sysfs entries for shutdown status, kernel command line, firmware, ramdisk, bootmode and log buffer information. Patch 4: This patch introduces the "Intel MIC Card Driver" in the block diagram which does the following: a) Initializes the Intel MIC X100 platform device and driver. b) Sets up support to handle shutdown requests from the host. c) Maps the device page after...

...nd shuts down the card via sysfs entries. > b) Allocates and maps a device page for communication with the > card driver and updates the device page address via scratchpad > registers. > c) Provides sysfs entries for shutdown status, kernel command line, > firmware, ramdisk, bootmode and log buffer information. > > Patch 4: This patch introduces the "Intel MIC Card Driver" in the block > diagram which does the following: > a) Initializes the Intel MIC X100 platform device and driver. > b) Sets up support to handle shutdown requests from the host. >...

...*dev, struct device_attribute *attr, char *buf) static ssize_t mic_store_ramdisk(struct device *dev, struct device_attribute *attr, - const char *buf, size_t count) + const char *buf, size_t count) { struct mic_device *mdev = dev_get_drvdata(dev->parent); @@ -334,7 +334,7 @@ mic_show_bootmode(struct device *dev, struct device_attribute *attr, char *buf) static ssize_t mic_store_bootmode(struct device *dev, struct device_attribute *attr, - const char *buf, size_t count) + const char *buf, size_t count) { struct mic_device *mdev = dev_get_drvdata(dev->parent); @@ -368,7 +3...