X-MimeOLE: Produced By Microsoft Exchange V6.5
Received: by onstor-exch02.onstor.net 
	id <01C73B3B.6556421C@onstor-exch02.onstor.net>; Thu, 18 Jan 2007 12:01:09 -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: which console on bobcat sibyte
Date: Thu, 18 Jan 2007 12:01:08 -0800
Message-ID: <BB375AF679D4A34E9CA8DFA650E2B04E0222818F@onstor-exch02.onstor.net>
In-Reply-To: <20070118114006.773887c1@ripper.onstor.net>
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
Thread-Topic: which console on bobcat sibyte
thread-index: Acc7OHRo9Ln/sPqWSPuBOp4lVf3h2wAAeb6g
From: "Warren Gale" <warren.gale@onstor.com>
To: "Andy Sharp" <andy.sharp@onstor.com>

Well I looked into the prom branch  and it looks like to me that we go
directly to hardware.
I don't see anything that refers to CFE API's.

If you have a branch out the  SiBytes "console_driver" is
Set up to point to  "sb1250_uart()" and this manipulates registers
directly.
In dir "code/sm-serio"

I haven't looked at the CFE API's for consoles.
(don't think I've even heard of them :) ) sorry.

Maybe that is a little more help ?

Thanks
Warren
=20

-----Original Message-----
From: Andrew Sharp [mailto:andy.sharp@onstor.com]=20
Sent: Thursday, January 18, 2007 11:40 AM
To: Warren Gale
Subject: Re: which console on bobcat sibyte

No, that didn't help ~:^)

Basically, they end up using the same hardware, but the "CFE console"
just means that the kernel will use CFE APIs for console IO rather than
going directly to the hardware itself, which assumes that our prom code
is close enough to the CFE that it has this, that the console code is
there and we use it, etc.  I was wondering if you knew if our prom code
uses the standard CFE console IO code and so forth.  I figured you
would be the most likely person to know the answer to that.

As far as debugging goes, unless I get really excited, I won't be
trying to do kernel debugging on the bobcat sibyte.  As far knowing if
the eventual debugging setup will require 2 serial ports, I don't even
know.  I tend to think of kernel debuggers as a substitute for
thinking.  Hmm, maybe I should use a debugger at that.

Cheers,

a




On Thu, 18 Jan 2007 11:29:36 -0800 "Warren Gale"
<warren.gale@onstor.com> wrote:

>=20
> Hi Andy,
>     Not sure.   Cheep answer :)
>  The SiByte has a DUART.  Not sure what the CFE is using.. That maybe=20
> for a target board??
>=20
> Maybe I don't understand what CFE is doing.
> ( we use some CFE "based" code but it seems to be modified for our
> use)
>=20
> This brings up another Question.
> Debugging Linux kernel.
>  Typically in the past the BSD kernel was debugged using 2 serial
> ports. (Larry might know more on this, worked with Dan)
> I believe that in the FC console one needed to type in "debug", then
> a "gdb" session would be connected to the SSC console.
>=20
> So If you are doing this on a bobcat SiByte then you will need 2
> consoles.
> ie FP0 and FP1 consoles.
>=20
> Don't know if any of this helped.
>=20
> Thanks,
> Warren
>=20
> -----Original Message-----
> From: Andrew Sharp [mailto:andy.sharp@onstor.com]=20
> Sent: Thursday, January 18, 2007 11:09 AM
> To: Warren Gale
> Subject: which console on bobcat sibyte
>=20
> Hi Warren,
>=20
> Cheap question: which console option should I go for on the Bobcat
> sibyte?  The CFE console, or the duart (dual uart) console?  It looks
> like the two can't co-exist configuration-wise in the linux kernel, I
> have to pick one or the other.  I figured you would be the best person
> to ask.
>=20
> Cheers,
>=20
> a
