Skip to contentSkip to conversation

question about setup.c

DISCUSSION John Gluck 2 participants 2 messages Dec 23, 2003 – Dec 26, 2003

lore
Share & tools
lore

John Gluck

author
#0 lore raw

Hi

I've been poking around the kernel startup code to try and understand the sequence of events. I came across something I don't understand and which might be redundant.

This is from the 2.6.0 kernel:

In arch/i386/kernel/setup.c the parse_cmdline_early() function, the argument "mem=XXX[kKmM]" is parsed.

In arch/sh/kernel/setup.c the parse_cmdline() function also parses "mem=XXX[kKmM]"

Could someone please explain this.

I am not subscribed to this list so a reply directly to me would be appreciated.

Thanks and a Merry Christmas to everyone

John

#1 lore raw
Quoted 8 lines · John Gluck

Hi

I've been poking around the kernel startup code to try and understand the sequence of events. I came across something I don't understand and which might be redundant.

This is from the 2.6.0 kernel:

Quoted 7 lines

In arch/i386/kernel/setup.c the parse_cmdline_early() function, the argument "mem=XXX[kKmM]" is parsed.

In arch/sh/kernel/setup.c the parse_cmdline() function also parses "mem=XXX[kKmM]"

Could someone please explain this.

This is because they are two different architectures! If you are compiling for i386 you aren't compiling for any other architecture, and vice versa!

IOW: only one subdirectory of "linux/arch" is used for each compilation.

Quoted 8 lines

I am not subscribed to this list so a reply directly to me would be appreciated.

Thanks and a Merry Christmas to everyone

John

BYE

Signature · 2 lines
	Paolo Ornati
	Linux v2.4.23