initramfs-tools.git/scripts/init-top/framebuffer, branch 0.95.1

nuke framebuffer boot script

2009-07-29T13:48:15+00:00

fb should be loaded after initramfs by init to have a beautiful userland. allows faster boot not to try parsing crazy things with only posix sh at our hands. this will need a README.DEBIAN section as noone is now currently loading fbcon. Signed-off-by: maximilian attems

scripts/init-top/framebuffer: i915 needs intel-agp too

2009-06-16T16:57:23+00:00

The i915 DRM module doubles as a framebuffer of sorts, at least in kernel mode-setting setups; like its cousins intelfb and i810fb, it effectively requires intel-agp despite not actually using any of its symbols. As such, could you please arrange for scripts/init-top/framebuffer to give it the same treatment, per the following patch?: (closes: #533258) Signed-off-by: maximilian attems

init-top/framebuffer: syntax fix.

2009-04-01T23:54:46+00:00

fix wrong merge of e184c8c2a9ad4520cf0cf4536301c6ae6206e911 scripts/init-top/framebuffer: 84: Syntax error: ")" unexpected (expecting ";;")

init-top/framebuffer: Load intel-agp for intelfb

2009-03-31T14:00:05+00:00

After further experimentation, I discovered additional problems that my first patch did not address, namely that 1) Some FB drivers need the AGP subsystem up and running before they are loaded and 2) intelfb needs intel-agp.ko, but does not have a dependency on it. intelfb does not actually *work* on my testsystem after this (it crashes), but unlike with plain initramfs-tools, it loads (and prints something useful if loaded with the probeonly option). I'll try to find out why it fails to work tomorrow; it's probably an unrelated issue. [ make the patch applyable, probably whitespace damaged, fix comments, no need to pass -q to modprobe that is set globaly -maks ] (closes: #416063, #455876) Signed-off-by: maximilian attems

init-top/framebuffer: ignore blacklist for forced vga= usage.

2009-03-20T21:48:05+00:00

DO NOT USE -Qb for framebuffer. Blank ttys when using vesafb (vga=xxx) LP: #129910 [ s/-Q/-q/ for modprobe options -maks ]

Revert "framebuffer: Let udev create fb devices."

2008-12-15T10:31:15+00:00

udev isn't started at this point and therefore can't create framebuffer devices. This causes usplash not to run on PS3. set sane permissions will making the char files. This reverts commit 0aec8b0c22b7622841c4ab7a3b492b4d2657456f.

framebuffer: Add support for uvesafb

2008-12-15T10:11:22+00:00

Uvesafb framebuffer driver needs v86d userspace program but when fb driver is modprobed at init-top stage of initrd, /dev/zero and /dev/mem are missing because udev have not been run yet.

framebuffer: Leave tty devices for udev too.

2008-03-25T13:47:17+00:00

udev creates tty devices too, in the case of not using udev, we need to ship more anyway, so no need to worry about that right now.

framebuffer: Let udev create fb devices.

2008-03-25T13:40:45+00:00

nuke fb device mknod creation as udev creates the fb device nodes. suggested by waldi. positive test on qemu with usplash. let's see if we get a bad interaction with usplash and vga=XXX boots.

scripts/init-top/framebuffer: fix variable name

2007-09-05T20:22:20+00:00

s/fbnum/fbno/