Linux MIPS Architecture development
 help / color / mirror / Atom feed
* mips64/setup.c
@ 2003-07-31 15:54 David Kesselring
  2003-07-31 16:52 ` mips64/setup.c Ralf Baechle
  0 siblings, 1 reply; 4+ messages in thread
From: David Kesselring @ 2003-07-31 15:54 UTC (permalink / raw)
  To: linux-mips

Is the file mips64/setup.c used? I believe that I see two problems in it;
1) The Ocelot options in setup_arch have case statements without a switch.
2) There is no option for Sead but the mips64 build for sead compiles
fine.
Is this some leftovers from some merging that has been talked about?

David Kesselring
Atmel MMC
dkesselr@mmc.atmel.com
919-462-6587

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: mips64/setup.c
  2003-07-31 15:54 mips64/setup.c David Kesselring
@ 2003-07-31 16:52 ` Ralf Baechle
  2003-07-31 18:22   ` mips64/setup.c David Kesselring
  0 siblings, 1 reply; 4+ messages in thread
From: Ralf Baechle @ 2003-07-31 16:52 UTC (permalink / raw)
  To: David Kesselring; +Cc: linux-mips

On Thu, Jul 31, 2003 at 11:54:15AM -0400, David Kesselring wrote:

> Is the file mips64/setup.c used? I believe that I see two problems in it;
> 1) The Ocelot options in setup_arch have case statements without a switch.

Ocelot 64-bit kernel is currently work in progress.  A first cut of
the patch was posted to this mailing list a few days ago.

> 2) There is no option for Sead but the mips64 build for sead compiles
>    fine.

The fun of when two almost identical files go out of sync.

> Is this some leftovers from some merging that has been talked about?

No.  The big merge thing did only happen in 2.6.  It's way to intrusive
for 2.4.

  Ralf

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: mips64/setup.c
  2003-07-31 16:52 ` mips64/setup.c Ralf Baechle
@ 2003-07-31 18:22   ` David Kesselring
  2003-07-31 20:17     ` mips64/setup.c Ralf Baechle
  0 siblings, 1 reply; 4+ messages in thread
From: David Kesselring @ 2003-07-31 18:22 UTC (permalink / raw)
  To: Ralf Baechle; +Cc: linux-mips

On Thu, 31 Jul 2003, Ralf Baechle wrote:

> On Thu, Jul 31, 2003 at 11:54:15AM -0400, David Kesselring wrote:
>
> > Is the file mips64/setup.c used? I believe that I see two problems in it;
> > 1) The Ocelot options in setup_arch have case statements without a switch.
>
> Ocelot 64-bit kernel is currently work in progress.  A first cut of
> the patch was posted to this mailing list a few days ago.
>
> > 2) There is no option for Sead but the mips64 build for sead compiles
> >    fine.
>
> The fun of when two almost identical files go out of sync.
Then do you know what is happening when 64bit sead is configured? Why
doesn't the compile fail?



>
> > Is this some leftovers from some merging that has been talked about?
>
> No.  The big merge thing did only happen in 2.6.  It's way to intrusive
> for 2.4.
>
>   Ralf
>
>

David Kesselring
Atmel MMC
dkesselr@mmc.atmel.com
919-462-6587

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: mips64/setup.c
  2003-07-31 18:22   ` mips64/setup.c David Kesselring
@ 2003-07-31 20:17     ` Ralf Baechle
  0 siblings, 0 replies; 4+ messages in thread
From: Ralf Baechle @ 2003-07-31 20:17 UTC (permalink / raw)
  To: David Kesselring; +Cc: linux-mips

On Thu, Jul 31, 2003 at 02:22:45PM -0400, David Kesselring wrote:

> > On Thu, Jul 31, 2003 at 11:54:15AM -0400, David Kesselring wrote:
> >
> > > Is the file mips64/setup.c used? I believe that I see two problems in it;
> > > 1) The Ocelot options in setup_arch have case statements without a switch.
> >
> > Ocelot 64-bit kernel is currently work in progress.  A first cut of
> > the patch was posted to this mailing list a few days ago.
> >
> > > 2) There is no option for Sead but the mips64 build for sead compiles
> > >    fine.
> >
> > The fun of when two almost identical files go out of sync.
> Then do you know what is happening when 64bit sead is configured? Why
> doesn't the compile fail?

This is easy, there is a function call missing which won't cause an
error message unlike a missing function.  Don't ask me why - it just seems
the 64-bit SEAD port was never completly sent to me or so.  Anyway, I
just fixed this in the linux_2_4 CVS branch; as the result of merging
mips with mips64 this bug was magically dealt with in 2.6.

  Ralf

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2003-07-31 20:17 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-07-31 15:54 mips64/setup.c David Kesselring
2003-07-31 16:52 ` mips64/setup.c Ralf Baechle
2003-07-31 18:22   ` mips64/setup.c David Kesselring
2003-07-31 20:17     ` mips64/setup.c Ralf Baechle

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox