From: Tom Rini <trini@kernel•crashing.org>
To: Yu Bo-BOYU1 <Bo.Yu@motorola•com>
Cc: linuxppc-embedded@lists•linuxppc.org
Subject: Re: question about open_pic and serial port
Date: Tue, 22 Oct 2002 09:33:32 -0700 [thread overview]
Message-ID: <20021022163332.GD669@opus.bloom.county> (raw)
In-Reply-To: <0B0A39652BB0D411BCCF00508B9512EC08AEB555@tx14exm05.ftw.mot.com>
On Tue, Oct 22, 2002 at 10:23:20AM -0500, Yu Bo-BOYU1 wrote:
>
> Does the current version Mvista preview 2.1 fully support serial mode of 107
> EPIC ?
> If so, what is interrupt number for serial mode interrupt 0 of mpc107 ? I
> reviewed
> the old messages on this list and the open_pic.c and there are some threads
> talking
> about the first 16 interrupts are reserved for 8259 only. Does that mean
> serial mode interrupt
> 0 match interrupt 16 on open_pic interrupt table ?
The way that things are handled internally are still to offset by 16,
when describing the interrupts. This is no longer true in the community
tree, but on both trees, all interrupts work, and yes, in the mvista
source, interrupt 16 in the table is OpenPIC interrupt 0.
> Plus, I changed the base address of boot/common/ns16550.c to drive the TI
> 752 uart.
> It appears working before kernel starts. Then it hang. It seems that the
> same file (ns16550.c)
> is not used after kernel starts. Which serial device driver is used after
> kernel starts ?
drivers/char/serial.c is used once the kernel starts. Is this for some
custom hardware? If you changed boot/common/ns16550.c directly, I
suspect you did something wrong, as it works with numerous base
addresses.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-10-22 16:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-22 15:23 question about open_pic and serial port Yu Bo-BOYU1
2002-10-22 16:33 ` 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=20021022163332.GD669@opus.bloom.county \
--to=trini@kernel$(echo .)crashing.org \
--cc=Bo.Yu@motorola$(echo .)com \
--cc=linuxppc-embedded@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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