On 9/30/07, <b class="gmail_sendername">Tim Dijkstra</b> <<a href="mailto:newsuser@famdijkstra.org">newsuser@famdijkstra.org</a>> wrote:<div><span class="gmail_quote"></span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Sun, 30 Sep 2007 15:39:44 -0400<br>"Luis Mondesi" <<a href="mailto:lemsx1@gmail.com">lemsx1@gmail.com</a>> wrote:<br><br>> Yep. That's correct. But like I said before, solution 2 is not a solution
<br>> for Debian (Sid). That solution works for RPath Linux and perhaps other<br>> distros.<br><br>Maybe I'm being daft, but why does it work for other distro's?</blockquote><div><br>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.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> In Debian, all we need is to yield the CPU at the keyboard thread<br>> level.<br><br>Can't we yield it in our own code?</blockquote><div><br>No, the problem is in the library, way deeper than Splashy's code.
</div></div><br>-- <br>----)(----- <br>Luis Mondesi<br>Maestro Debiano<br><br>----- START ENCRYPTED BLOCK (Triple-ROT13) ------<br>Gur Hohagh [Yvahk] qvfgevohgvba oevatf gur fcvevg bs Hohagh gb gur fbsgjner jbeyq.<br>----- END ENCRYPTED BLOCK (Triple-ROT13) ------