similar to: [PATCH RFC 2/9] console: prepare for non-COMn port support

Dear R-experts, I am struggling with the following problem, and I am looking for advice from more experienced R-users: I have a data frame with 2 identifying variables (comn and mi), and an output variable (x). comn is a variable for a company and mi is a variable for a month. comn<-c("abc", "abc", "abc", "abc", "abc", "abc",

Type of tx_ready callback got changed to int to faciliate error condition, but the ARM serial drivers were not modified thus breaking the compilation. Reported-by: Julien Grall <julien.grall@linaro.org> Signed-off-by: Tomasz Wroblewski <tomasz.wroblewski@citrix.com> --- xen/drivers/char/exynos4210-uart.c | 2 +- xen/drivers/char/omap-uart.c | 2 +-

James Liggett wrote: >Of course, running palm desktop is a different story (there is a crash >in WinMM that stops it from running) but I'm pretty sure we can get >hotsync to work if we can figure out how to set up the serial ports. > > You just need to symlink your serial device (maybe /dev/ttyS0) to ~/.wine/dosdevices/COMn (where n is > 0) and then you can access it

The commit 874f76a "PL011: fix reverse logic for interrupt mask register" introduced regression on the Versatile Express. The board didn''t receive correctly input. The timeout interrupt may be asserted when the FIFO is not empty, and no futher data is received over a 32-bit period. Signed-off-by: Julien Grall <julien.grall@linaro.org> --- xen/drivers/char/pl011.c | 2

FYI, I see the following build error with this patch... MRJ ---- new warnings/errors for xen ---- keyhandler.c: In function `__dump_execstate'': keyhandler.c:96: warning: asm operand 1 probably doesn''t match constraints gmake[5]: *** [keyhandler.o] Error 1 gmake[4]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/common/built_in.o] Error 2 gmake[3]: *** [/tank/ws/xvm-3.4.3/xen.hg/xen/xen]

Prior to c/s 23811:f1349a968a5a LSR_THRE was checked only once, while there it got promoted into the surrounding loop''s condition. Since that bit may not clear for an extended period of time (i.e. when no new output is generated), it must not be used in this way indefinitely. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/char/ns16550.c +++

On x86 ioremap() is not suitable here, set_fixmap() must be used instead. Also replace some literal numbers by their proper symbolic constants, making the code easier to understand. Signed-off-by: Jan Beulich <jbeulich@suse.com> --- a/xen/drivers/char/ns16550.c +++ b/xen/drivers/char/ns16550.c @@ -20,6 +20,9 @@ #include <xen/pci.h> #include <xen/pci_regs.h> #include

Ben- I like the idea but I don''t understand how this patch can work: 1) You never put a name into `serial_devices[]'' for the summa port. The loop in `main'' that initializes the serial devices only calls `qemu_chr_open'' if there''s a string name in `serial_devices''. How did you get this to work? 2) Minor point, I don''t see the need

On Sun, Oct 9, 2016 at 7:25 AM, Oliver Mangold via Syslinux <syslinux at zytor.com> wrote: > Hi, > > I would like to point out an issue with the enumeration of ISA serial > devices in Syslinux. If I interpret the snippet below correctly, Syslinux > looks up the device order with the BIOS, while Linux uses the fixed order > 3F8,2F8,3E8,2E8. > > Note that this

Hi, I would like to point out an issue with the enumeration of ISA serial devices in Syslinux. If I interpret the snippet below correctly, Syslinux looks up the device order with the BIOS, while Linux uses the fixed order 3F8,2F8,3E8,2E8. Note that this inconsistency is a real problem, as some motherboards (like e.g. a Supermicro X10DRi with default BIOS settings) have a different order

Hi, This is the fifth version of this patch series. With the Versatile Express TC2, it''s possible to boot only with A7 or A15. If the user choose to boot with only A7, the CPU ID will start at 0x100. As Xen relies on it to set the logical ID and the GIC, it won''t be possible to use Xen with this use case. This patch series is divided in 3 parts: - Patch 1: prepare Xen

This series consists of improvements to Xen''s ability to print traces of its own stack, and specifically for the stack overflow case to be able to use frame pointers in a debug build. I have dev tested the series in debug and non-debug cases, with and without memory guards, and I believe that all the stack traces look correct (given the available information Xen has), and that the

dear experts, I have a clean kvm installation on ubuntu 12.04 x64 , when trying to create my first guest I get the following error: Unable to complete install: 'internal error cannot load AppArmor profile 'libvirt-ac760227-6849-b81e-15f6-a7eae418225f'' Traceback (most recent call last): File "/usr/share/virt-manager/virtManager/asyncjob.py", line 45, in