[linuxdc-dev] Fwd: Kernel building

SourceForge Headquarters 1320 Columbia Street Suite 310 San Diego, CA 92101 +1 (858) 422-6466

----------  Forwarded Message  ----------

Subject: Kernel building
Date: Fri, 18 Oct 2002 07:51:27 -0700
From: "Mike Barnett" <mik...@ho...>
To: <ad...@mc...>

Hi... good morning, or maybe it's good evening for you.

    My keyboard and VGA converters are late getting to me.  It's difficult to
 get a good idea of what's really running on the system without them.  I can
 however build and boot CDs.  I have problems in that area.  I can build Bill
 Gatliff's distribution with no problem.  Burns OK and boots up. Now I want
 to be able to build using the latest releases from the CVS tree so that I
 can use the new drivers (microphone, etc).  What I did is as follows: 1..
 Build Bill's toolchain, kernel, initial RD just like instructed 2.. Burn
 Bill's image just to test it
  3.. Download a stock 2.4.18 kernel
  4.. Download CVS linuxSH kernel patches labeled linux-2.4-branch
  5.. Perform treelink.sh using LinuxSH tree
  6.. Perform treelink.sh using linux-dc tree
  7.. Copied .config from Bill's distribution as a template.  I've also used
 other people's .config file with no luck. 8.. Symbolically link my newly
 downloaded, patched tree into Bill's tree.  (linked 'kernel' to the source
 tree) 9.. AN IMPORTANT DIFFERENCE?? - I have to modify the Makefile in
 kernel/arch/sh to remove the "-mnoimplicit-fp" switch since Bill's toolchain
 is a little old 10.. Did a make clean dep zImage
  11.. Followed the normal steps I take making Bill's CD (compress initrd,
 scramble image, etc..) 12.. Burn CD
  13.. Boot in DC.  I get the initial Logo, SEGA splash screen.  And then the
 system resets itself.

So what could I be doing wrong?  Do you have a similar set up?
Perhaps my down-rev toolchain is causing some problems?
I have a hard time believing that the CVS tree for linux-dc has problems. 
 Any help you can lend would be greatly appreciated.  If you think it's a
 good idea, I can put this one out to the mailing list and see if anyone else
 has had this problem.

Thanks
Mike
(anyone wanna buy a coaster??)

-------------------------------------------------------