AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070309174636.552b7084@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<warren.gale@onstor.com>
MAID:1
X-Sylpheed-Privacy-System:
X-Sylpheed-Sign:0
SCF:#mh/Mailbox/sent
RMID:#imap/andys@onstor.net@onstor-exch02.onstor.net/INBOX	0	BB375AF679D4A34E9CA8DFA650E2B04E02C1B66D@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 9 Mar 2007 17:46:59 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Warren Gale" <warren.gale@onstor.com>
Subject: Re: PROM load image comand
Message-ID: <20070309174659.5455bf01@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02C1B66D@onstor-exch02.onstor.net>
References: <20070309160519.0bbc46a5@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E02C1B66D@onstor-exch02.onstor.net>
Organization: Onstor
X-Mailer: Sylpheed-Claws 2.6.0 (GTK+ 2.8.20; x86_64-pc-linux-gnu)
Mime-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit

Dang it, it didn't work.  I'm guessing maybe they also ifdef'd out the
part that puts that address into the right place.  You can probably
find that spot by searching for that symbol.

Anyway, can you just tell me the address of the printf function?  I'll
just hack it in.

The prom did boot, btw.  I dig all the debugging spewage.

Cheers,

a



On Fri, 9 Mar 2007 17:08:21 -0800 "Warren Gale"
<warren.gale@onstor.com> wrote:

> 
> Ok..  Got one for you..
> It's on /n/users/warreng/bc_proms/4AndyS
>       File r9kfimg.bin24Andy
> Did have to NULL some of the fields.
> 
> Warren
> 
> 
> -----Original Message-----
> From: Andy Sharp 
> Sent: Friday, March 09, 2007 4:05 PM
> To: Warren Gale
> Subject: Re: PROM load image comand
> 
> No problemo, give me a call or I can try you at your desk.
> 
> Cheers,
> 
> a
> 
> On Fri, 9 Mar 2007 16:02:20 -0800 "Warren Gale"
> <warren.gale@onstor.com> wrote:
> 
> > 
> > Andy,
> >   Ok, I'm looking but it does not compute. (Sorry)
> > I can't find anything in the PROM code that has any mention of 
> > "PMON Vectors".  Since I don't have any docs on PMON, (that I know
> > of) do you have some thing that tells me a bit more on this?
> > 
> > Looks like there are some jump tables, is this what it's like?
> > I'm willing to try anything. (At least once) 
> > (I'm really just a diag guy..  single thread bit twiddling stuff)
> > Thanks,
> > Warren
> > 
> > -----Original Message-----
> > From: Andy Sharp 
> > Sent: Friday, March 09, 2007 3:32 PM
> > To: Brian Stark
> > Cc: Warren Gale
> > Subject: Re: PROM load image comand
> > 
> > Here is header file from the kernel:
> > 
> > struct callvectors {
> > 	int	(*open) (char*, int, int);
> > 	int	(*close) (int);
> > 	int	(*read) (int, void*, int);
> > 	int	(*write) (int, void*, int);
> > 	off_t	(*lseek) (int, off_t, int);
> > 	int	(*printf) (const char*, ...);
> > 	void	(*cacheflush) (void);
> > 	char*	(*gets) (char*);
> > 	union {
> > 		int	(*smpfork) (unsigned long cp, char *sp);
> > 		int	(*cpustart) (long, long, long, long);
> > 	} _s;
> > 	int	(*semlock) (int sem);
> > 	void	(*semunlock) (int sem);
> > };
> > 
> > 
> > The printf function is the only one I really need, the others you
> > could just leave as NULL.  Of course, the cpustart function would be
> > good to play with.
> > 
> > Cheers,
> > 
> > a
> > 
> > On Fri, 9 Mar 2007 15:28:08 -0800 "Brian Stark"
> > <brian.stark@onstor.com> wrote:
> > 
> > > Andy,
> > > 
> > > I think Warren understands what you're looking for with the PMON
> > > call vectors since you guys have talked about it, but I don't know
> > > if he's scoped the work yet.  It really depends on how soon you
> > > need something.
> > > 
> > > 
> > > Brian
> > > 
> > > 
> > > 
> > > > -----Original Message-----
> > > > From: Andy Sharp 
> > > > Sent: Friday, March 09, 2007 3:17 PM
> > > > To: Brian Stark
> > > > Cc: Warren Gale
> > > > Subject: Re: PROM load image comand
> > > > 
> > > > On Fri, 9 Mar 2007 15:09:49 -0800 "Brian Stark"
> > > > <brian.stark@onstor.com> wrote:
> > > > 
> > > > Ditto...
> > > > 
> > > > > See below...
> > > > > 
> > > > > 
> > > > > > -----Original Message-----
> > > > > > From: Andy Sharp
> > > > > > Sent: Friday, March 09, 2007 2:53 PM
> > > > > > To: Brian Stark
> > > > > > Cc: Warren Gale
> > > > > > Subject: Re: PROM load image comand
> > > > > > 
> > > > > > On Fri, 9 Mar 2007 14:40:23 -0800 "Brian Stark"
> > > > > > <brian.stark@onstor.com> wrote:
> > > > > > 
> > > > > > > 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.
> > > > > > 
> > > > > > So use the same int as the mpsc ports on the marvell.  
> > > > > > Interrupt sharing is not a problem.  As long as they're
> > > > > > "like" interrupts.
> > > > > 
> > > > > 
> > > > > This may be feasible since the interrupts are tri-stated 
> > > > when inactive 
> > > > > (high).  I could wire up the 16552 interrupt directly to 
> > > > the Marvell 
> > > > > interrupt output that's used for the BSD mpsc port, which 
> > > > looks to be 
> > > > > CPU_INT0_L from the Marvell.  Then when this interrupt fires
> > > > > to the PMC, you'd have to go poll the Marvell cause register
> > > > > and then the 16552 port to see who generated it.  Is this
> > > > > cool?  If so, 
> > > > I'll look 
> > > > > to see what the rework looks like.
> > > > > 
> > > > > Of course, this is only needed if you can't get polling to
> > > > > work. Software fixes for hardware mistakes are so much fun!
> > > > 
> > > > I'll make you a deal: make me a PROM that gives me the 
> > > > standard PMON call vectors and I'll make the polling thing 
> > > > work.  Seriously.
> > > > 
> > > > Cheers,
> > > > 
> > > > a
> > > > 
