[Splashy-devel] Initramfs bug understood
Luis Mondesi
lemsx1 at gmail.com
Mon Oct 1 01:01:03 UTC 2007
On 9/30/07, Tim Dijkstra <newsuser at famdijkstra.org> wrote:
>
> On Sun, 30 Sep 2007 15:39:44 -0400
> "Luis Mondesi" <lemsx1 at gmail.com> wrote:
>
> > Yep. That's correct. But like I said before, solution 2 is not a
> solution
> > for Debian (Sid). That solution works for RPath Linux and perhaps other
> > distros.
>
> Maybe I'm being daft, but why does it work for other distro's?
dunno. That's what Elliot, from RPath, said on #splashy. He said that they
needed to make Splashy use tty8. I don't know how RPath boot process works.
In Debian, though, there is no need. When Splashy starts from initramfs,
tty2 is used and no text is displayed to the screen (and the boot process is
never stopped since console-screen.sh is not executed to change the state of
the TTYs while Splashy is running). When usleep() is in the directfb
keyboard thread code, the boot process works fine and it goes fast.
> In Debian, all we need is to yield the CPU at the keyboard thread
> > level.
>
> Can't we yield it in our own code?
No, the problem is in the library, way deeper than Splashy's code.
--
----)(-----
Luis Mondesi
Maestro Debiano
----- START ENCRYPTED BLOCK (Triple-ROT13) ------
Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner
jbeyq.
----- END ENCRYPTED BLOCK (Triple-ROT13) ------
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.alioth.debian.org/pipermail/splashy-devel/attachments/20070930/0ad98251/attachment.htm
More information about the Splashy-devel
mailing list