AF:
NF:0
PS:10
SRH:1
SFN:
DSR:
MID:<20070309145135.42ba9295@ripper.onstor.net>
CFG:
PT:0
S:andy.sharp@onstor.com
RQ:
SSV:onstor-exch02.onstor.net
NSV:
SSH:
R:<brian.stark@onstor.com>,<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	BB375AF679D4A34E9CA8DFA650E2B04E02C1B51F@onstor-exch02.onstor.net
X-Sylpheed-End-Special-Headers: 1
Date: Fri, 9 Mar 2007 14:53:06 -0800
From: Andrew Sharp <andy.sharp@onstor.com>
To: "Brian Stark" <brian.stark@onstor.com>
Cc: "Warren Gale" <warren.gale@onstor.com>
Subject: Re: PROM load image comand
Message-ID: <20070309145306.2c57fe0e@ripper.onstor.net>
In-Reply-To: <BB375AF679D4A34E9CA8DFA650E2B04E02C1B51F@onstor-exch02.onstor.net>
References: <BB375AF679D4A34E9CA8DFA650E2B04E02C1B4BC@onstor-exch02.onstor.net>
	<20070309141540.7b395cb2@ripper.onstor.net>
	<BB375AF679D4A34E9CA8DFA650E2B04E02C1B51F@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

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.

> 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.

Oh crap, I hope that doesn't mean a custom driver.  You know how I am
about writing code.

I probably can write a quick hack of an early console driver that does
some horribly patheticly simple output routine, and screw even doing an
input routine.  But first I will see if the standard driver is smart
enough to just figure out that no specified interrupt means that it has
to poll.  The regular driver might do that, but the early console
driver might not be that versatile.  It might require a polling thread,
and the kernel isn't sufficiently started enough to handle threads and
scheduling and such.  But you never know.

Thanks,

a
