X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C7629B.ECE67E17@onstor-exch02.onstor.net>; Fri, 9 Mar 2007 15:40:23 -0700
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Content-class: urn:content-classes:message
Subject: RE: PROM load image comand
Date: Fri, 9 Mar 2007 15:40:23 -0700
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E02C1B51F@onstor-exch02.onstor.net>
In-Reply-To: <20070309141540.7b395cb2@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: PROM load image comand
Thread-Index: AcdimHinaaKKJQ2PRaORqBSf94qAuwAAEHGg
References: <BB375AF679D4A34E9CA8DFA650E2B04E02C1B4BC@onstor-exch02.onstor.net> <20070309141540.7b395cb2@ripper.onstor.net>
From: "Brian Stark" <brian.stark@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>,
	"Warren Gale" <warren.gale@onstor.com>

Crap, those damn interrupts get me every time.  The 16552 interrupts are
not hooked up to anything because all of the PMC interrupts were already
taken when the 16552 was added.  Same goes for the Marvell GPP pins that
could be wired up as interrupt inputs.

Can you poll the UART to see if characters have been received?  Maybe
this would work until the Marvell UART is going.

A word of caution on the RTC.  Because of the way the Marvell part
addresses devices on its device bus, the RTC is addressed on double-word
boundaries:

CPU address		RTC reg
1f00.0000		0
1f00.0008		1
1f00.0010		2
1f00.0018		3
...

So, you gotta do byte reads to double-word addresses.  I know this ain't
ideal, but blame the Marvell part.


Brian
=20

> -----Original Message-----
> From: Andy Sharp=20
> Sent: Friday, March 09, 2007 2:16 PM
> To: Warren Gale
> Cc: Brian Stark
> Subject: Re: PROM load image comand
>=20
> Hi Warren,
>=20
> No, I was looking for the command that would let me do an ELF=20
> load and boot of an arbitrary file, but it appears that the=20
> diskload command does not do ELF interpretation any more than=20
> the tftp 'load' command does.  Oh well.
>=20
> It seems I've gotten past my last problem.  I always find the=20
> problem and fix it right after whining like a little girl. =20
> Right now I'm trying to hook up the RTC and the serial=20
> anything, because the debug_vectors aren't being set up, or=20
> they aren't being passed into the kernel, so I can't use the=20
> PMON printf function for early console output.  Which would=20
> be *really* great if I could.  Any chance that you could make=20
> me a PROM with that little item fixed?
>=20
> I was going to ask what IRQ the 16552 serial ports are hooked=20
> up to, could you ask Brian that?  I'll just CC him on this. =20
> Max seems to think that they aren't hooked up to an interrupt=20
> which would be kind of a bummer.  But I still might be able=20
> to use them as an early console.
>=20
> Thanks,
>=20
> a
>=20
>=20
>=20
>  On Fri, 9 Mar 2007 14:04:51 -0800 "Warren Gale"
> <warren.gale@onstor.com> wrote:
>=20
> > Andy,
> >=20
> >    Are you looking for a PROM command that loads the image from the=20
> > net?
> >=20
> > Ie. "load -a 83000000 10.2.0.49 bsd.test"  This way you=20
> don't need to=20
> > have it on the Compact Flash.
> > I think 10.2.0.49 is the tftpboot server?
> >=20
> > =20
> >=20
> > You would then need to give it the "g  83000000"=20
> command.(Or where it
> > starts)
> >=20
> > I think Dan used an offset  like 83000040.. Since there were some=20
> > parameters in the first 0 - 40.
> >=20
> > =20
> >=20
> > Warren
> >=20
>=20
