linuxppc_2_4_devel - Walnut compile

linuxppc_2_4_devel - Walnut compile

[Curtis, Allen]

I downloaded and tried to compile an IBM405GP kernel using the Walnut
configuration. Here is the path I have taken. Hopefully someone can take me
the rest of the way home.

1. make menuconfig (xconfig - does not work)
    and stripped out all of the extra junk

2. linker error - early_serial* symbols undefined
   modified drivers/char/Makefile - to include serial.c

3. linker error - serial_close() undefined
   reviewed the source code in arch/ppc. I believe that I need serial_sicc.c

4. Reviewed arch/ppc/config.in and discovered the following
  a. Minor error in file was preventing menu "IBM 4xx options --->" from
displaying (fixed)
     This is the only place I can find a reference for SICC console support.
This is dependent on 3 conditions. 1) Board is STB03xxx (not in any menus)
2) SERIAL_SICC is true 3) UART0_TTYS1 is true.
  b. Removed the platform dependency.

5. serial_sicc.c - does not compile because the only place the symbols are
defined is in ibmstb3.h (guess it is platform dependent)

Obviously my assumption about SICC serial support was wrong. What do I need
to successfully compile and link this platform?

Thanks in advance!

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: linuxppc_2_4_devel - Walnut compile

[Tom Rini]

On Thu, May 02, 2002 at 04:06:46PM -0700, Curtis, Allen wrote:

> 1. make menuconfig (xconfig - does not work)
>     and stripped out all of the extra junk
>

I hopefully just fixed xconfig.  Now I need to talk to Keith Owens to
get the proper fix pushed onto Marcelo.

> 2. linker error - early_serial* symbols undefined
>    modified drivers/char/Makefile - to include serial.c

Turn on CONFIG_SERIAL.  No one has tested any of the 4xx configs w/o
CONFIG_SERIAL, so it's not supprising it didn't work.  I've pushed a few
small things which might help however.

> 3. linker error - serial_close() undefined
>    reviewed the source code in arch/ppc. I believe that I need serial_sicc.c

This is odd.  Where was the linker error?  serial_close() is also in the
bootwrapper stuff.

> 4. Reviewed arch/ppc/config.in and discovered the following

Fix this as well (missing space was the actual problem).

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

RE: linuxppc_2_4_devel - Walnut compile

[Curtis, Allen]

> I hopefully just fixed xconfig.  Now I need to talk to Keith Owens to
> get the proper fix pushed onto Marcelo.
>

Thanks

> > 2. linker error - early_serial* symbols undefined
> >    modified drivers/char/Makefile - to include serial.c
>
> Turn on CONFIG_SERIAL.  No one has tested any of the 4xx configs w/o
> CONFIG_SERIAL, so it's not supprising it didn't work.  I've
> pushed a few
> small things which might help however.

I got this to build doing the following. In the process of testing it now.

1. Changed Standard/Generic Serial Port to [Y] from [M]
	This enabled the console on serial port option

Notes:
a) Makefile modifications were unnecessary in drivers/char.
b) I guess that SICC is not appropriate.....

> > 4. Reviewed arch/ppc/config.in and discovered the following
>
> Fix this as well (missing space was the actual problem).

Yup, that is what I did....

Thanks for the help!


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/

Re: linuxppc_2_4_devel - Walnut compile

[Tom Rini]

On Fri, May 03, 2002 at 09:39:36AM -0700, Curtis, Allen wrote:

> > > 2. linker error - early_serial* symbols undefined
> > >    modified drivers/char/Makefile - to include serial.c
> >
> > Turn on CONFIG_SERIAL.  No one has tested any of the 4xx configs w/o
> > CONFIG_SERIAL, so it's not supprising it didn't work.  I've
> > pushed a few
> > small things which might help however.
>
> I got this to build doing the following. In the process of testing it now.
>
> 1. Changed Standard/Generic Serial Port to [Y] from [M]
> 	This enabled the console on serial port option
>
> Notes:
> a) Makefile modifications were unnecessary in drivers/char.
> b) I guess that SICC is not appropriate.....

Right.  SICC is an STB03xxx-specific thing.

--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/

** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/