linux-kernel - Re: [Linux-fbdev-devel] [PATCH v2] viafb: 2D engine rewrite (and viafb patches in general)

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <4AA47514.8080801@gmx.de>
Date:	Mon, 07 Sep 2009 04:51:00 +0200
From:	Florian Tobias Schandinat <FlorianSchandinat@....de>
To:	Jonathan Corbet <corbet@....net>
CC:	Andrew Morton <akpm@...ux-foundation.org>, JosephChan@....com.tw,
	ScottFang@...tech.com.cn, linux-fbdev-devel@...ts.sourceforge.net,
	linux-kernel@...r.kernel.org
Subject: Re: [Linux-fbdev-devel] [PATCH v2] viafb: 2D engine rewrite (and
 viafb patches in general)

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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/