From: "Antonino A. Daplas" <adaplas@gmail.com>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: linux-kernel@vger.kernel.org, Jordan Crouse <jordan.crouse@amd.com>
Subject: Re: Geode GX framebuffer driver: Arcom vs. AMD
Date: Sun, 15 Jul 2007 04:31:34 +0800 [thread overview]
Message-ID: <1184445094.4692.2.camel@daplas> (raw)
In-Reply-To: <76366b180707141201u14585c2eyeb58f0b7b279ea1b@mail.gmail.com>
On Sat, 2007-07-14 at 15:01 -0400, Andrew Paprocki wrote:
> 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.
>
There's a patch for the AMD Geode LX which I'm going to send for the -mm
tree soon. Its module name is lxfb.
Tony
next prev parent reply other threads:[~2007-07-14 20:32 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 19:01 Geode GX framebuffer driver: Arcom vs. AMD Andrew Paprocki
2007-07-14 19:18 ` Sam Ravnborg
2007-07-14 20:57 ` Andrew Paprocki
2007-07-14 22:13 ` Sam Ravnborg
2007-07-14 20:31 ` Antonino A. Daplas [this message]
2007-07-14 21:05 ` Andrew Paprocki
2007-07-14 22:55 ` Antonino A. Daplas
2007-07-18 1:42 ` Jordan Crouse
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=1184445094.4692.2.camel@daplas \
--to=adaplas@gmail.com \
--cc=andrew@ishiboo.com \
--cc=jordan.crouse@amd.com \
--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