GSoC: RFC: fbdev fbtft auxdisplay or IIO
Hi GregKH, In looking around what I could do in the mid-future, possibly as a GSoC project (?), I have 2 questions: Is there active ongoing work on getting rid of drivers/auxdisplay? There are 2 drivers left in there... If not, would that be desired? What is the status of fbtft? Moving drivers *in* to staging feels wrong, but fbtft isn't yet present in the main tree. I would guess that fbtft is where these auxdisplay drivers could go. Would you put them into another area? fbdev? Different topic: IIO: I have ideas for mma8452 driver additions, and along this way, additions to the iio sysfs ABI. Would it make sense to lay this out and make a project out of it? Thanks for your time and work, martin -- Martin Kepplinger https://martinkepplinger.com
On Sat, Mar 05, 2016 at 06:02:09PM +0100, Martin Kepplinger wrote:
Hi GregKH,
In looking around what I could do in the mid-future, possibly as a GSoC project (?), I have 2 questions:
Is there active ongoing work on getting rid of drivers/auxdisplay? There are 2 drivers left in there... If not, would that be desired?
I really do not know, do you have the hardware for those devices?
What is the status of fbtft? Moving drivers *in* to staging feels wrong, but fbtft isn't yet present in the main tree. I would guess that fbtft is where these auxdisplay drivers could go. Would you put them into another area? fbdev?
There's a thread in the archives somewhere that talks about moving fbtft into being a "real" drm driver. I suggest you look into that if you are curious.
Different topic: IIO: I have ideas for mma8452 driver additions, and along this way, additions to the iio sysfs ABI. Would it make sense to lay this out and make a project out of it?
That might be good, care to go into more details about this? thanks, greg k-h
Am 2016-03-05 um 18:40 schrieb gregkh@linuxfoundation.org:
On Sat, Mar 05, 2016 at 06:02:09PM +0100, Martin Kepplinger wrote:
Hi GregKH,
In looking around what I could do in the mid-future, possibly as a GSoC project (?), I have 2 questions:
Is there active ongoing work on getting rid of drivers/auxdisplay? There are 2 drivers left in there... If not, would that be desired?
I really do not know, do you have the hardware for those devices?
What is the status of fbtft? Moving drivers *in* to staging feels wrong, but fbtft isn't yet present in the main tree. I would guess that fbtft is where these auxdisplay drivers could go. Would you put them into another area? fbdev?
There's a thread in the archives somewhere that talks about moving fbtft into being a "real" drm driver. I suggest you look into that if you are curious.
Different topic: IIO: I have ideas for mma8452 driver additions, and along this way, additions to the iio sysfs ABI. Would it make sense to lay this out and make a project out of it?
That might be good, care to go into more details about this?
just for the record, I won't do a GSoC project this year. Thought it through, too little time, less than any usual year. Consider auxdisplay and fbtft a suggestion for anyone who is reading this. Ask a relevant list why the auxdisplay directory is there, get the hardware and rewrite those 2 drivers. I'll continue working on the iio list on various stuff as time permits and see what happens next year regarding a different task. ... And I know fixing -rc1 will come up more often that I would like it :)
thanks,
greg k-h
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
participants (2)
-
gregkhï¼ linuxfoundation.org -
Martin Kepplinger