On Mon, Dec 8, 2014 at 2:02 PM, Julien Grall wrote:
>
> Hi Oleksandr,
>
> Please avoid top-post.
>
> On 08/12/14 06:34, Oleksandr Dmytryshyn wrote:
> > In our case We've added an additional fake node to the device tree with
> > UART MMIO range for Xen and Xen mapped this MMIO range
> > for the Ker
Hi Oleksandr,
Please avoid top-post.
On 08/12/14 06:34, Oleksandr Dmytryshyn wrote:
> In our case We've added an additional fake node to the device tree with
> UART MMIO range for Xen and Xen mapped this MMIO range
> for the Kernel 3.8. By default UART has wrong configuration in OMAP.
Ok. So it
In our case We've added an additional fake node to the device tree with
UART MMIO range for Xen and Xen mapped this MMIO range
for the Kernel 3.8. By default UART has wrong configuration in OMAP.
Oleksandr Dmytryshyn | Product Engineering and Development
GlobalLogic
M +38.067.382.2525
www.globallo
Hi Oleksandr,
On 05/12/14 13:46, Oleksandr Dmytryshyn wrote:
> UART is not able to receive bytes when idle mode is not
> configured properly. When we use Xen with old Linux
> Kernel (for example 3.8) this kernel configures UART
> idle mode even if the UART node in device tree is absent.
I don't u
UART is not able to receive bytes when idle mode is not
configured properly. When we use Xen with old Linux
Kernel (for example 3.8) this kernel configures UART
idle mode even if the UART node in device tree is absent.
So UART works normally in this case. But new Linux
Kernel (3.12 and upper) doesn
