|
From: Hihn J. <Jas...@DA...> - 2002-01-30 20:53:14
|
Yes. You are correct. I cannot type. I have the stock driver from the bzip mentioned today. (Which I also compared to the 2.2 driver, which is eerily similar.) Where could I find this other driver of which you speak? Sorry about the barrage of questions earlier, but I was really wondering why no one has done those things yet. It seems to be a simple matter that even _I_ could do. ;) -J Hey, check out this humor from my demented mind: Linux Philosophy 101: ln -s /bin/less more -----Original Message----- From: Paul Mundt [mailto:le...@Ch...] Sent: Wednesday, January 30, 2002 3:43 PM To: Hihn Jason Cc: lin...@li... Subject: Re: [Linux-fbdev-devel] PPC 832 LCD Driver questions On Wed, Jan 30, 2002 at 09:33:44PM +0100, Hihn Jason wrote: > Is there some reason why it's bare bones? And by that I mean: > Why does the IOCTL function do nothing? > Why doesn't ....set_var() do any setting? > Why doesn't the driver read from the registers? (Particularly necessary if > you could change depth, resolution) > And what is this "int con" everywhere? console? > I'm presuming this is a typo, since I've never heard of an MPC832... If you're ferring to the MPC823, which driver in particular are you referring to? There are two of these in circulation (which should probably get around to being merged.. but thats another matter entirely..). Regards, -- Paul Mundt <le...@ch...> |