mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Andrew Paprocki <andrew@ishiboo.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Geode GX framebuffer driver: Arcom vs. AMD
Date: Sat, 14 Jul 2007 21:18:54 +0200	[thread overview]
Message-ID: <20070714191854.GD13823@uranus.ravnborg.org> (raw)
In-Reply-To: <76366b180707141201u14585c2eyeb58f0b7b279ea1b@mail.gmail.com>

On Sat, Jul 14, 2007 at 03:01:56PM -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.
> 
> 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

After a very brief look on the relevant part of the patch:
-> Needs to be adapted to CodingStyle all over.
-> The use of AMD specific BUILDNUM etc are not used in-kernel
-> The HAL in lib/cimarron needs to be justified - who are the oter users?
-> There seems to be a _lot_ of specific defines in lib/cimarron - I wonder
   if this is the way used in the rest of the kernel?

But anyway - the patch it not trivially ready for inclusion.

	Sam

  reply	other threads:[~2007-07-14 19:17 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 [this message]
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
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=20070714191854.GD13823@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=andrew@ishiboo.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