On 2/26/22 14:30, Mark Kettenis wrote:
Date: Fri, 25 Feb 2022 14:50:59 +0100
From: Marek Vasut
On 2/25/22 12:37, Mark Kettenis wrote:
From: Fabio Estevam
Date: Fri, 25 Feb 2022 08:12:58 -0300
Hi Tim,
On Thu, Feb 24, 2022 at 6:46 PM Tim Harvey wrote:
Fabio,
No, that commit is 'not' in v2
> Date: Fri, 25 Feb 2022 14:50:59 +0100
> From: Marek Vasut
>
> On 2/25/22 12:37, Mark Kettenis wrote:
> >> From: Fabio Estevam
> >> Date: Fri, 25 Feb 2022 08:12:58 -0300
> >>
> >> Hi Tim,
> >>
> >> On Thu, Feb 24, 2022 at 6:46 PM Tim Harvey wrote:
> >>
> >>> Fabio,
> >>>
> >>> No, that commit
On 2/25/22 12:37, Mark Kettenis wrote:
From: Fabio Estevam
Date: Fri, 25 Feb 2022 08:12:58 -0300
Hi Tim,
On Thu, Feb 24, 2022 at 6:46 PM Tim Harvey wrote:
Fabio,
No, that commit is 'not' in v2021.07. Please test with master and you
should see that go away.
Yes, you are right.
Regardles
> From: Fabio Estevam
> Date: Fri, 25 Feb 2022 08:12:58 -0300
>
> Hi Tim,
>
> On Thu, Feb 24, 2022 at 6:46 PM Tim Harvey wrote:
>
> > Fabio,
> >
> > No, that commit is 'not' in v2021.07. Please test with master and you
> > should see that go away.
>
> Yes, you are right.
>
> > Regardless, Ma
Hi Tim,
On Thu, Feb 24, 2022 at 6:46 PM Tim Harvey wrote:
> Fabio,
>
> No, that commit is 'not' in v2021.07. Please test with master and you
> should see that go away.
Yes, you are right.
> Regardless, Marek's suggestion is the right fix if you can manage
> that... we really don't want to limi
On Thu, Feb 24, 2022 at 12:32 PM Fabio Estevam wrote:
>
> Hi Tim,
>
> On Thu, Feb 24, 2022 at 5:20 PM Tim Harvey wrote:
>
> > Fabio,
> >
> > As Marek points out the individual peripheral drivers have not been
> > updated properly but this should be worked around with commit
> > e27bddff4b97 ("imx
Hi Tim,
On Thu, Feb 24, 2022 at 5:20 PM Tim Harvey wrote:
> Fabio,
>
> As Marek points out the individual peripheral drivers have not been
> updated properly but this should be worked around with commit
> e27bddff4b97 ("imx8m: Restrict usable memory to space below 4G
> boundary").
I am using 20
On 2/24/22 21:19, Tim Harvey wrote:
On Thu, Feb 24, 2022 at 12:03 PM Marek Vasut wrote:
On 2/24/22 20:50, Fabio Estevam wrote:
Hi Tim,
Sorry for resurrecting such an old thread.
On Fri, Sep 25, 2020 at 11:52 AM Tim Harvey wrote:
Greetings,
I'm working with an IMX8MM board that has 4GiB
On Thu, Feb 24, 2022 at 12:03 PM Marek Vasut wrote:
>
> On 2/24/22 20:50, Fabio Estevam wrote:
> > Hi Tim,
> >
> > Sorry for resurrecting such an old thread.
> >
> > On Fri, Sep 25, 2020 at 11:52 AM Tim Harvey wrote:
> >>
> >> Greetings,
> >>
> >> I'm working with an IMX8MM board that has 4GiB of
On 2/24/22 20:50, Fabio Estevam wrote:
Hi Tim,
Sorry for resurrecting such an old thread.
On Fri, Sep 25, 2020 at 11:52 AM Tim Harvey wrote:
Greetings,
I'm working with an IMX8MM board that has 4GiB of DRAM. I've found
that in this configuration the MMC driver and FEC network driver
appear
Hi Tim,
Sorry for resurrecting such an old thread.
On Fri, Sep 25, 2020 at 11:52 AM Tim Harvey wrote:
>
> Greetings,
>
> I'm working with an IMX8MM board that has 4GiB of DRAM. I've found
> that in this configuration the MMC driver and FEC network driver
> appear to have some issues with crossin
On Thu, Oct 1, 2020 at 1:50 PM Marek Vasut wrote:
> In Linux, R-Car3 uses IOMMU, so there is no performance hit on that
> specific hardware. On iMX8M, you would likely need to set some bit which
> indicates the hardware supports only 32bit DMA, so the DMA buffers would
> be allocated below the 32
> Subject: Re: IMX8MM 4GiB boundary issue
>
> On Sat, Sep 26, 2020 at 7:35 PM Peng Fan wrote:
> >
> > > Subject: Re: IMX8MM 4GiB boundary issue
> > >
> > > On 9/27/20 2:56 AM, Peng Fan wrote:
> > >
> > > [...]
> > >
On 10/1/20 6:33 PM, Tim Harvey wrote:
> On Sun, Sep 27, 2020 at 7:47 AM Marek Vasut wrote:
>>
>> On 9/27/20 4:35 AM, Peng Fan wrote:
>>>> Subject: Re: IMX8MM 4GiB boundary issue
>>>>
>>>> On 9/27/20 2:56 AM, Peng Fan wrote:
>>>>
>
On Sun, Sep 27, 2020 at 7:47 AM Marek Vasut wrote:
>
> On 9/27/20 4:35 AM, Peng Fan wrote:
> >> Subject: Re: IMX8MM 4GiB boundary issue
> >>
> >> On 9/27/20 2:56 AM, Peng Fan wrote:
> >>
> >> [...]
> >>
> >>>>> I c
On Sat, Sep 26, 2020 at 7:35 PM Peng Fan wrote:
>
> > Subject: Re: IMX8MM 4GiB boundary issue
> >
> > On 9/27/20 2:56 AM, Peng Fan wrote:
> >
> > [...]
> >
> > >>> I can imagine that either the FEC/SDHCI is limited to 32bit
> > >>
On 9/27/20 4:35 AM, Peng Fan wrote:
>> Subject: Re: IMX8MM 4GiB boundary issue
>>
>> On 9/27/20 2:56 AM, Peng Fan wrote:
>>
>> [...]
>>
>>>>> I can imagine that either the FEC/SDHCI is limited to 32bit
>>>>> addressing in hardwa
> Subject: Re: IMX8MM 4GiB boundary issue
>
> On 9/27/20 2:56 AM, Peng Fan wrote:
>
> [...]
>
> >>> I can imagine that either the FEC/SDHCI is limited to 32bit
> >>> addressing in hardware (the DMA can only operate on 32bit range due
> >>>
On 9/27/20 2:56 AM, Peng Fan wrote:
[...]
>>> I can imagine that either the FEC/SDHCI is limited to 32bit addressing
>>> in hardware (the DMA can only operate on 32bit range due to it coming
>>> from 32bit systems), OR, the drivers need to be patched to support the
>>> 64bit addresses properly on
> Subject: Re: IMX8MM 4GiB boundary issue
>
> On Fri, Sep 25, 2020 at 8:05 AM Marek Vasut wrote:
> >
> > On 9/25/20 4:52 PM, Tim Harvey wrote:
> > > Greetings,
> > >
> > > I'm working with an IMX8MM board that has 4GiB of DRAM. I've fou
On 9/25/20 5:12 PM, Tim Harvey wrote:
> On Fri, Sep 25, 2020 at 8:05 AM Marek Vasut wrote:
>>
>> On 9/25/20 4:52 PM, Tim Harvey wrote:
>>> Greetings,
>>>
>>> I'm working with an IMX8MM board that has 4GiB of DRAM. I've found
>>> that in this configuration the MMC driver and FEC network driver
>>>
On Fri, Sep 25, 2020 at 8:05 AM Marek Vasut wrote:
>
> On 9/25/20 4:52 PM, Tim Harvey wrote:
> > Greetings,
> >
> > I'm working with an IMX8MM board that has 4GiB of DRAM. I've found
> > that in this configuration the MMC driver and FEC network driver
> > appear to have some issues with crossing t
On 9/25/20 4:52 PM, Tim Harvey wrote:
> Greetings,
>
> I'm working with an IMX8MM board that has 4GiB of DRAM. I've found
> that in this configuration the MMC driver and FEC network driver
> appear to have some issues with crossing the 4GiB address space. If I
> tell U-Boot I have 3GiB everything
Greetings,
I'm working with an IMX8MM board that has 4GiB of DRAM. I've found
that in this configuration the MMC driver and FEC network driver
appear to have some issues with crossing the 4GiB address space. If I
tell U-Boot I have 3GiB everything is ok, but when I set it to 4GiB I
see the followi
24 matches
Mail list logo
