From: Florian Tobias Schandinat <FlorianSchandinat@gmx.de>
To: Jonathan Corbet <corbet@lwn.net>
Cc: Andrew Morton <akpm@linux-foundation.org>,
JosephChan@via.com.tw, ScottFang@viatech.com.cn,
linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH v2] viafb: 2D engine rewrite (and viafb patches in general)
Date: Mon, 07 Sep 2009 04:51:00 +0200 [thread overview]
Message-ID: <4AA47514.8080801@gmx.de> (raw)
In-Reply-To: <20090906074002.7976d4a5@bike.lwn.net>
Jonathan Corbet schrieb:
>> Do you have a pointer to the OLPC tree?
>
> git://dev.laptop.org/olpc-2.6
>
> They are working in the olpc-2.6.30 branch, currently.
Thanks. After having a look at it seems concerning viafb to be mostly
Haralds patches with 1 or 2 extra ones.
>> I'd really like to see VX855/OLPC support in mainline as soon as
>> possible as I consider it a good thing to support "new" hardware early.
>> However even if I am capable to write such support based on Haralds work
>> I don't want to see it in mainline as long as no one with that hardware
>> tested it.
>
> I do have the hardware, and I've taken on the responsibility for making
> pieces of it work. In my mind, that includes being responsible for
> mainlining things too. I will start to work in that direction; 2.6.33
> should be a reasonable target for the bulk of it.
>
> My thinking, FWIW, is to turn the viafb code into something more like a
> regular multi-function device driver. I've already integrated Harald's i2c
> stuff with the OLPC code; I need to add proper GPIO support next. Then
> there will be the V4L2 chunk for the video capture engine. Along the way,
> I may try to introduce some foreign concepts like locking.
Feel free to add the things you like. The main objective is probably to
get things working and stable. I do not have an idea how good that will
work out as I don't know how much code that requires. If you think
that's the way to go, then we'll try it and see whether it leads to
something usable and maintainable.
> I have a tree on git.lwn.net now, but it's against the 2.6.30 base. I will
> try to bring things forward to a more current tree sometime soon and put it
> up as, at least, a place where we can see the various lines of development
> going on.
>
> Sound good?
Jep, that's fine with me. I'll try to rebase&integrate the patches I
consider interesting from Harald's tree in -mm. I guess that's a good
thing to do as that's the latest used common base.
Any objections?
Regards,
Florian Tobias Schandinat
prev parent reply other threads:[~2009-09-07 2:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-30 21:07 [PATCH] viafb: 2D engine rewrite Florian Tobias Schandinat
2009-09-04 20:43 ` [PATCH v2] " Florian Tobias Schandinat
2009-09-05 22:16 ` [PATCH v2] viafb: 2D engine rewrite (and viafb patches in general) Jonathan Corbet
2009-09-05 23:01 ` Andrew Morton
2009-09-06 0:38 ` Florian Tobias Schandinat
2009-09-06 3:02 ` [Linux-fbdev-devel] " Andrew Morton
2009-09-06 13:40 ` Jonathan Corbet
2009-09-07 2:51 ` Florian Tobias Schandinat [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=4AA47514.8080801@gmx.de \
--to=florianschandinat@gmx.de \
--cc=JosephChan@via.com.tw \
--cc=ScottFang@viatech.com.cn \
--cc=akpm@linux-foundation.org \
--cc=corbet@lwn.net \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linux-kernel@vger.kernel.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).