All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Rini <trini@kernel.crashing.org>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded Linux PPC list <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: 2.5 bk tree on 8xx board ... so close
Date: Tue, 29 Jun 2004 08:16:04 -0700	[thread overview]
Message-ID: <20040629151603.GG28128@smtp.west.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0406290546500.3272@localhost.localdomain>


On Tue, Jun 29, 2004 at 05:53:22AM -0400, Robert P. J. Day wrote:

> On Mon, 28 Jun 2004, Tom Rini wrote:
>
> >Which serial driver did you use?  For me 8xx_UART does not work, but
> >CPM_UART will (it's still not quite correct, I have to config in both
> >SMC1 and SCC1 to get SMC1 to work, but I'm burried under a bunch of
> >other stuff right now).
>
> i was, in fact, using 8xx_UART under the "MPC8xx CPM options" menu,
> but (pardon my confusion) i'm not aware of this CPM_UART option of
> which you speak (unless you're just paraphrasing).

Paraphrasing from memory, yes, sorry.

> if i deselect 8xx_UART, i'm assuming you're talking about going then
> to the menu selections:
>
>   Device Drivers
>     Character devices
>       Serial drivers
>
> and selecting the appropriate CONFIG_SERIAL_CPM* settings (_SCC1 and
> _SMC1)?  is that what you're referring to above?

Yes, that driver.  As I was saying, for some reason I haven't had time
to dig into, I have to select both SCC1 and SMC1 to get a console which
is on SMC1 working.  I've also found that enabling everything doesn't
horribly kill the board, so you could just try that for now.

--
Tom Rini
http://gate.crashing.org/~trini/

** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

      reply	other threads:[~2004-06-29 15:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-06-28 21:48 2.5 bk tree on 8xx board ... so close Robert P. J. Day
2004-06-28 23:31 ` Tom Rini
2004-06-29  9:53   ` Robert P. J. Day
2004-06-29 15:16     ` Tom Rini [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040629151603.GG28128@smtp.west.cox.net \
    --to=trini@kernel.crashing.org \
    --cc=linuxppc-embedded@lists.linuxppc.org \
    --cc=rpjday@mindspring.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.