Hi!
> >I'm thinking about how to clean up video resume/how to get it to work
> >for non-VESA video modes (jikos' case).
> >
> >I guess the cleanest solution would be to just call set_mode from
> >wakeup.S.... but that is not as easy as I imagined, because bootup
> >code seems to be compiled separately.
> >
> >Is there some easy way to retain bootup code in memory, so that wakeup
> >can use it? Or is there some easy solution I'm missing?
>
> No, not really. The setup code is not even part of the kernel binary
> proper, and may not even have been run under certain circumstances.
>
> The "easy" solution is to link it in again, which seems to be what
> you're doing. Now, currently the boot code is compiled after vmlinux is
> complete, so some of the build ordering would have to be changed and/or
> some of the code rearranged.
I guess major change is to rename conflicting symbols, so that it is
possible to link it twice. That would mean boot_memset() instead of
memset() etc... Is that acceptable?
> I suggest we tackle this *after* the x86 merge.
Well, we still have the regression on jikos' strange system, and I
would like to understand what is going on there.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures)
http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
