good, I will let it start from 0x500, and linuxbios table after it. that is most easy, and don't need to use command line to pass the info, because it the signature is before 1K. YH - 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/
- References:
- RE: Inclusion of x86_64 memorize ioapic at bootup patch
- From: "Lu, Yinghai" <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: [email protected] (Eric W. Biederman)
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: yhlu <[email protected]>
- Re: Inclusion of x86_64 memorize ioapic at bootup patch
- From: [email protected] (Eric W. Biederman)
- RE: Inclusion of x86_64 memorize ioapic at bootup patch
- Prev by Date: Re: 2.6.15-mm2
- Next by Date: Re: [2.6 patch] OCFS2: __init / __exit problem
- Previous by thread: Re: Inclusion of x86_64 memorize ioapic at bootup patch
- Next by thread: Linux 2.6.15
- Index(es):
 |