Re: [linux-yocto] [kernel v5.2/standard/xlnx-soc][PATCH 0/1][V2]patches for xilinx

2019-11-03 Thread Quanyang Wang

Hi Bruce,

On 10/25/19 1:20 AM, Bruce Ashfield wrote:

On Thu, Oct 24, 2019 at 6:26 AM  wrote:

From: Quanyang Wang 

Hi all,

V1 ---> V2:

1. delete the patch "arch: arm64: dts: add overlay dts file" because it is 
improper
to add into kernel source.

2. modify the patch " i2c: cadence: do not clear bus_hold_flag in mrecv" by 
adding
a I2C_M_NOSTART flag check according to Shubhrajyoti's suggestion. And test it 
at
zcu102 board (read bus 0x8 device 0x65 (ucd10120) register 0xd6)as below:
Before applying this patch:
root@xilinx-zynq:~# i2cget -f -y 0x8 0x65 0xd6
0xff
After applying this patch:
root@xilinx-zynq:~# i2cget -f -y 0x8 0x65 0xd6
0x05


I'll wait for comments on this patch.


This patch has been reviewed. Would you please help merge it to 
v5.2/standard/xlnx-soc?


Thanks,

Quanyang



I just wanted to follow up to say that I *think* that I have all of
the reviewed and ack'd patches merged now .. but gmail is doing some
very strange things and hiding replies to some of the threads.

So if you see something that is reviewed/acked and is missing, send it
again with a clear "v2" (or whatever version it is) in the subject.

Bruce


Thanks,
Quanyang

Quanyang Wang (1):
   i2c: cadence: keep bus_hold_flag unless I2C_M_NOSTART is set

  drivers/i2c/busses/i2c-cadence.c | 8 +---
  1 file changed, 5 insertions(+), 3 deletions(-)

--
2.17.1




--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto


Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

2019-11-03 Thread Adrian Bunk
On Sun, Nov 03, 2019 at 05:56:45PM +, Andrei Gherzan wrote:
> On 3 November 2019 13:18:53 GMT, Khem Raj  wrote:
> >On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan 
> >wrote:
> >> I was thinking about this. The erratum seems to show that this
> >applies
> >> to all revisions of a53. So it sounds like we should add it in
> >> `tune-cortexa53.inc`.
> >>
> >
> >Up to r0b4 only so maybe not all a53 implementations are impacted
> >
> 
> As far as I know that is the latest revision. Do you mean that newer revision 
> might come up with this fixed? 

It is fixed in some r0p4 implementations, indicated in REVIDR[8].

cu
Adrian

-- 

   "Is there not promise of rain?" Ling Tan asked suddenly out
of the darkness. There had been need of rain for many days.
   "Only a promise," Lao Er said.
   Pearl S. Buck - Dragon Seed

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

2019-11-03 Thread Khem Raj
On Sun, Nov 3, 2019 at 9:56 AM Andrei Gherzan  wrote:

>
>
> On 3 November 2019 13:18:53 GMT, Khem Raj  wrote:
> >On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan 
> >wrote:
> >
> >> On 01/11/2019 17:18, Khem Raj wrote:
> >> > On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan 
> >wrote:
> >> >>
> >> >> Hi Steve,
> >> >>
> >> >> On 01/11/2019 05:32, Steve Pavao wrote:
> >> >>> poky linux build fails when ARM erratum mfix linker switch is
> >specified
> >> >>> in local.conf:
> >> >>>
> >> >>> TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419”
> >> >>>
> >> >>> causes build failure.
> >> >>>
> >> >>> Please advise how to use this switch successfully.  I am synced
> >current
> >> >>> in master branch in all layers as of today.  The switch causes
> >libtool
> >> >>> link to fail due to missing libbz2.so.  If I don’t specify the
> >switch,
> >> >>> the build completes without errors.
> >> >>>
> >> >>> It is important to be able to build poky linux with this switch
> >to
> >> avoid
> >> >>> certain crash conditions as described in the ARM errata document.
> >> >>
> >> >> I haven't tried this erratum fix. It is indeed implemented at the
> >> >> linker's lever. It's curious though to see the bz2 dependency. Can
> >you
> >> >> share the specific error? I assume you are doing this on RPi3.
> >> >>
> >> >
> >> > this will impact rpi3 in 64bit mode, don't think 32bit needs this.
> >I
> >> > think its best to
> >> > add this option in raspberrypi3-64.conf perhaps via TUNE_CCARGS
> >>
> >> I was thinking about this. The erratum seems to show that this
> >applies
> >> to all revisions of a53. So it sounds like we should add it in
> >> `tune-cortexa53.inc`.
> >>
> >
> >Up to r0b4 only so maybe not all a53 implementations are impacted
> >
>
> As far as I know that is the latest revision. Do you mean that newer
> revision might come up with this fixed?
>

