RE: [Linux-fbdev-devel] PPC 832 LCD Driver questions

[Hihn J. <Jas...@DA...>]

I have the HHL one. But the one Wolfgang referred to looks pretty much the
same. Other than the inclusion of a mmap() function, more LCD panels, #ifdef
debugs, and some small symantec differences, they are the same. No
functionality is removed. You could probably just use his driver, and skip a
merge, probably. 

Of the things I needed to do:
the power off/on was one.
text mode emulation was another. (adding an auto-blitted text plane) (Does
this already exist somehow for frame buffer console device?) I can have this
done in application code, but I think it'd be a faster port if I could hand
off text to the kernel...

Perhaps I'm still a bit wet behind the ears.. I thought IOCTLs were for
anything that didn't match the open/read/write/close file style interface,
thereby making a power on/off a IOCTL. How would you go about implementing
those?

Thanks
-J

-----Original Message-----
From: Paul Mundt [mailto:le...@Ch...]
Sent: Wednesday, January 30, 2002 4:05 PM
To: Hihn Jason
Cc: lin...@li...
Subject: Re: [Linux-fbdev-devel] PPC 832 LCD Driver questions


On Wed, Jan 30, 2002 at 09:57:38PM +0100, Hihn Jason wrote:
> 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. ;) 
> 
There's two drivers for this.. the one in the linuxppc tree (maintained by
Wolfgang Denk, and the one in the MontaVista Linux (formerly HHL) tree which
is maintained by myself. Have been meaning to merge the two.. but lack of
time
is a rather irritating nuisance.

If one of them doesn't have what you're looking for, you might wish to
consult the other one before making any decisions over what to start hacking
on..

As far as things like the ioctl() interface.. there really isn't much need
for
it, since there isn't a whole lot that's needed in this case. Even powering
the panel on and off isn't worth dealing with through the ioctl() interface.
Is there anything in particular that you really have a need for the ioctl()
for?

Regards,

-- 
Paul Mundt <le...@ch...>