On Thu, 5 May 2022, Maciej W. Rozycki wrote:
> > I see that Linux patch was not not merged yet and there are already
> > comments that this issue is probably board or arch specific and maybe
> > should be in arch/riscv linux dir:
> >
On Sun, 1 May 2022, Pali Rohár wrote:
> > By now I have become somewhat tired arguing and explaining matters over
> > and over again as things have been moving as slow as molasses in this
> > area, but one point I want to raise here is while it is indeed the ASM2824
> > device that seems
On Friday 08 April 2022 00:18:48 Maciej W. Rozycki wrote:
> On Thu, 7 Apr 2022, Stefan Roese wrote:
>
> > > Hello! What do you think about this change? I think it is good
> > > compromise between enable this workaround for all builds on all boards
> > > and enable it only based on device id. Or
On Thu, 7 Apr 2022, Stefan Roese wrote:
> > Hello! What do you think about this change? I think it is good
> > compromise between enable this workaround for all builds on all boards
> > and enable it only based on device id. Or would it be better to restrict
> > this workaround just for ASM2824
On 4/6/22 17:09, Pali Rohár wrote:
PCIe ASMedia ASM2824 workaround code unconditionally increase size of all
SPL binaries with PCIe support, even those which do not use ASMedia ASM2824
PCIe switch.
Moreover this workaround is enabled for all existing hardware and also all
future PCIe hardware,
PCIe ASMedia ASM2824 workaround code unconditionally increase size of all
SPL binaries with PCIe support, even those which do not use ASMedia ASM2824
PCIe switch.
Moreover this workaround is enabled for all existing hardware and also all
future PCIe hardware, which opens a hole that other PCIe
6 matches
Mail list logo
