kernelnewbies.kernelnewbies.org archive mirror
 help / color / mirror / Atom feed
From: gregkh@linuxfoundation.org (gregkh at linuxfoundation.org)
To: kernelnewbies@lists.kernelnewbies.org
Subject: GSoC: RFC: fbdev fbtft auxdisplay or IIO
Date: Sat, 5 Mar 2016 09:40:45 -0800	[thread overview]
Message-ID: <20160305174045.GA14401@kroah.com> (raw)
In-Reply-To: <56DB1111.6090106@posteo.de>

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

  reply	other threads:[~2016-03-05 17:40 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 [this message]
2016-03-08 12:48   ` Martin Kepplinger

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=20160305174045.GA14401@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).