From: Nathan K. <nat...@gm...> - 2006-11-13 18:07:12
|
> > I'm not sure how to use the information in that link. Everything I'm > doing > > is in kernelspace and that tutorial appears to be for userspace > programming. > > Also it seems to be for a system with VGA hardware and ours has none, > we've > > got a virtual framebuffer that sits in system RAM. > > > > I'd considered that the cursor could be at fault somehow, but the cursor > > drawing code that fbcon points to (softcursor if I recall correctly) > just > > points back again to the cfb* functions. > > > > I don't suppose you have any other thoughts on this? I'm going to start > > feeling pretty stupid if I can't solve it soon. ;) > > Looking at the code all cursor control from the driver level has been > removed. It been put into fbcon. So if you enable fbcon then it will > activate the cursor and have full control of the cursor. Only terminal > codes will turn it off. Any reason to fbcon enabled? > Well, without fbcon I'm not too sure how we could see any of our output. To view our graphics data we're reading from the framebuffer and sending that data to another piece of hardware that puts it on a screen. |