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] [thread-next>] [day] [month] [year] [list]
Date:	Sun, 6 Sep 2009 07:40:02 -0600
From:	Jonathan Corbet <corbet@....net>
To:	Florian Tobias Schandinat <FlorianSchandinat@....de>
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)

> 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.

> 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.

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?

jon

--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