From: Jon Smirl <jonsmirl@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Adrian Bunk <bunk@stusta.de>,
adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: RFC: disallow modular framebuffers
Date: Tue, 1 Mar 2005 01:07:51 -0500 [thread overview]
Message-ID: <9e47339105022822079eb6f86@mail.gmail.com> (raw)
In-Reply-To: <4223E59D.3060902@pobox.com>
The on-going work to support XGL is going to change the significance
of modular framebuffers. Right now there is no real need to load
framebuffers on X86. In the future XGL is probably going to require
that the framebuffer be loaded. When XGL initially starts being
distributed people are not going to have framebuffer loaded so modular
framebuffer will let you load it on demand. From then on, in the XGL
case, if framebuffers weren't modular Redhat would have to compile all
75 of them into their distro kernel.
I don't think the framebuffer codebase has received the same level of
inspection that a lot of the other kernel code has. This is probably
because all X86 users can currently avoid loading them due to VGA
compatibility.
--
Jon Smirl
jonsmirl@gmail.com
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
WARNING: multiple messages have this Message-ID (diff)
From: Jon Smirl <jonsmirl@gmail.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Adrian Bunk <bunk@stusta.de>,
adaplas@pol.net, linux-fbdev-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org
Subject: Re: RFC: disallow modular framebuffers
Date: Tue, 1 Mar 2005 01:07:51 -0500 [thread overview]
Message-ID: <9e47339105022822079eb6f86@mail.gmail.com> (raw)
In-Reply-To: <4223E59D.3060902@pobox.com>
The on-going work to support XGL is going to change the significance
of modular framebuffers. Right now there is no real need to load
framebuffers on X86. In the future XGL is probably going to require
that the framebuffer be loaded. When XGL initially starts being
distributed people are not going to have framebuffer loaded so modular
framebuffer will let you load it on demand. From then on, in the XGL
case, if framebuffers weren't modular Redhat would have to compile all
75 of them into their distro kernel.
I don't think the framebuffer codebase has received the same level of
inspection that a lot of the other kernel code has. This is probably
because all X86 users can currently avoid loading them due to VGA
compatibility.
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2005-03-01 6:08 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-01 2:41 RFC: disallow modular framebuffers Adrian Bunk
2005-03-01 3:46 ` Jeff Garzik
2005-03-01 6:07 ` Jon Smirl [this message]
2005-03-01 6:07 ` Jon Smirl
2005-03-01 17:52 ` [Linux-fbdev-devel] " James Simmons
2005-03-01 12:49 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-03-01 12:49 ` Antonino A. Daplas
2005-03-01 13:15 ` Antonino A. Daplas
2005-03-03 16:56 ` Adrian Bunk
2005-03-03 19:50 ` Antonino A. Daplas
2005-03-03 20:20 ` Adrian Bunk
2005-03-03 20:20 ` Adrian Bunk
2005-03-03 20:37 ` Antonino A. Daplas
2005-03-03 20:37 ` Antonino A. Daplas
2005-03-03 23:07 ` [2.6 patch] make savagefb one module Adrian Bunk
2005-03-04 9:17 ` [Linux-fbdev-devel] " Geert Uytterhoeven
2005-03-05 1:12 ` Adrian Bunk
2005-03-05 1:12 ` [Linux-fbdev-devel] " Adrian Bunk
2005-03-05 20:49 ` Antonino A. Daplas
2005-03-05 20:49 ` [Linux-fbdev-devel] " Antonino A. Daplas
2005-03-01 16:59 ` RFC: disallow modular framebuffers Jesse Barnes
2005-03-02 11:32 ` [Linux-fbdev-devel] " David Vrabel
2005-03-02 12:17 ` Paul Mundt
2005-03-02 18:01 ` Jon Smirl
2005-03-02 18:01 ` Jon Smirl
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=9e47339105022822079eb6f86@mail.gmail.com \
--to=jonsmirl@gmail.com \
--cc=adaplas@pol.net \
--cc=bunk@stusta.de \
--cc=jgarzik@pobox.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.