[linuxdc-dev] Kernel update 2001-02-21 (fwd)

[M. R. B. <ma...@uw...>]

I guess I was up a little to late, I left off the 's', and it bounced,
sorry to keep y'all waiting :).

M. R.



---------- Forwarded message ----------
Date: Wed, 21 Feb 2001 10:12:13 -0600 (CST)
From: "M. R. Brown" <ma...@uw...>
To: lin...@li...
Subject: Kernel update 2001-02-21

Hey all,

I've submitted a batch of updates to CVS; now the kernel isn't broken by
default :).  All that's there right now is the necessary RTC stuff to keep
the kernel from hanging, and low-level interrupt routines for the
PowerVR2DC chip (or G2 bus or whatever).  Anyway, I've tested it via
serial, and ethernet+serial.  Here's a brief synopsis:

- I compiled my tree using a fairly recent snapshot of gcc.  My version of
  binutils is 2.10.1.  HOWTOs for tool-building are in the works, I'd
  figure the code would look better first :)

- gcc has a "bug" with the flag -m4-nofpu that's specified in
  arch/sh/Makefile.  Either apply my attached patch, or change the lines
  that read -m4-nofpu to -m4.

- I've also attached a .config file that you can use, it has everything
  completely stripped out.

- If you're ready to build, do a:
  $ make ARCH=sh dep
  $ make -j3 ARCH=sh zImage

- When using a compressed kernel image, a real bootloader places ramdisk
  and other kernel parameters as predesignated locations in RAM.  Well, we
  don't have one of those yet :).  So instead, I've attached a file called
  page0.  It's purpose is to provide default parameters to start a serial
  console, and specify the system RAM size (approx. 16M).

- Whether you have ethernet (BBA) or serial cable, the best tool for
  uploading is Andrew K.'s dcload.  Because both versions have the same
  name and take the same arguments, the following commands apply to both
  sets of tools:

  $ dc-tool -a 0x8c011000 -u page0
  # This loads the kernel parameters
  $ dc-tool -n -a 0x8c220000 -x arch/sh/boot/zImage
  # And this loads the compressed kernel image and executes it.

  Note: if you use the serial version of dcload then specify the -p option
  to see the kernel boot messages.  If you have a combination of
  ethernet+serial, specify the -n option to dcload while your terminal is
  listening on your COM port.  And if you only have ethernet, well, you
  won't get anything :)

  For those who don't have either, here's the dmesg output:

Linux version 2.4.0 (mrbrown@alphaflight) (gcc version 3.1 20010220 (experimental)) #1 Wed Feb 21 09:31:05 CST 2001
On node 0 totalpages: 4080
zone(0): 4080 pages.
zone(1): 0 pages.
zone(2): 0 pages.
Kernel command line: root=/dev/ram mem=16320k console=ttySC1,57600
CPU clock: 199.50MHz
Bus clock: 99.75MHz
Module clock: 49.87MHz
Interval = 124692
Calibrating delay loop... 199.06 BogoMIPS
Memory: 15404k/16320k available (463k kernel code, 916k reserved, 17k data, 24k init)
Dentry-cache hash table entries: 2048 (order: 2, 16384 bytes)
Buffer-cache hash table entries: 1024 (order: 0, 4096 bytes)
Page-cache hash table entries: 4096 (order: 2, 16384 bytes)
Inode-cache hash table entries: 1024 (order: 1, 8192 bytes)
CPU: SH7750
POSIX conformance testing by UNIFIX
Linux NET4.0 for Linux 2.4
Based upon Swansea University Computer Society NET3.039
Initializing PowerVR2DC v1.1 at 0xa05f0000 (interrupts on IRQ 9, 96 total)
Starting kswapd v1.8
block: queued sectors max/low 10176kB/3392kB, 64 slots per queue
RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
SuperH SCI(F) driver initialized
ttySC0 at 0xffe00000 is a SCI
ttySC1 at 0xffe80000 is a SCIF
VFS: Cannot open root device "ram" or 01:00
Please append a correct "root=" boot option
Kernel panic: VFS: Unable to mount root fs on 01:00


Good night! :)

M. R.