From: "Xiaogeng (Shawn) Jin" <xjin@redswitch.com>
To: James Don <JDon@spacebridge.com>
Cc: "'linuxppc-embedded@lists.linuxppc.org'"
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: Configure 8xx_io in 2.4.21-pre3
Date: Tue, 14 Jan 2003 09:59:09 -0800 [thread overview]
Message-ID: <3E244FED.8020602@redswitch.com> (raw)
In-Reply-To: <DB0585C9F6F9D411BE8F00D0B7896A4CC06064@SNCMAIL>
Hi Jim,
Thank you for your suggestions. I had a working 2.4.4 (released by DENX)
kernel on my board, which has more stuff related to 8xx_io than
2.4.21-pre3. I don't know if those DENX-added stuff are necessary to
enable 8xx CPM or if the 8xx_io code in 2.4.21 is sufficient to make 8xx
CPM working. Probably I need to compare the code in these two versions
line by line.
- Shawn.
> 1.) I recommend start with UART only build of the kernel first
>
> 2.) Did you check that your PA,PB,PC, and PD pins are set up properly ...
>
> I my custom board had pins moved for things like enet on SCC ? However
> normally I believe SMC1 only can be on one pair of pins for a UART ...
> another
>
> 3.) Another thing to look at is your BRG clock for your board ... in my
> kernel I found mvista didn't look at the some parts of the hardware reset
> word that divide down my 80 Mhz reference intenerally before it goes to the
> brg ... I was really surprised this code wasn't there ...
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-01-14 17:59 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-14 16:06 Configure 8xx_io in 2.4.21-pre3 James Don
2003-01-14 17:59 ` Xiaogeng (Shawn) Jin [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-01-14 18:02 James Don
2003-01-14 5:07 Xiaogeng (Shawn) Jin
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=3E244FED.8020602@redswitch.com \
--to=xjin@redswitch.com \
--cc=JDon@spacebridge.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).