linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Ron Sass" <rsass@uncc.edu>
Cc: Jean-Samuel Chenard <jsamch@macs.ece.mcgill.ca>,
	linuxppc-embedded@ozlabs.org
Subject: Re: ml310 kernel2.6 booting problems
Date: Fri, 18 Jan 2008 18:23:24 -0700	[thread overview]
Message-ID: <fa686aa40801181723r4ca29725s23f4acd9297e905@mail.gmail.com> (raw)
In-Reply-To: <200801190011.m0J0BCtr001286@rsass-homer.uncc.edu>

On 1/18/08, Ron Sass <rsass@uncc.edu> wrote:
> My question is this:  Would it make sense to have a Kernel
> configuration something like "VIRTEX_PCI" and a platforms
> "XILINX_ML4xx" / "XILINX_ML3xx" ... or create four platforms:
>
>   XILINX_ML300
>   XILINX_ML310
>   XILINX_ML40x
>   XILINX_ML410

The whole CONFIG_XILINX_ML*** stuff will be disappearing as part of
the migration from arch/ppc to arch/powerpc.  Instead, the board
configuration will be described using a device tree file (dts).  Feel
free to add stuff in your local tree, but be prepared to migrate your
drivers in the next 6 months or so.

Cheers,
g.

-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.

  parent reply	other threads:[~2008-01-19  1:23 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-18  2:49 ml310 kernel2.6 booting problems Jean-Samuel Chenard
2008-01-19  0:11 ` Ron Sass
2008-01-19  0:35   ` Stephen Neuendorffer
2008-01-19  1:21     ` Ron Sass
2008-01-19  1:23   ` Grant Likely [this message]
  -- strict thread matches above, loose matches on Subject: below --
2008-01-17 20:19 Joachim Meyer
2008-01-16 20:02 Joachim Meyer
2008-01-16 20:30 ` Grant Likely
2008-01-16 13:25 Joachim Meyer
2008-01-16 14:50 ` Grant Likely
2008-01-25 13:04   ` greenlean
2008-01-25 15:17     ` Grant Likely

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=fa686aa40801181723r4ca29725s23f4acd9297e905@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=jsamch@macs.ece.mcgill.ca \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=rsass@uncc.edu \
    /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).