All of lore.kernel.org
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Arnd Bergmann <arnd@arndb.de>
Cc: linuxppc-dev@ozlabs.org, Paul Mackerras <paulus@samba.org>,
	Guennadi Liakhovetski <g.liakhovetski@gmx.de>
Subject: Re: [PATCH] linkstation / kurobox support
Date: Sat, 02 Dec 2006 22:19:51 +1100	[thread overview]
Message-ID: <1165058392.22108.34.camel@localhost.localdomain> (raw)
In-Reply-To: <200612021156.37067.arnd@arndb.de>

On Sat, 2006-12-02 at 11:56 +0100, Arnd Bergmann wrote:
> > +
> > +       /* Interpret the "ranges" property */
> > +       /* This also maps the I/O region and sets isa_io/mem_base */
> > +       pci_process_bridge_OF_ranges(hose, dev, 1);
> > +
> > +       return 0;
> > +}
> 
> Can't you use the new PCI probing from arch/powerpc/kernel/of_platform
> for this?

I wouldnt recomment it for 32 bits just yet ...

> > +#ifdef CONFIG_BLK_DEV_INITRD
> > +       if (initrd_start)
> > +               ROOT_DEV = Root_RAM0;
> > +       else
> > +#endif
> > +#ifdef CONFIG_ROOT_NFS
> > +               ROOT_DEV = Root_NFS;
> > +#else
> > +               ROOT_DEV = Root_HDA1;
> > +#endif
> > +
> 
> This looks wrong. Didn't the same code come up recently in a review for
> another platform? What was the conclusion?

It's a copy paste that we inhertit from the big bang...  Should probably
go...

Note that PowerMac does have a proper root autodetect feature though
it's not fascionable to have such a thing nowadays and the only reason
it's still in is because it mostly stays under the radar :-)

So basically... yeah, the #ifdef sucks, but I don't mind that much...

Ben

  reply	other threads:[~2006-12-02 11:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-01 21:53 [PATCH] linkstation / kurobox support Guennadi Liakhovetski
2006-12-02 10:56 ` Arnd Bergmann
2006-12-02 11:19   ` Benjamin Herrenschmidt [this message]
2006-12-02 11:32     ` Benjamin Herrenschmidt
2006-12-02 12:32     ` Guennadi Liakhovetski
2007-01-28 22:31     ` Guennadi Liakhovetski
2007-02-08 21:47       ` Kumar Gala

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=1165058392.22108.34.camel@localhost.localdomain \
    --to=benh@kernel.crashing.org \
    --cc=arnd@arndb.de \
    --cc=g.liakhovetski@gmx.de \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=paulus@samba.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.