/linux/tools/arch/x86/dell-uart-backlight-emulator/ |
H A D | Makefile | 4 dell-uart-backlight-emulator: dell-uart-backlight-emulator.c 15 @rm -f dell-uart-backlight-emulator 17 install : dell-uart-backlight-emulator 19 install -m 755 -p dell-uart-backlight-emulator $(DESTDIR)$(BINDIR)/dell-uart-backlight-emulator
|
H A D | README | 15 This small emulator allows testing 32 ./dell-uart-backlight-emulator <path-to-/dev/tty*S#-for-second-port> 36 ./dell-uart-backlight-emulator /dev/ttyUSB0 43 the firmware version string from the emulator. If this works there 46 by matching output from the emulator.
|
H A D | .gitignore | 1 dell-uart-backlight-emulator
|
/linux/arch/x86/math-emu/ |
H A D | README | 2 | wm-FPU-emu an FPU emulator for 80386 and 80486SX microprocessors. | 25 wm-FPU-emu is an FPU emulator for Linux. It is derived from wm-emu387 26 which was my 80387 emulator for early versions of djgpp (gcc under 29 the original Linux math emulator by Linus Torvalds. 38 in the detailed behaviour of the emulator and a real 80486. 48 For more information on the emulator and on floating point topics, see 80 The code of the emulator is complicated slightly by the need to 81 account for a limited form of re-entrancy. Normally, the emulator will 83 However, it may happen that when the emulator is accessing the user 84 memory space, swapping may be needed. In this case the emulator may be [all …]
|
/linux/Documentation/arch/arm/nwfpe/ |
H A D | notes.rst | 4 There seems to be a problem with exp(double) and our emulator. I haven't 5 been able to track it down yet. This does not occur with the emulator 8 I also found one oddity in the emulator. I don't think it is serious but 16 f4 had been converted to an extended value in the emulator. 22 emulator sees a multiply of a double and extended, it promotes the double to
|
H A D | nwfpe.rst | 14 I have attempted to make the emulator as portable as possible. One of 22 All the other files contain emulator specific code. This should allow 23 others to port the emulator to NetBSD for instance relatively easily. 37 so far in the emulator. The file TODO contains a information on what 38 remains to be done, and other ideas for the emulator. 42 work correctly when your emulator is installed" are useful for
|
H A D | index.rst | 4 NetWinder's floating point emulator
|
H A D | netwinder-fpe.rst | 6 emulator. 98 extended precision operands. The emulator currently does not check 155 emulator directly. It is possible to run with no floating point module 161 distribution) can be loaded to replace the functionality of the emulator
|
H A D | todo.rst | 48 introduce such a capability into the emulator. The FPCR contains 49 bits describing the rounding mode. The emulator could be altered to
|
/linux/Documentation/devicetree/bindings/goldfish/ |
H A D | battery.txt | 3 Android goldfish battery device generated by android emulator. 7 - compatible : should contain "google,goldfish-battery" to match emulator
|
H A D | audio.txt | 3 Android goldfish audio device generated by android emulator. 7 - compatible : should contain "google,goldfish-audio" to match emulator
|
H A D | pipe.txt | 3 Andorid pipe virtual device generated by android emulator. 7 - compatible : should contain "google,android-pipe" to match emulator
|
H A D | tty.txt | 3 Android goldfish tty device generated by android emulator. 7 - compatible : should contain "google,goldfish-tty" to match emulator
|
H A D | events.txt | 3 Android goldfish events keypad device generated by android emulator. 7 - compatible : should contain "google,goldfish-events-keypad" to match emulator
|
/linux/Documentation/security/tpm/ |
H A D | tpm_vtpm_proxy.rst | 27 is passed to the TPM emulator. Software inside the container can then send 28 TPM commands using the character device and the emulator will receive the 34 whether TPM 1.2 or TPM 2 functionality is supported by the TPM emulator.
|
/linux/arch/mips/generic/ |
H A D | Kconfig | 118 bool "Support Ranchu platform for Android emulator" 120 This enables support for the platform used by Android emulator. 124 Android emulator. Android emulator is based on Qemu, and contains
|
/linux/samples/seccomp/ |
H A D | bpf-direct.c | 62 static void emulator(int nr, siginfo_t *info, void *void_context) in emulator() function 98 act.sa_sigaction = &emulator; in install_emulator()
|
/linux/Documentation/devicetree/bindings/display/ |
H A D | google,goldfish-fb.txt | 3 Android Goldfish framebuffer device used by Android emulator.
|
/linux/Documentation/devicetree/bindings/interrupt-controller/ |
H A D | google,goldfish-pic.txt | 4 emulator.
|
/linux/tools/perf/Documentation/ |
H A D | android.txt | 58 You need to connect to your Android device/emulator using adb. 77 Run perf on your device/emulator to which you previously connected using adb:
|
/linux/drivers/platform/goldfish/ |
H A D | Kconfig | 10 Unless you are building for the Android Goldfish emulator say N here.
|
/linux/drivers/net/slip/ |
H A D | Kconfig | 20 to be able to use it, but there is now a SLIP emulator called SLiRP 54 you plan to use SLiRP, the SLIP emulator (available from
|
/linux/Documentation/arch/arm/ |
H A D | mem_alignment.rst | 43 slow (think about the floating point emulator) and
|
/linux/Documentation/arch/s390/ |
H A D | 3270.rst | 32 another 3270 emulator, started from an xterm window on your PC or 145 3279, or use the 3270 emulator of your choice. You would be 146 running the emulator on your PC or workstation. You would use
|
/linux/Documentation/arch/openrisc/ |
H A D | openrisc_port.rst | 70 QEMU is a processor emulator which we recommend for simulating the OpenRISC
|