From: Tom Rini <trini@kernel.crashing.org>
To: Dan Malek <dan@embeddededge.com>
Cc: alebas@televes.com, linuxppc-embedded@ozlabs.org
Subject: Re: Kernel 2.6.10 running on mpc8272ads
Date: Wed, 12 Jan 2005 07:19:02 -0700 [thread overview]
Message-ID: <20050112141902.GQ3391@smtp.west.cox.net> (raw)
In-Reply-To: <71A72D18-5F4C-11D9-A045-003065F9B7DC@embeddededge.com>
On Wed, Jan 05, 2005 at 02:03:11PM -0500, Dan Malek wrote:
>
> On Jan 5, 2005, at 12:48 PM, Tom Rini wrote:
>
> >Indeed. While I had a PQ2FADS for a bit, I had to do that as well.
> >Kumar, what/why is that needed exactly? Did I screw up in re-working
> >the 82xx init stuff and it needs to happen a bit later in boot?
>
> I don't understand the what/why question, but that has never stopped
> me from providing answers in the past :-)
Ha!
> So, In 2.6, and I think in some of the 2.4 cpm2 stuff, we no longer
> automatically map any of the hardware IO resources for common
> access like I used to do in the past. If you want to access the
> BCSR, you need to make sure it is ioremap()'ed in your driver before
> you make the access. Was that the question, or was it that
> the BCSR should have been set someplace outside of the
> driver for the serial port to work?
Actually, I did break it. When I re-worked the hooks around
platform_init/ppc_md.setup_arch, I added a call-out from platform_init()
but not from m82xx_setup_arch(), when I really needed one. I'll follow
up with a patch momentarily.
--
Tom Rini
http://gate.crashing.org/~trini/
next prev parent reply other threads:[~2005-01-12 14:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-09 9:42 Kernel 2.6.10 running on mpc8272ads alebas
2005-01-05 17:48 ` Tom Rini
2005-01-05 19:03 ` Dan Malek
2005-01-12 14:19 ` Tom Rini [this message]
2005-01-12 14:22 ` [PATCH 2.6.10] ppc32: Fix mpc8272ads Tom Rini
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=20050112141902.GQ3391@smtp.west.cox.net \
--to=trini@kernel.crashing.org \
--cc=alebas@televes.com \
--cc=dan@embeddededge.com \
--cc=linuxppc-embedded@ozlabs.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).