From: Carlo Pisani <carlojpisani@gmail.com>
To: benh@kernel.crashing.org, paulus@samba.org, mpe@ellerman.id.au,
linuxppc-dev@lists.ozlabs.org, alistair@popple.id.au,
mporter@kernel.crashing.org, sfr@canb.auug.org.au,
michael@ellerman.id.au, david@gibson.dropbear.id.au,
agust@denx.de, scottwood@freescale.com,
patchwork.ozlabs@gmail.com
Subject: Linux PowerPC, PPC4xx
Date: Wed, 16 Oct 2019 15:19:24 +0200 [thread overview]
Message-ID: <CA+QBN9Cxgwhga4dArM8MiHMYjT_Ab1YBVNnL6vAPf-euH03erw@mail.gmail.com> (raw)
hi
I am a student, I represent a group of friends running a couple of
opensource projects(1), and we are lost with this(2) problem.
I wrote here(2) a couple of years ago, we are still working with kernel
4.11.0 and there is broken support for initializing the PCI.
The PCI initialization of the PPC405GP seems wrong and every
kernel >= 2.6.26 is not able to correctly address the PDC20265
an interesting note is:
kernel 2.6.26 can be compiled with arch=ppc and arch=powerpc
when compiled with arch=ppc the promise PDC20265 chip is correctly
managed; while when compiled with arch=powerpc the PDC20265 is not
correctly managed
any idea? advice? help? suggestion?
a good place to discuss it?
thanks
Carlo
(1) http://www.downthebunker.com/reloaded/space/viewforum.php?f=37
(2) https://bugzilla.kernel.org/show_bug.cgi?id=195933
next reply other threads:[~2019-10-16 13:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-16 13:19 Carlo Pisani [this message]
2019-10-17 2:11 ` Linux PowerPC, PPC4xx Benjamin Herrenschmidt
-- strict thread matches above, loose matches on Subject: below --
2019-10-16 13:09 Carlo Pisani
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=CA+QBN9Cxgwhga4dArM8MiHMYjT_Ab1YBVNnL6vAPf-euH03erw@mail.gmail.com \
--to=carlojpisani@gmail.com \
--cc=agust@denx.de \
--cc=alistair@popple.id.au \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=michael@ellerman.id.au \
--cc=mpe@ellerman.id.au \
--cc=mporter@kernel.crashing.org \
--cc=patchwork.ozlabs@gmail.com \
--cc=paulus@samba.org \
--cc=scottwood@freescale.com \
--cc=sfr@canb.auug.org.au \
/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).