search for: uarts

See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. As before several of the patches are not to be applied because they can be done better using infrastructure from Julien''s "Allow Xen to boot with a raw Device Tree" patch. They are included for completeness. With

See http://www.gossamer-threads.com/lists/xen/devel/297170 for some information on how to get this going. I''ve rebased and addressed the review comments. With this rebase I''ve picked up some patches from Julien which were required to do things properly, so the gic v7 and device blacklisting patches have been changed to use the proper mechanisms. Previously I was able to boot

Since OMAP UART has a few distinct features than common 8250 UART, I re-implemented its driver rather than porting it based on ns16550.c. There are mainly two big differences between the implementations. First, OMAP UART introduces the concept of register access mode, which divides the register map into seperated space. Switching the access mode is then necessary when configuring it. Second, THRE

This is a fairly standard and old machine with 2 COM ports. Recently (last Friday) I decided to update my RELENG_7 system and also to transition from sio to uart. This what I had before the upgrade: kernel: sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0 kernel: sio0: type 16550A kernel: sio0: [FILTER] kernel: sio1: <16550A-compatible COM port> port

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

Hi Julien > On some board, there is no alias to the UART. To avoid modification in > the device tree, dt-uart should also search device by path. > > To distinguish an alias from a path, dt-uart will check the first character. > If it''s a / then it''s path, otherwise it''s an alias. > > Signed-off-by: Julien Grall <julien.grall@xxxxxxxxxx> >

Besides single-port serial cards, also accept multi-port ones and such providing mixed functionality (e.g. also having a parallel port). Reading PCI_INTERRUPT_PIN before ACPI gets enabled generally produces an incorrect IRQ (below 16, whereas after enabling ACPI it frequently would end up at a higher one), so this is useful (almost) only when a system already boots in ACPI mode. Signed-off-by:

...> > I would like SYSLINUX to get input from UART and act accordingly. > For example, I want to choose what rootfs to load according to the sequence received from UART. > So I'd like to know if SYSLINUX a the infrastructure for doing this Yes, Syslinux supports serial ports a.k.a. UARTS. Since the very begining of the project. > and if it maybe some reference for it. http://www.syslinux.org/wiki/index.php/Doc/syslinux search there ( `CTRL-F` ) for keyword 'SERIAL' Feel free to convert your exprience into feedback to us, the Syslinux project. Groeten Geert Stappe...

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 +-

We have upgraded a box from 6.2 to 6.3-RELEASE. Afterwards the box does not recognize its ST Lab I-160 serial card with Netmos 9845 Chipset. It worked flawlessly on 6.2 with puc(4) driver. >From dmesg: pci1: <simple comms, UART> at device 8.0 (no driver attached) ~# pciconf -l -v | grep -B 4 UART none2@pci1:8:0: class=0x070002 card=0x00041000 chip=0x98459710 rev=0x01 hdr=0x00

The current early-printk support for ARM is rather hard-coded, making it hard to add machines or tweak settings. This series slightly moves some code to gather UART settings in xen/arch/arm/Rules.mk instead of the actual .c files. Also it allows two different machines with different settings to share the same driver, which the last patch exploits to add support the Calxeda Midway hardware. This

...tranger still, the app works with the uart driver when uart attaches to the built in com port on the isa bus. However, its uart devices when its connected to a PUC backed serial card where the problems happen. e.g. when the uart driver attaches as so, puc0: <Oxford Semiconductor OX16PCI954 UARTs> port 0xe520-0xe53f,0xe540-0xe55f mem 0xa0005000-0xa0005fff,0xa0006000-0xa0006fff irq 15 at device 17.0 on pci0 puc0: [FILTER] uart0: <16950 or compatible> on puc0 uart0: [FILTER] uart1: <16950 or compatible> on puc0 uart1: [FILTER] uart2: <16950 or compatible> on puc0 uart2:...

I have installed two 4-port serial cards (http://www.startech.com/ Product/ItemDetail.aspx?productid=PCI4S550&c=US) on a CentOS 4.4 system. The hardware appears to be recognized correctly, as kudzu added 2 entries to /etc/sysconfig/hwconf and lscpi shows both cards (output of lspci -vv for both cards included at the end of this email): # lspci 00:00.0 Host bridge: Intel Corporation

...> > I would like SYSLINUX to get input from UART and act accordingly. > For example, I want to choose what rootfs to load according to the sequence received from UART. > So I'd like to know if SYSLINUX a the infrastructure for doing this Yes, Syslinux supports serial ports a.k.a. UARTS. Since the very begining of the project. > and if it maybe some reference for it. http://www.syslinux.org/wiki/index.php/Doc/syslinux search there ( `CTRL-F` ) for keyword 'SERIAL' Feel free to convert your experience into feedback to us, the Syslinux project. Groeten Geert Stapp...

Tal Lubko via Syslinux <syslinux at zytor.com> writes: > What I'm planning to do is to write COM32 image that will open UART > channel and wait for input (until timeout arrives). In case input > arrives, it will parse and validate it and act accordingly. > My solution doesn't involve user interaction. This is exactly what the Syslinux command interpreter does, if

On Sat, Aug 1, 2015 at 4:56 PM, Tal Lubko via Syslinux <syslinux at zytor.com> wrote: > Hi Geert > > > Thanks for your help. > What I'm planning to do is to write COM32 image that will open UART channel and wait for input (until timeout arrives). > In case input arrives, it will parse and validate it and act accordingly. > My solution doesn't involve user

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 +++

...port. Also, now that > FIFOs are in place, I believe performance could be improved > significantly by putting some code into the hypervisor so that reads & > writes from the FIFOs don''t have to exit into qemu-dm at all. I''m also > reading up on the specs for newer uarts with deeper FIFOs. I notice with this patch that my HVM domain, which specifies serial=pty in the config file, no longer boots without me attaching to the console via xm. Previously it would boot regardless of whether I was attached to the console. Is this change in behavior intentional? Note...

Hi, I'm having issues connecting Garmin GPS 18 to COM1 on 9.1, I get nothing but silence. Identical setup works absolutely fine with Linux. I've got PPS wire connected to DCD, but that seems to make no difference on Linux, so I presume it shouldn't affect fbsd either. On Linux, I get: $ uname -a Linux ubuntu 3.8.0-19-generic #29-Ubuntu SMP Wed Apr 17 18:16:28 UTC 2013 x86_64 x86_64

These series patch enable Allwinner A31(code name sun6i) support in assemble. with these patches, the cpu 0 of sun6i SOC could successful boot into the c environment. Bamvor Jian Zhang (4): xen/arm: introduce Cortex-A7 support xen/arm: introduce Allwinner sun6i SOC basic support xen/arm: enable early printk for sun6i xen/arm: enable switch to hyper mode for sun6i xen/arch/arm/Rules.mk