On 6/10/05, Adam Jackson <[EMAIL PROTECTED]> wrote:
> > My solution to this is to make radeon DRM depend on radeonfb. radeonfb
> > properly attaches to the device and marks everything in use. I chose
> > this method because Xegl wants radeonfb loaded and this scheme has
> > minimal code impact.
> 
> This seems like an odd solution.  Why wouldn't you just enable multiple
> drivers to attach to the device?

Attaching multiple drivers to hardware resources is not supported in
Linux. There would all kinds of issues with ref counting resource
reservations, allowing multiple interrupts handlers (who acks the
interrupt), etc. What about loading/unload in different orders?

In Linux you attach a primary driver to the hardware and then
secondary drivers can attach to the  primary one.

> > Can everyone please try this patch out and see if loading radeonfb
> > causes any problems on your system. Having radeonfb loaded on x86 is
> > not a normal case. Radeon Xegl is going to depend on having both
> > radeon and radeonfb loaded so I need to know if this will cause
> > problems.
> 
> Last time I tried it, the console went blank (except for the cursor) somewhere
> during runlevel 3 bringup, so I rebooted blind and went back to a kernel
> without radeonfb.

That is the bug in radeonfb. It is a simple bug, loading the driver is
memsetting the framebuffer to zero. The VGA fonts were in the
framebuffer and they got wiped.

Another way to get the fonts back is to VT swap from console to X and
back again.

The bug is fixed in the patch. I'm working with benh to get it in the kernel.

-- 
Jon Smirl
[EMAIL PROTECTED]


-------------------------------------------------------
This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you shotput
a projector? How fast can you ride your desk chair down the office luge track?
If you want to score the big prize, get to know the little guy.
Play to win an NEC 61" plasma display: http://www.necitguy.com/?r 
--
_______________________________________________
Dri-devel mailing list
Dri-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to