Rpi3 is one of many cortex a53 implementations

>
> --
> Andrei Gherzan
> gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

2019-11-03 Thread Andrei Gherzan


On 3 November 2019 13:18:53 GMT, Khem Raj  wrote:
>On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan 
>wrote:
>
>> On 01/11/2019 17:18, Khem Raj wrote:
>> > On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan 
>wrote:
>> >>
>> >> Hi Steve,
>> >>
>> >> On 01/11/2019 05:32, Steve Pavao wrote:
>> >>> poky linux build fails when ARM erratum mfix linker switch is
>specified
>> >>> in local.conf:
>> >>>
>> >>> TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419”
>> >>>
>> >>> causes build failure.
>> >>>
>> >>> Please advise how to use this switch successfully.  I am synced
>current
>> >>> in master branch in all layers as of today.  The switch causes
>libtool
>> >>> link to fail due to missing libbz2.so.  If I don’t specify the
>switch,
>> >>> the build completes without errors.
>> >>>
>> >>> It is important to be able to build poky linux with this switch
>to
>> avoid
>> >>> certain crash conditions as described in the ARM errata document.
>> >>
>> >> I haven't tried this erratum fix. It is indeed implemented at the
>> >> linker's lever. It's curious though to see the bz2 dependency. Can
>you
>> >> share the specific error? I assume you are doing this on RPi3.
>> >>
>> >
>> > this will impact rpi3 in 64bit mode, don't think 32bit needs this.
>I
>> > think its best to
>> > add this option in raspberrypi3-64.conf perhaps via TUNE_CCARGS
>>
>> I was thinking about this. The erratum seems to show that this
>applies
>> to all revisions of a53. So it sounds like we should add it in
>> `tune-cortexa53.inc`.
>>
>
>Up to r0b4 only so maybe not all a53 implementations are impacted
>

As far as I know that is the latest revision. Do you mean that newer revision 
might come up with this fixed? 

--
Andrei Gherzan
gpg: rsa4096/D4D94F67AD0E9640 | t: @agherzan
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

2019-11-03 Thread Khem Raj
On Sun, Nov 3, 2019 at 2:46 AM Andrei Gherzan  wrote:

> On 01/11/2019 17:18, Khem Raj wrote:
> > On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan  wrote:
> >>
> >> Hi Steve,
> >>
> >> On 01/11/2019 05:32, Steve Pavao wrote:
> >>> poky linux build fails when ARM erratum mfix linker switch is specified
> >>> in local.conf:
> >>>
> >>> TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419”
> >>>
> >>> causes build failure.
> >>>
> >>> Please advise how to use this switch successfully.  I am synced current
> >>> in master branch in all layers as of today.  The switch causes libtool
> >>> link to fail due to missing libbz2.so.  If I don’t specify the switch,
> >>> the build completes without errors.
> >>>
> >>> It is important to be able to build poky linux with this switch to
> avoid
> >>> certain crash conditions as described in the ARM errata document.
> >>
> >> I haven't tried this erratum fix. It is indeed implemented at the
> >> linker's lever. It's curious though to see the bz2 dependency. Can you
> >> share the specific error? I assume you are doing this on RPi3.
> >>
> >
> > this will impact rpi3 in 64bit mode, don't think 32bit needs this. I
> > think its best to
> > add this option in raspberrypi3-64.conf perhaps via TUNE_CCARGS
>
> I was thinking about this. The erratum seems to show that this applies
> to all revisions of a53. So it sounds like we should add it in
> `tune-cortexa53.inc`.
>

