linux-kernel - Re: via agp patches

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]

Message-ID: <21d7e9970805311550r182c5291ta4c55e8069e631a1@mail.gmail.com>
Date:	Sun, 1 Jun 2008 08:50:39 +1000
From:	"Dave Airlie" <airlied@...il.com>
To:	"Greg KH" <gregkh@...e.de>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: via agp patches

On Sat, May 31, 2008 at 10:32 AM, Greg KH <gregkh@...e.de> wrote:
> Recently VIA has been distributing some pre-build kernel modules for
> their latest video cards without the source for it.  So I asked, and got
> the patches.  I've forward ported them to the current 2.6.26-rc4 tree,
> and they also apply cleanly to 2.6.25 as well.  They are here in the
> three emails after this one.
>
> I'm still working on getting some more information on exactly what these
> patches each do for a good changelog, but until then, if anyone has the
> hardware and wants to play with the code, here it is.
>
> If anyone has any questions, please let me know.
>

Like I can pull the cleanups and style one no problems, but really any
functional changes
need to be explained with some detail, and the drm changes need to be
submitted to dri-devel@...ts.sf.net
and Thomas Hellstrom would need to at least understand them before we
could let them into the kernel.

also adding support to the kernel without some idea of what userspace
can use it isn't going to happen.

VIA need to deal with the openchrome project to get those sort of
changes into an upstream X.org related driver.

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