linux-kernel - Geode GX framebuffer driver: Arcom vs. AMD

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-next>] [day] [month] [year] [list]

Message-ID: <76366b180707141201u14585c2eyeb58f0b7b279ea1b@mail.gmail.com>
Date:	Sat, 14 Jul 2007 15:01:56 -0400
From:	"Andrew Paprocki" <andrew@...iboo.com>
To:	linux-kernel@...r.kernel.org
Subject: Geode GX framebuffer driver: Arcom vs. AMD

Is there any reason why the GPL framebuffer driver for the GX/GX1/LX
directly from AMD is not integrated into the kernel and only a custom
driver for only the GX/GX1 written by Arcom exists?
(drivers/video/geode/*)

If you have an LX, the Arcom driver won't work and it is difficult to
use AMD's patch for 2.6.11 with a more recent kernel because the
drivers/video/geode directory has filename conflicts with files in the
patch.

If there are no issues preventing its inclusion, would updated patches
be accepted to switch to AMD's framebuffer driver? The AMD patches
would need to be combined to support all three platforms in the driver
dir, all sitting on top of the Cimarron HAL installed in lib/cimarron.

The entire AMD LX patch for 2.6.11 is here:
http://www.amd.com/files/connectivitysolutions/geode/geode_lx/Patches_Linux2.6.11_Common_02.03.0100.patch

The relevant parts are:
drivers/video/geode/*
lib/cimarron/*

Thanks, -Andrew
-
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/