Hi I see where you are going but in this case no. The cpu has a fixed time period to get a response on the bus. As you go faster the device simply cant put the correct data on the bus in time. Waiting in software would amount to asking the device repeatedly...but every response is incorrect. What we need here is to slow down the processor so that within one bus read you get a valid answer.
To your other question... Seems like the LCD drivers start to miss data. The processor is quickly writing pixel data and the lcd drivers miss a write, so a column of pixels goes missing. First indicator of exceeding the speed limit. On Sunday, November 15, 2020, John R. Hogerhuis <[email protected]> wrote: > > > On Sun, Nov 15, 2020 at 12:48 PM Stephen Adolph <[email protected]> > wrote: > >> good question. In fact it is hardware. the response time of those >> drivers is pretty slow. seems like the first thing that happens is the >> pixels start to get distorted a bit. >> > > And that's because of the higher clock frequency? > > >> And then if you go faster, the laptop freezes at one specific location >> - in a loop where the LCD driver status is checked. Since the driver >> doesn't respond in time, it just loops there. >> >> > So if the code was modified could it be made to wait long enough for the > driver? > > -- John. >
