RE: Loading and executing kernel from a non-standard address usin g SY SLINUX

• Next message: Martin J. Bligh: "[Bug 436] New: i82365.c does not compile (too many arguments to `pnp_activate_dev')"
• Previous message: Patrick Mochel: "Re: [PATCH] pcmcia: get initialization ordering right [Was: [PATCH 2.5] : i82365 & platform_bus_type]"
• In reply to: ravikumar.chakaravarthy@amd.com: "RE: Loading and executing kernel from a non-standard address usin g SY SLINUX"
• Next in thread: ravikumar.chakaravarthy@amd.com: "RE: Loading and executing kernel from a non-standard address usin g SY SLINUX"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

> Yes the kernel is uncompressed to the right location (0x200000), in my
> case. When I try to uncompress it to a non standard address (other than
> 0x100000), the address mapping is affected.

Why would you need to uncompress it to a different address? You mention
that your bootloader does something odd, but that should only affect the
address of the compressed bzImage, not the decompressed kernel ...

M.

-
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/

• Next message: Martin J. Bligh: "[Bug 436] New: i82365.c does not compile (too many arguments to `pnp_activate_dev')"
• Previous message: Patrick Mochel: "Re: [PATCH] pcmcia: get initialization ordering right [Was: [PATCH 2.5] : i82365 & platform_bus_type]"
• In reply to: ravikumar.chakaravarthy@amd.com: "RE: Loading and executing kernel from a non-standard address usin g SY SLINUX"
• Next in thread: ravikumar.chakaravarthy@amd.com: "RE: Loading and executing kernel from a non-standard address usin g SY SLINUX"
• Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

This archive was generated by hypermail 2b29 : Fri Mar 07 2003 - 22:00:25 EST