From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: "Frank Svendsbøe" <frank.svendsboe@gmail•com>
Cc: Scott Wood <scottwood@freescale•com>,
"linuxppc-dev@ozlabs•org" <linuxppc-dev@ozlabs•org>,
Daniel Ng <daniel.ng1234@gmail•com>,
Norbert van Bolhuis <nvbolhuis@aimvalley•nl>
Subject: Re: MPC8272- Porting HDLC driver from 2.6.14 to 2.6.27- "no_irq_chip" error
Date: Tue, 02 Jun 2009 10:48:34 +1000 [thread overview]
Message-ID: <1243903714.591.20.camel@pasglop> (raw)
In-Reply-To: <1ba63b520905301322n72fa165ds7e2eb3af4475f109@mail.gmail.com>
On Sat, 2009-05-30 at 22:22 +0200, Frank Svendsbøe wrote:
> Regarding doing manual mapping: Is there another way to retrieve the
> host controller
> from a driver module without modifying kernel source? In case not, do
> you think
> exporting the mpc8xx_pic_host symbol is a better solution?
>
> Anyway, now that I'm beginning to understand dts I guess I might as
> well just do it properly.
Well, precisely :-) The DTS allows to contain the linkage to the PIC and
let the kernel resolve it all nicely for you.
Cheers,
Ben.
next prev parent reply other threads:[~2009-06-02 0:50 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-28 7:37 MPC8272- Porting HDLC driver from 2.6.14 to 2.6.27- "no_irq_chip" error Daniel Ng
2009-05-28 10:33 ` Norbert van Bolhuis
2009-05-28 12:33 ` Wolfram Sang
2009-05-29 0:46 ` Daniel Ng
2009-05-29 8:31 ` [PATCH] powerpc/cpm2: make cpm2_pic the default host Wolfram Sang
2009-05-29 10:56 ` MPC8272- Porting HDLC driver from 2.6.14 to 2.6.27- "no_irq_chip" error Frank Svendsbøe
2009-05-29 17:18 ` Scott Wood
2009-05-30 20:22 ` Frank Svendsbøe
2009-06-02 0:48 ` Benjamin Herrenschmidt [this message]
2009-06-02 0:47 ` Benjamin Herrenschmidt
2009-06-02 4:38 ` Wolfram Sang
2009-06-02 4:42 ` Benjamin Herrenschmidt
2009-06-02 0:46 ` Benjamin Herrenschmidt
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=1243903714.591.20.camel@pasglop \
--to=benh@kernel$(echo .)crashing.org \
--cc=daniel.ng1234@gmail$(echo .)com \
--cc=frank.svendsboe@gmail$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
--cc=nvbolhuis@aimvalley$(echo .)nl \
--cc=scottwood@freescale$(echo .)com \
/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