From: "Andrew Paprocki" <andrew@ishiboo.com>
To: "Antonino A. Daplas" <adaplas@gmail.com>
Cc: linux-kernel@vger.kernel.org, "Jordan Crouse" <jordan.crouse@amd.com>
Subject: Re: Geode GX framebuffer driver: Arcom vs. AMD
Date: Sat, 14 Jul 2007 17:05:07 -0400 [thread overview]
Message-ID: <76366b180707141405n7aeb9cf0i6d66ca5b0093bd8f@mail.gmail.com> (raw)
In-Reply-To: <1184445094.4692.2.camel@daplas>
Tony,
Do you have the patch working already? I'd love to try this out in the
meantime on the LX system I am developing with at the moment. I'm
assuming you worked this into the existing Arcom framework (gxfb) and
pulled the necessary pieces from the AMD code?
I looked at doing this, but it just seemed easier to use the AMD
provided driver, as it would be easier to merge any changes in the
future and might provide more full support for the hardware and all
its modes.
Also, question for AMD/Jordan.. Is AMD going to provide any
support/patches for the existing gxfb and this new lxfb? (Maybe
perhaps an AMD supported DirectFB driver? :))
If anyone else is interested, I'll get around to making a patch of the
work I just did to bring the original AMD 2.6.11 framebuffer &
Cimarron fully up to date with the 2.6.22 tree. If AMD is going to
continue to maintain their own driver, this will allow the use of an
up-to-date kernel.
Thanks, -Andrew
On 7/14/07, Antonino A. Daplas <adaplas@gmail.com> wrote:
> 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 21:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-14 19:01 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
2007-07-14 21:05 ` Andrew Paprocki [this message]
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=76366b180707141405n7aeb9cf0i6d66ca5b0093bd8f@mail.gmail.com \
--to=andrew@ishiboo.com \
--cc=adaplas@gmail.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
Powered by JetHome