From: Murray Jensen <Murray.Jensen@cmst.csiro.au>
To: Dan Malek <dan@mvista.com>
Cc: Konstantin Sabodash <konstantin.sabodash@fnc.fujitsu.com>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: SCC2 as console on 8260
Date: Tue, 06 Feb 2001 16:28:42 +1100 [thread overview]
Message-ID: <19367.981437322@msa.cmst.csiro.au> (raw)
In-Reply-To: Message from Dan Malek <dan@mvista.com> of "Fri, 02 Feb 2001 11:22:55 CDT." <3A7ADEDF.FC5008D3@mvista.com>
[-- Attachment #1: Type: text/plain, Size: 1204 bytes --]
On Fri, 02 Feb 2001 11:22:55 -0500, Dan Malek <dan@mvista.com> writes:
>Konstantin Sabodash wrote:
>> I set in "arch/ppc/8260_io/uart.c"
>> #define CONFIG_SERIAL_CONSOLE_PORT 2
>> Is it enough to to make SCC2 main console?
>
>No. The current 8260 uart.c driver is in pretty bad shape. I started
>making some changes to support exactly what you are asking for, but
>didn't yet finish.
>
> -- Dan
Maybe this will help. Here are the changes I had to make to the 8260 uart.c
driver for our custom board (Hymod). As well as console working properly on
the SCC port (I use SCC1, but should work on SCC2), I have added support for
KGDB on any serial port (I use KGDB on SCC2). Everything appears to be
running well. The code is still a mess (I tried to keep the changes to a
minimum), but it works for SCC now (at least for me :-). Cheers!
Murray...
PS: I figured I'd post the diffs here because they were only 8K compressed.
Is this too big for this list?
--
Murray Jensen, CSIRO Manufacturing Sci & Tech, Phone: +61 3 9662 7763
Locked Bag No. 9, Preston, Vic, 3072, Australia. Fax: +61 3 9662 7853
Internet: Murray.Jensen@cmst.csiro.au (old address was mjj@mlb.dmt.csiro.au)
[-- Attachment #2: linuxppc-8260-uart-diffs.gz --]
[-- Type: application/x-gzip , Size: 7996 bytes --]
prev parent reply other threads:[~2001-02-06 5:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-01 1:52 SCC2 as console on 8260 Konstantin Sabodash
2001-02-02 16:22 ` Dan Malek
2001-02-06 5:28 ` Murray Jensen [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=19367.981437322@msa.cmst.csiro.au \
--to=murray.jensen@cmst.csiro.au \
--cc=dan@mvista.com \
--cc=konstantin.sabodash@fnc.fujitsu.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).