- 25 1月, 2013 1 次提交
-
-
由 David 'Digit' Turner 提交于
A QEMU pipe is a very fast communication channel between the guest system and the emulator. Usage from the guest is simply something like; // connect to special device fd = open("/dev/qemu_pipe", O_RDWR); // tell which service we want to talk to (must be zero-terminated) write(fd, "pipeName", strlen("pipeName")+1); // do read()/write() through fd now ... // close channel close(fd); Signed-off-by: NDavid 'Digit' Turner <digit@android.com> [Added support for parameter buffers for speed] igned-off-by: NXin, Xiaohui <xiaohui.xin@intel.com> Signed-off-by: NJiang, Yunhong <yunhong.jiang@intel.com> Signed-off-by: NNakajima, Jun <jun.nakajima@intel.com> [Ported to 3.6] Signed-off-by: NTom Keel <thomas.keel@intel.com> [Ported to 3.7, moved to platform/goldfish] Signed-off-by: NAlan Cox <alan@linux.intel.com> Signed-off-by: NGreg Kroah-Hartman <gregkh@linuxfoundation.org>
-
- 09 11月, 2009 1 次提交
-
-
由 Michael Roth 提交于
Additionally, some excessive newlines removed. Signed-off-by: NMichael Roth <mroth@nessie.de> Signed-off-by: NJiri Kosina <jkosina@suse.cz>
-
- 19 12月, 2008 1 次提交
-
-
由 Len Brown 提交于
Move x86 platform specific drivers from drivers/misc/ to a new home under drivers/platform/x86/. The community has been maintaining x86 vendor-specific platform specific drivers under /drivers/misc/ for a few years. The oldest ones started life under drivers/acpi. They moved out of drivers/acpi/ because they don't actually implement the ACPI specification, but either simply use ACPI, or implement vendor-specific ACPI extensions. In the future we anticipate... drivers/misc/ will go away. other architectures will create drivers/platform/<arch> Signed-off-by: NLen Brown <len.brown@intel.com>
-