Hi Simon,
On Thu, Feb 4, 2021 at 8:33 AM Simon Glass wrote:
>
> On Wed, 3 Feb 2021 at 17:20, Bin Meng wrote:
> >
> > Hi Simon,
> >
> > On Thu, Feb 4, 2021 at 5:42 AM Simon Glass wrote:
> > >
> > > Hi Bin,
> > >
> > > On Wed, 3 Feb 2021 at 07:42, Bin Meng wrote:
> > > >
> > > > A working device
Hi Simon,
On Thu, Feb 4, 2021 at 8:33 AM Simon Glass wrote:
>
> On Wed, 3 Feb 2021 at 17:20, Bin Meng wrote:
> >
> > Hi Simon,
> >
> > On Thu, Feb 4, 2021 at 5:42 AM Simon Glass wrote:
> > >
> > > Hi Bin,
> > >
> > > On Wed, 3 Feb 2021 at 07:42, Bin Meng wrote:
> > > >
> > > > A working device
On Wed, 3 Feb 2021 at 17:20, Bin Meng wrote:
>
> Hi Simon,
>
> On Thu, Feb 4, 2021 at 5:42 AM Simon Glass wrote:
> >
> > Hi Bin,
> >
> > On Wed, 3 Feb 2021 at 07:42, Bin Meng wrote:
> > >
> > > A working device tree node of ns16550 should never be populated
> > > with value zero for the propert
Hi Simon,
On Thu, Feb 4, 2021 at 5:42 AM Simon Glass wrote:
>
> Hi Bin,
>
> On Wed, 3 Feb 2021 at 07:42, Bin Meng wrote:
> >
> > A working device tree node of ns16550 should never be populated
> > with value zero for the property. Unfortunately
> > this is the case for the QEMU ppce500 target.
Hi Bin,
On Wed, 3 Feb 2021 at 07:42, Bin Meng wrote:
>
> A working device tree node of ns16550 should never be populated
> with value zero for the property. Unfortunately
> this is the case for the QEMU ppce500 target.
>
> Let's try to assign plat->clock to CONFIG_SYS_NS16550_CLK as the
> last r
A working device tree node of ns16550 should never be populated
with value zero for the property. Unfortunately
this is the case for the QEMU ppce500 target.
Let's try to assign plat->clock to CONFIG_SYS_NS16550_CLK as the
last resort to handle such case.
This commit should be reverted when:
-
6 matches
Mail list logo
