From: Kumar Gala <kumar.gala@freescale.com>
To: "Jakob Viketoft" <jakob.viketoft@bitsim.se>
Cc: Linux PPC Embedded list <linuxppc-embedded@ozlabs.org>
Subject: Re: Adding machine types to the kernel tree...
Date: Mon, 7 Mar 2005 11:38:26 -0600 [thread overview]
Message-ID: <f3ed8c626354b5b1b51f355838e877eb@freescale.com> (raw)
In-Reply-To: <422C27FE.6000709@bitsim.se>
On Mar 7, 2005, at 4:07 AM, Jakob Viketoft wrote:
> Thanks for the comments!
>
> Andrew May wrote:
> > I think a huge first step would be to banish xparameters.h from all
> the
> > kernel code.
> > Our HW guys just seem to do the strangest things without checking.
> > So I have 2 spins of a board with 2 Virtex-II pro's each.
> > The 2 spins have a small refrence clock change and the 2 CPU's have
> > different IRQ mappings.
>
> I understand that there is numerous resentment against having this file
> in the kernel and I've been thinking of a solution without it. One such
> path would be serving the kernel with a OCP list of the devices used,
> but I'm unsure about the current status of OCP. Is this The Right Way
> to
> do it, or are OCP likely to be abandoned further along the 2.6 road?
If you are talking about 2.6, dont use OCP. Use the driver model and
platform devices. You can take a look at the arch/ppc/syslib/ppc_sys.c
and arch/ppc/platforms/85xx for examples.
- kumar
prev parent reply other threads:[~2005-03-07 17:38 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-03 11:46 Adding machine types to the kernel tree Jakob Viketoft
2005-03-03 18:50 ` Andrew May
2005-03-07 10:07 ` Jakob Viketoft
2005-03-07 12:27 ` Matt Porter
2005-03-08 18:01 ` Debian User
2005-03-14 9:43 ` Jakob Viketoft
2005-03-07 17:38 ` Kumar Gala [this message]
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=f3ed8c626354b5b1b51f355838e877eb@freescale.com \
--to=kumar.gala@freescale.com \
--cc=jakob.viketoft@bitsim.se \
--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).