Title: The Device Tree: Plug and play for Embedded Linux
this...
aliases
{&
nbsp;&nbs
p;
Title: The Device Tree: Plug and play for Embedded Linux
If i am understanding correctly this something added to chosen to
bind the console to a specific uart... as in
/dts-v1/; /{
#address-cells = <1>; #size-cells = <1>;
compatible = "xlnx,zynq-zed";
apparently our problem is not new and the existing solution is the
"linux,stdout-path" syntax
so stdout-path = &uartf; should work (... maybe)
jonas just pointed this out to me
On 30/08/2014 11:37, Luis Soltero wrote:
> hm... it still seems that the board integrator should be able to determin
hm... it still seems that the board integrator should be able to determine the
node name for the device. Implementing a
scheme based on base address still hard wires the node name to the port and
does not provide the flexibility of changing
it.Absolutely depending on the load order is quirk
Hi
On Lantiq we derive the port numbering from the base addr that gets
used for early printk. i will implement a similar solution for ralink.
having to rely on the load order seems quirky.
John
On 29/08/2014 23:56, Luis Soltero wrote:
>
> Hello All,
>
> Most mt7620a routers defined in
Hello All,
Most mt7620a routers defined in the target/linux/ramips/dts have exactly one
serial port defined which is used for the
console. The serial port driver links this to node /dev/ttyS0.
However. one (and now 2) devices use the mt7620a serial port lines for use as
a second real serial
