linux-fbdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Russell King <rmk@arm.linux.org.uk>
To: James Simmons <jsimmons@infradead.org>
Cc: Linux Fbdev development list
	<linux-fbdev-devel@lists.sourceforge.net>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	Linux console project <linuxconsole-dev@lists.sourceforge.net>
Subject: Re: [ANNOUCE] fbdev changes finished.
Date: Thu, 17 Oct 2002 18:27:56 +0100	[thread overview]
Message-ID: <20021017182756.B3326@flint.arm.linux.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.33.0210170919210.4730-100000@maxwell.earthlink.net>; from jsimmons@infradead.org on Thu, Oct 17, 2002 at 09:38:37AM -0700

On Thu, Oct 17, 2002 at 09:38:37AM -0700, James Simmons wrote:
>   I like to annouce that I just finished the final fbdev changes. They are
> in the BK repository bk://fbdev.bkbits.net/fbdev-2.5. The changes are
> 
> 1) Removal of all console related code in the lower level drivers. Smaller
>    easier to program drivers.
> 
> 2) Now you can use the framebuffer driver WITHOUT framebuffer console.
>    Last night I built a kernel with MDA console and used the VESA
>    framebuffer by itself. Now you can easily debug new framebuffer
>    drivers. The real bonus is for embedded systems you have much smaller
>    kernels.
> 
> 3) I moved the agp and drm code into drivers/video. I did NOT place any
>    drm code with framebuffer code at people's request. I simiple moved the
>    directory from one spot to another. The main reason I did this was
>    because some framebuffer drivers will need to use the agp code initialized
>    before the framebuffer layer. The DRM code was moved because it makes
>    sense to move it there.
> 
> 4) I cleaned up the config.in for all the video stuff across all
>    platforms.
> 
> You can grab the lastest BK tree at
> 
> bk://fbdev.bkbits.net/fbdev-2.5
> 
> Give it a try. For people who want a diff it is avaiable at
> 
> http://phoenix.infradead.org/~jsimmons/fbdev.diff.gz

... which is not representative of the changes.

Can you _please_ take much more care over patches and such like and take
the time to get them correct _please_.

I really don't like patches that float around that unintentionally delete
other peoples drivers for no reason.

-- 
Russell King (rmk@arm.linux.org.uk)                The developer of ARM Linux
             http://www.arm.linux.org.uk/personal/aboutme.html



-------------------------------------------------------
This sf.net email is sponsored by: viaVerio will pay you up to
$1,000 for every account that you consolidate with us.
http://ad.doubleclick.net/clk;4749864;7604308;v?
http://www.viaverio.com/consolidator/osdn.cfm

  reply	other threads:[~2002-10-17 17:27 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-10-17 16:38 [ANNOUCE] fbdev changes finished James Simmons
2002-10-17 17:27 ` Russell King [this message]
2002-10-17 18:42   ` James Simmons
2002-10-21 10:32 ` Jani Monoses

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=20021017182756.B3326@flint.arm.linux.org.uk \
    --to=rmk@arm.linux.org.uk \
    --cc=jsimmons@infradead.org \
    --cc=linux-fbdev-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxconsole-dev@lists.sourceforge.net \
    /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;
as well as URLs for NNTP newsgroup(s).