Changes I would like to get into the 2_4_devel

Changes I would like to get into the 2_4_devel

[Anders Blomdell]

Where do I send a request of the following changes to linuxppc_2_4_devel:

in arch/ppc/Makefile:
   add -D__powerpc__ to CPPFLAGS and CFLAGS (just like it is on  kernel.org)
     This makes drivers/char/serial.c compile correctly (no more 5 bit
     characters)

in Makefile:
   add -D__linux__ to CPPFLAGS
     This makes coda.h compile correctly (u_quad_t)

in arch/ppc/kernel/i8259.c:
   Some way to set
     pci_intack = 0;
   if we are running on a MVME 2400/2600, since the PIB (PCI-to-ISA Bridge)
  does
   not support anything but polling of the 8229 pair.

arch/ppc/platforms/prpmc800_setup.c:
   patch previously sent.

I know that you think I have an incorrectly configured gcc, but I think
that it's a nice feature if the kernel compiles with a gcc that has been
configured according to the 'http://penguinppc.org/embedded/cross-compiling/
', even though it warns about gcc-3.x (3.2 generates working code with the
above changes)...


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

Re: Changes I would like to get into the 2_4_devel

[Hollis Blanchard]

On Fri, 2002-10-25 at 12:30, Anders Blomdell wrote:
>
> in arch/ppc/Makefile:
>    add -D__powerpc__ to CPPFLAGS and CFLAGS (just like it is on  kernel.org)
>      This makes drivers/char/serial.c compile correctly (no more 5 bit
>      characters)
>
> in Makefile:
>    add -D__linux__ to CPPFLAGS
>      This makes coda.h compile correctly (u_quad_t)

<snip>

> I know that you think I have an incorrectly configured gcc, but I think
> that it's a nice feature if the kernel compiles with a gcc that has been
> configured according to the 'http://penguinppc.org/embedded/cross-compiling/
> ', even though it warns about gcc-3.x (3.2 generates working code with the
> above changes)...

This is a handy one-liner for seeing what defines gcc has:
	echo | powerpc-linux-gcc -E -dM -
When I run it with a cross-compiled gcc 2.95.3 *and* 3.2, I see both
	#define __linux__ 1
	#define __powerpc__ 1
The 2.95.3 was compiled with exactly the directions you refer to above.
3.2 was slightly different, but in both cases --target=powerpc-linux .

-Hollis

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

Re: Changes I would like to get into the 2_4_devel

[Tom Rini]

On Fri, Oct 25, 2002 at 07:30:59PM +0200, Anders Blomdell wrote:

> Where do I send a request of the following changes to linuxppc_2_4_devel:
>
> in arch/ppc/Makefile:
>   add -D__powerpc__ to CPPFLAGS and CFLAGS (just like it is on  kernel.org)
>     This makes drivers/char/serial.c compile correctly (no more 5 bit
>     characters)
>
> in Makefile:
>   add -D__linux__ to CPPFLAGS
>     This makes coda.h compile correctly (u_quad_t)

As Hollis has pointed out as well, it is very odd that you cannot get a
compiler which correctly defines __linux__ and __powerpc__.  You are
creating a powerpc-linux cross compiler correct, and not powerpc-eabi or
some other incantation?

> in arch/ppc/kernel/i8259.c:
>   Some way to set
>     pci_intack = 0;
>   if we are running on a MVME 2400/2600, since the PIB (PCI-to-ISA Bridge)
>  does
>   not support anything but polling of the 8229 pair.

This is an issue since you're running the MVME 2400/2600 under
CONFIG_ALL_PPC, yes?  Can you verify that in _devel, CONFIG_PPLUS works
on these boards, as from what I recall it should.  As for fixing
CONFIG_ALL_PPC, what I intend to do is add a check to verify the bridge
and then set the intack occordingly.

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

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