From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andy Fleming <afleming@freescale.com>
Cc: M Ptich <ptich@hotmail.com>, linuxppc-dev@ozlabs.org
Subject: Re: Booting without Uboot on 8548E
Date: Tue, 07 Nov 2006 08:38:10 +1100 [thread overview]
Message-ID: <1162849091.28571.348.camel@localhost.localdomain> (raw)
In-Reply-To: <C508D5D4-125D-47FD-81D2-2DE6545A240F@freescale.com>
> But moving to arch/powerpc (while a good idea) is not going to solve
> your problems. There are bound to be a large number of things the
> kernel expects to have done for it by the firmware. In arch/powerpc,
> the 8548 kernel expects PCI to be set up, for instance (We plan to
> fix that, but it involves porting some code that only exists in arch/
> ppc).
I hope you don't mean porting pci-auto over :)
While It was good to have back then, we should really fix out PCI layer
to properly assign unassigned devices itself.
There is much work to do to cleanup ppc32, ppc64 and core PCI so they
can deal with all the various setups around, but it's probably a
worthwhile goal.
Ben.
next prev parent reply other threads:[~2006-11-06 21:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-04 8:52 Booting without Uboot on 8548E M Ptich
2006-11-04 9:13 ` Benjamin Herrenschmidt
2006-11-04 9:19 ` Benjamin Herrenschmidt
2006-11-10 8:14 ` Low memory not pageable on Freescale BookE M Ptich
2006-11-10 14:17 ` Kumar Gala
2006-11-10 21:59 ` KGDB support in 2.6.18 for 85xx platforms M Ptich
2006-11-15 0:38 ` Low memory not pageable on Freescale BookE M Ptich
2006-11-15 0:55 ` Kumar Gala
2006-11-04 9:28 ` Booting without Uboot on 8548E M Ptich
2006-11-06 21:16 ` Andy Fleming
2006-11-06 21:38 ` Benjamin Herrenschmidt [this message]
2006-11-04 17:22 ` Dan Malek
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=1162849091.28571.348.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=afleming@freescale.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=ptich@hotmail.com \
/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).