From: Chris Zimman <chris@cryptoapps.com>
To: linuxppc-embedded@lists.linuxppc.org
Subject: 824x EUMB/UART move problem
Date: Tue, 4 Mar 2003 23:47:43 -0800 [thread overview]
Message-ID: <20030305074743.GA7814@mail.cryptoapps.com> (raw)
I'm looking at the EUMB move/UART problem right now. I don't see
that there's currently a clean way to deal with the fact that the EUMB
has moved and ppc_md.progress() is supposed to be called right after
the fact.
There are some obvious hacks that can be used to get around this, but
I'm looking for a clean method.
A callback could be added right after the EUMB move to update the base
addresses in serial_state. machdep_calls doesn't have a callback for
this right now. feature_call() could be used, but maybe this deserves
a callback of its own?
In mpc10x_common.c, something like:
/* Set base addr of the 8240/107 EUMB. */
early_write_config_dword(hose,
0,
PCI_DEVFN(0,0),
MPC10X_CFG_EUMBBAR,
phys_eumb_base);
if (ppc_md.eumb_uart_update)
ppc_md.eumb_uart_update(phys_eumb_base);
Has someone already dealt with this and I've somehow missed it?
--Chris
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-03-05 7:47 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20030305074743.GA7814@mail.cryptoapps.com \
--to=chris@cryptoapps.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).