On Fri, 20 May 2005 21:26:59 +0200, Geert Uytterhoeven said: > On Fri, 20 May 2005, Richard B. Johnson wrote: > > I think that I've discovered a bug. I know that what I have written gets > > to the screen buffer because I can read in back! This doesn't make > > any sense. > > Even if it's only in the CPU cache, of course you can read it back (using the > CPU, not DMA ;-). No, the bug is in Richard's assuming that because he can read it back in means that it's in the screen buffer. In fact, it only means he wrote it into some memory location that he can read back in. ;) Now if he added a description that verified that a read *from the screen buffer* (rather than "from where he wrote") shows his changes, *then* he'd have something...
Attachment:
pgpfd6U2oJEo2.pgp
Description: PGP signature
- Follow-Ups:
- Re: Screen regen buffer at 0x00b8000
- From: "Richard B. Johnson" <[email protected]>
- Re: Screen regen buffer at 0x00b8000
- References:
- Screen regen buffer at 0x00b8000
- From: "Richard B. Johnson" <[email protected]>
- Re: Screen regen buffer at 0x00b8000
- From: Jan-Benedict Glaw <[email protected]>
- Re: Screen regen buffer at 0x00b8000
- From: "Richard B. Johnson" <[email protected]>
- Re: Screen regen buffer at 0x00b8000
- From: Geert Uytterhoeven <[email protected]>
- Screen regen buffer at 0x00b8000
- Prev by Date: Re: [patch 1/1] Proposed: Let's not waste precious IRQs...
- Next by Date: RE: [OpenAFS] Re: Openafs 1.3.78 and kernel 2.4.29 oopses , same for 2.4.30 and openafs 1.3.82
- Previous by thread: Re: Screen regen buffer at 0x00b8000
- Next by thread: Re: Screen regen buffer at 0x00b8000
- Index(es):