Re: [Bug 2419] New: Solo crashes on ia64 on startup
Jesse Barnes wrote: On Monday, January 31, 2005 12:00 pm, Stephane Marchesin wrote: Yes, other drivers suffer from that too (at least r128, i810 and mga as far as I can see). However, as I said previously I don't understand them enough to touch them. Oh, I must have missed that message, sorry. No problem, "previously" was quite some time ago... It sure looks like the r128 case is almost exactly the same as the one you fixed in the radeon driver, in fact your patch almost applies but for the small amount of radeon specific context in it. i810 actually looks like it has the memset #if 0'd out, so is probably safe. Ah right, in i810 it's commented out. And mga again looks nearly identical to the radeon case. Why don't we fix them all up at once? Ok, I will attach another patch to the bug. Stephane --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug 2419] New: Solo crashes on ia64 on startup
On Monday, January 31, 2005 12:00 pm, Stephane Marchesin wrote: > Yes, other drivers suffer from that too (at least r128, i810 and mga as > far as I can see). However, as I said previously I don't understand them > enough to touch them. Oh, I must have missed that message, sorry. It sure looks like the r128 case is almost exactly the same as the one you fixed in the radeon driver, in fact your patch almost applies but for the small amount of radeon specific context in it. i810 actually looks like it has the memset #if 0'd out, so is probably safe. And mga again looks nearly identical to the radeon case. Why don't we fix them all up at once? Jesse --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug 2419] New: Solo crashes on ia64 on startup
Jesse Barnes wrote: On Saturday, January 29, 2005 4:38 pm, [EMAIL PROTECTED] wrote: When I use solo on ia64, it sometimes causes an MCA upon startup. That's because a memset is done on the framebuffer memory during init. Please refer to this message from Jesse Barnes to know why this is bad : http://sourceforge.net/mailarchive/forum.php?thread_id=6354420&forum_id=717 7 Here is a patch that fixes this by changing the memset into a for() loop doing memory access one byte at a time : http://icps.u-strasbg.fr/~marchesin/dri/ia64_solo_memset.patch Is it just radeon that suffers from this problem? How about r128 or the other drivers? (I don't have the tree in front of me just now or I'd do a quick audit.) Yes, other drivers suffer from that too (at least r128, i810 and mga as far as I can see). However, as I said previously I don't understand them enough to touch them. Stephane --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
Re: [Bug 2419] New: Solo crashes on ia64 on startup
On Saturday, January 29, 2005 4:38 pm, [EMAIL PROTECTED] wrote: > When I use solo on ia64, it sometimes causes an MCA upon startup. That's > because a memset is done on the framebuffer memory during init. > > Please refer to this message from Jesse Barnes to know why this is bad : > http://sourceforge.net/mailarchive/forum.php?thread_id=6354420&forum_id=717 >7 > > Here is a patch that fixes this by changing the memset into a for() loop > doing memory access one byte at a time : > http://icps.u-strasbg.fr/~marchesin/dri/ia64_solo_memset.patch Is it just radeon that suffers from this problem? How about r128 or the other drivers? (I don't have the tree in front of me just now or I'd do a quick audit.) Thanks, Jesse --- This SF.Net email is sponsored by: IntelliVIEW -- Interactive Reporting Tool for open source databases. Create drag-&-drop reports. Save time by over 75%! Publish reports on the web. Export to DOC, XLS, RTF, etc. Download a FREE copy at http://www.intelliview.com/go/osdn_nl -- ___ Dri-devel mailing list Dri-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dri-devel