Up to r0b4 only so maybe not all a53 implementations are impacted

>
> --
> Andrei Gherzan
>
-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-raspberrypi] poky linux build fails if ARM erratum mfix linker switch is specified

2019-11-03 Thread Andrei Gherzan

On 01/11/2019 17:18, Khem Raj wrote:

On Fri, Nov 1, 2019 at 1:28 AM Andrei Gherzan  wrote:


Hi Steve,

On 01/11/2019 05:32, Steve Pavao wrote:

poky linux build fails when ARM erratum mfix linker switch is specified
in local.conf:

TARGET_LD_ARCH_append += " -mfix-cortex-a53-843419”

causes build failure.

Please advise how to use this switch successfully.  I am synced current
in master branch in all layers as of today.  The switch causes libtool
link to fail due to missing libbz2.so.  If I don’t specify the switch,
the build completes without errors.

It is important to be able to build poky linux with this switch to avoid
certain crash conditions as described in the ARM errata document.


I haven't tried this erratum fix. It is indeed implemented at the
linker's lever. It's curious though to see the bz2 dependency. Can you
share the specific error? I assume you are doing this on RPi3.



this will impact rpi3 in 64bit mode, don't think 32bit needs this. I
think its best to
add this option in raspberrypi3-64.conf perhaps via TUNE_CCARGS


I was thinking about this. The erratum seems to show that this applies 
to all revisions of a53. So it sounds like we should add it in 
`tune-cortexa53.inc`.


--
Andrei Gherzan
--
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto


Re: [yocto] [meta-qt5] How to contribute patches for qtwebengine in meta-qt5?

2019-11-03 Thread Tanu Kaskinen
On Fri, 2019-11-01 at 13:24 +0100, Martin Jansa wrote:
> This patch is already included in 5.13.2 upgrade (ready in zeus-next
> and master-next branches), so you don't need to do anything.

Okay, that's great!

> Otherwise like Khem says, submit the change for meta-qt5 repository
> like any other layer.
> 
> The meta-qt5/qt* repositories are used to maintain the patches, but
> usually only me is updating them to keep in sync with meta-qt5 and
> then syncing from them to meta-qt5 with git format-patch --no-
> numbered --no-signature when doing bigger rebase like when upgrading
> to newer Qt version.

Thanks for the information!

-- Tanu


> On Fri, Nov 1, 2019 at 11:02 AM Tanu Kaskinen  wrote:
> > Hi all!
> > 
> > The meta-qt5 readme says that contributions should be made by forking
> > the meta-qt5 repository on GitHub, but when I look at the qtwebengine
> > recipe, it looks like patches are pulled from
> > https://github.com/meta-qt5/qtwebengine-chromium, and that repository
> > looks like the patches are kept in a particular order so adding a patch
> > at the top is perhaps not what I should do.
> > 
> > It's not clear to me how I should submit a patch in this case. The
> > patch in question would be a simple backport of this upstream commit:
> > https://codereview.qt-project.org/gitweb?p=qt/qtwebengine-chromium.git;a=commitdiff;h=b84e8682b312fb16b16ffb9591415067ceae69f8
> > 
> > It's needed for not breaking qtwebengine when upgrading PulseAudio to
> > 13.0.
> > 
> > -- 
> > Tanu
> > 
> > https://www.patreon.com/tanuk
> > https://liberapay.com/tanuk

-- 
___
yocto mailing list
yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/yocto