From: martink@posteo.de (Martin Kepplinger)
To: kernelnewbies@lists.kernelnewbies.org
Subject: GSoC: RFC: fbdev fbtft auxdisplay or IIO
Date: Tue, 8 Mar 2016 13:48:23 +0100 [thread overview]
Message-ID: <56DECA17.80701@posteo.de> (raw)
In-Reply-To: <20160305174045.GA14401@kroah.com>
Am 2016-03-05 um 18:40 schrieb gregkh at 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 at kernelnewbies.org
> http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
>
prev parent reply other threads:[~2016-03-08 12:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-05 17:02 GSoC: RFC: fbdev fbtft auxdisplay or IIO Martin Kepplinger
2016-03-05 17:40 ` gregkh at linuxfoundation.org
2016-03-08 12:48 ` Martin Kepplinger [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56DECA17.80701@posteo.de \
--to=martink@posteo.de \
--cc=kernelnewbies@lists.kernelnewbies.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.