lkml.org 
[lkml]   [2003]   [May]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRe: [PATCH] Use correct x86 reboot vector
    Date
    Followup to:  <m1smrl5mbw.fsf@frodo.biederman.org>
    By author: ebiederm@xmission.com (Eric W. Biederman)
    In newsgroup: linux.dev.kernel
    >
    > There is some software at least that knows the difference. I have seen short
    > jumps in a couple of BIOS's. But a reset is very different from a
    > reboot. As memory must be reinitialized etc. So I think going to
    > 0xffff0000:0xfff0 would be a very bad idea if the intent is to get a
    > reliable reboot.
    >

    I agree.

    Jumping to 0xf000:0xfff0 is widely accepted to be a standard warm
    reboot (as *should* an INIT, e.g. triplefault, be, as well -- make
    sure A20 is enabled before tripping, though.) For quite a few (most?)
    BIOSes, the vector that is stored at 0xf000:0xfff0 in the running
    (BIOS decompressed and shadowed) configuration is *not* the same as
    the one at the RESET vector.

    -hpa
    --
    <hpa@transmeta.com> at work, <hpa@zytor.com> in private!
    "Unix gives you enough rope to shoot yourself in the foot."
    Architectures needed: ia64 m68k mips64 ppc ppc64 s390 s390x sh v850 x86-64
    -
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to majordomo@vger.kernel.org
    More majordomo info at http://vger.kernel.org/majordomo-info.html
    Please read the FAQ at http://www.tux.org/lkml/

    \
     
     \ /
      Last update: 2005-03-22 13:35    [W:0.022 / U:180.788 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site