Jarod Wilson wrote:
On Saturday 26 January 2008 05:19:14 am Roland McGrath wrote:
Is F-[78] going to stay on 2.6.23 for a while, or switch to 2.6.24 fairly
soon?
Chuck was talking about branching in cvs to start doing 2.6.24 builds for at
least F8 as soon as possible for people
Is F-[78] going to stay on 2.6.23 for a while, or switch to 2.6.24 fairly soon?
Thanks,
Roland
___
Fedora-kernel-list mailing list
Fedora-kernel-list@redhat.com
https://www.redhat.com/mailman/listinfo/fedora-kernel-list
On Saturday 26 January 2008 05:19:14 am Roland McGrath wrote:
Is F-[78] going to stay on 2.6.23 for a while, or switch to 2.6.24 fairly
soon?
Chuck was talking about branching in cvs to start doing 2.6.24 builds for at
least F8 as soon as possible for people to test w/o committing
On Sat, 26 Jan 2008, Jarod Wilson wrote:
On Saturday 26 January 2008 05:19:14 am Roland McGrath wrote:
Is F-[78] going to stay on 2.6.23 for a while, or switch to 2.6.24 fairly
soon?
Chuck was talking about branching in cvs to start doing 2.6.24 builds for at
least F8 as soon
Ok, thanks for the info. If it's not likely to be weeks and weeks, then I
don't think I'll update the utrace/2.6.23 backport any more with recent fixes.
utrace/2.6-current is now on 2.6.24, and I won't rebase it for a few days.
When it breaks rawhide or when I get to it, I'll branch utrace/2.6.24
Mark ([EMAIL PROTECTED]) said:
Why wouldn't it be a module like (most) other framebuffers?
Well.. vesafb is also enabled with 'y' and because uvesafb is it's
successor it seems logical to me that it also gets enabled with 'y'
(not as a module but build in). Perhaps a good idea for fedora
On 01/08/2008 09:30 AM, Mark wrote:
Hey,
I just downloaded and installed the latest kernel rpm from koji [1]
but found out that uvesafb isn't enabled in the fedora kernels. Could
a kernel maintainer put the following value in the config-generc:
CONFIG_FB_UVESA=y
so that uvesafb is
To execute.. Quote from [1]:
add video=uvesafb:1024x768-32,mtrr:3,ywrap (or similar) to your
kernel command line
Right, but how does that work if built-in static? Is it relying
on initialization order vs. initramfs unpacking to find its userspace
component? Is it just spinning waiting
Mark ([EMAIL PROTECTED]) said:
AFAIK, we don't ship the tools for uvesafb, so it's a little late for
it to be a successor. How does it execute them if it's built-in, anyway?
uvesafb just got included in the 2.6.24 which isn't even final yet so
it's not 'late'.. more early than late
