C�pia Juliusz Chroboczek <[EMAIL PROTECTED]>: > 00000 - 003FF: mapped shared from /dev/mem; > 01000 - 01FFF: mapped private from /dev/zero; > A0000 - FFFFF: mapped shared from /dev/mem.
> I am therefore planning to change Xvesa to have a memory map with no > holes, and would be grateful for any advice. It is rather clear to me > that I should map 01000 through 9FFFF private from /dev/zero. On the > other hand, it is not clear to me whether 00400 through 00FFF should > be mapped private or shared, and where from. > > Of course, I would be curious to learn why this machine insists on > doing a memory scan upon int 10h; conspiracy theories welcome. Not sure if it will help, but I remember a similar problem with a notebook using the vesa driver, where I proposed a patch to map private a larger chunk of memory, i.e. make it do almost the same mappings as lrmi. I don't remember clearly, but I think it was a change to xf86int10.h. Maybe Egbert Eich has some comment, as he did several changes to the code, and made it work in a multi-head friendly way. Actually, I wrote the vesa driver just an exercise for a few days, to have a better understanding of the DESIGN document. I just used the already existing int10 code at the time, so I am not an expert :-) Anyway, I believe Keith's comment on adding a signal handler of some type should be the better solution. The bios code is probably trying to find some signature in the memory, maybe a DOS TSR to talk with. > Thanks for your help, > > Juliusz > > > _______________________________________________ > Xpert mailing list > [EMAIL PROTECTED] > http://XFree86.Org/mailman/listinfo/xpert Paulo _______________________________________________ Xpert mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/xpert
