From: akuster <akuster@dslextreme.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: First steps to OCP device model integration
Date: Fri, 09 Aug 2002 12:41:29 -0700 [thread overview]
Message-ID: <3D541AE9.40007@dslextreme.com> (raw)
In-Reply-To: 20020809042605.GC23642@zax
David Gibson wrote:
> THe patch below implements the first steps in transitioning the
> handling of 4xx OCP devices to the unfied device model (in 2.5). So
> far the code just registers an ocp bus and registers each device
> described in core_ocp on that bus. The next step is to convert the
> actual device drivers so that that they register with the unified
> driver tree rather than through the old ocp_register() mechanism.
>
> I will commit this shortly unless there are serious objections.
>
I object seriously.
Some of what you have might be useful.:) OCP is not just for 4xx. In
fact the name may need to change. I have been working on overhalling
this interface and testing the ideas before having a review of the
changes. I am on the hook to Paul and others to get this out in the
open to discuss and am not ready. So if you could just relax and wait I
would appriciate it. I would rather see the 2.5 kernel boot on a few
4xx boards
Armin
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-09 19:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-09 4:26 First steps to OCP device model integration David Gibson
2002-08-09 19:41 ` akuster [this message]
2002-08-10 8:15 ` Paul Mackerras
2002-08-11 21:51 ` akuster
2002-08-12 5:54 ` David Gibson
2002-08-13 15:34 ` Matt Porter
2002-08-16 18:39 ` 440 PCI adapter card DMA question Khai Trinh
2002-08-17 13:44 ` First steps to OCP device model integration David Gibson
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=3D541AE9.40007@dslextreme.com \
--to=akuster@dslextreme.com \
--cc=david@gibson.dropbear.id.au \
--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).