From: Matt Porter <mporter@kernel.crashing.org>
To: Richard Danter <richard.danter@windriver.com>
Cc: Matt Porter <mporter@kernel.crashing.org>,
linuxppc-embedded@lists.linuxppc.org
Subject: Re: 750/107 CHRP question
Date: Thu, 31 Jul 2003 15:48:43 -0700 [thread overview]
Message-ID: <20030731154843.A8523@home.com> (raw)
In-Reply-To: <3F298CED.8010701@windriver.com>; from richard.danter@windriver.com on Thu, Jul 31, 2003 at 10:41:01PM +0100
On Thu, Jul 31, 2003 at 10:41:01PM +0100, Richard Danter wrote:
>
> Matt Porter wrote:
> > [Oh my !#$!@. I never thought I'd be replying to a Linux question
> > from WRS. I need to check for reports of natural disasters and
> > mass rioting. :)]
>
> LOL!!
>
> Yes, I work for WRS, but this is a little personal project just for the
> hell of it. I just happen to be using a WRS board and vICE to do the
> debugging.
Sure, we believe you. :)
> >>How do I map this correctly???
> >
> > In 2.4, you can use early_serial_setup() or io_block_map(). It is
> > highly recommended to use early_serial_setup(). There are many
> > examples of this (spruce, lopec, etc.)
>
> Thanks, I'll take a look at that.
>
> I'm sure this bit is easy, the tricky stuff will probably be when I
> start playing with PCI...
That'll be easy too. Look at how the MPC10x-based ports are using
the mpc10x_common.c code.
Regards,
--
Matt Porter
mporter@kernel.crashing.org
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-07-31 22:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-31 16:54 750/107 CHRP question Richard Danter
2003-07-31 21:07 ` Matt Porter
2003-07-31 21:41 ` Richard Danter
2003-07-31 22:48 ` Matt Porter [this message]
2003-07-31 23:32 ` Wolfgang Denk
2003-08-01 8:16 ` Richard Danter
2003-08-01 4:34 ` Sangmoon Kim
[not found] <20030801082845.A38F6C602D@atlas.denx.de>
2003-08-01 9:02 ` Richard Danter
2003-08-01 12:17 ` Wolfgang Denk
2003-08-01 12:24 ` Richard Danter
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=20030731154843.A8523@home.com \
--to=mporter@kernel.crashing.org \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=richard.danter@windriver.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.