On 6/8/23 10:11, Lucas Stach wrote:
Am Mittwoch, dem 07.06.2023 um 15:54 +0200 schrieb Marek Vasut:
On 6/7/23 14:53, Lucas Stach wrote:
Am Freitag, dem 02.06.2023 um 23:34 +0200 schrieb Marek Vasut:
On 6/2/23 21:15, Lucas Stach wrote:
From: David Jander
The documentation is not clear about
Am Mittwoch, dem 07.06.2023 um 15:54 +0200 schrieb Marek Vasut:
> On 6/7/23 14:53, Lucas Stach wrote:
> > Am Freitag, dem 02.06.2023 um 23:34 +0200 schrieb Marek Vasut:
> > > On 6/2/23 21:15, Lucas Stach wrote:
> > > > From: David Jander
> > > >
> > > > The documentation is not clear about how
On 6/7/23 14:53, Lucas Stach wrote:
Am Freitag, dem 02.06.2023 um 23:34 +0200 schrieb Marek Vasut:
On 6/2/23 21:15, Lucas Stach wrote:
From: David Jander
The documentation is not clear about how this delay works.
Empirical tests have shown that with a VSDELAY of 0, the first
scanline is not
Am Freitag, dem 02.06.2023 um 23:34 +0200 schrieb Marek Vasut:
> On 6/2/23 21:15, Lucas Stach wrote:
> > From: David Jander
> >
> > The documentation is not clear about how this delay works.
> > Empirical tests have shown that with a VSDELAY of 0, the first
> > scanline is not properly formatted
On 6/2/23 21:15, Lucas Stach wrote:
From: David Jander
The documentation is not clear about how this delay works.
Empirical tests have shown that with a VSDELAY of 0, the first
scanline is not properly formatted in the output stream when
DSI->DP mode is used. The calculation spreadsheets from
From: David Jander
The documentation is not clear about how this delay works.
Empirical tests have shown that with a VSDELAY of 0, the first
scanline is not properly formatted in the output stream when
DSI->DP mode is used. The calculation spreadsheets from Toshiba
seem to always make this value
