X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C74644.1B1E7E7E@onstor-exch02.onstor.net>; Thu, 1 Feb 2007 13:01:13 -0800
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: a baby's first words
Date: Thu, 1 Feb 2007 13:01:13 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02444B19@onstor-exch02.onstor.net>
In-Reply-To: <20070201123223.3e056322@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: a baby's first words
Thread-Index: AcdGQBQfXFk/xusgSSCdQcvReoT3vQAA7G9A
References: <20070201123223.3e056322@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	<dl-cougar>

Andy,

Fantastic progress!  You're gonna need a Cougar motherboard soon!

I agree that you're probably hitting the UART errata.  Put the
workaround in, and this will hopefully clear it up.


Brian


> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@onstor.com]=20
> Sent: Thursday, February 01, 2007 12:32 PM
> To: dl-cougar
> Subject: a baby's first words
>=20
> First non-garbled output from Linux on bobcat TXRX:
>=20
> eth0: enabling TCP rcv checksum
> eth0: SiByte Ethernet at 0x10064000, address: 40:00:00:00:01:00
> eth1: enabling TCP rcv checksum
> eth1: SiByte Ethernet at 0x10065000, address: 40:00:00:00:01:01
> eth2: enabling TCP rcv checksum
> eth2: SiByte Ethernet at 0x10066000, address:=20
> 40:00:00:00:01:02 Uniform Multi-Platform E-IDE driver=20
> Revision: 7.00alpha2
> ide: Assuming 33MHz system bus speed for PIO modes; override=20
> with idebus=3Dxx TCP cubic registered
> NET: Registered protocol family 1
> NET: Registered protocol family 17
> Root-NFS: No NFS server available, giving up.
> Time: MIPS clocksource has been installed.
> VFS: Unable to mount root fs via NFS, trying floppy.
> No filesystem could mount root, tried:
> Kernel panic - not syncing: VFS: Unable to mount root fs on=20
> unknown-block(2,0)
>=20
> There is a lot that comes out before that, but it's garbled. =20
> I think maybe the sibyte errata 1956 WAR code for the DUART=20
> bug that is in the kernel might be hurtin' -- it's a little=20
> bit different than the way it was done in our code.  I'll=20
> probably try that next.
>=20
> I had to disable SMP to get this to come out ungarbled, I=20
> don't know why that would have anything to do with it.  I had=20
> to write a little bit of code in the memory managment section=20
> of the sibyte specific code to get the kernel to compile (and=20
> work) in non-SMP mode -- I guess no one ever tries to use a=20
> sibyte in uni-processor mode??  Seems a little odd.
>=20
> Cheers,
>=20
> a
>=20
