From: acmay@acmay.homeip.net
To: Stefan Roese <stefan.roese@esd-electronics.com>
Cc: Linuxppc-Embedded <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PPC405GPWalnutPciBusMaster
Date: Thu, 19 Apr 2001 08:05:45 -0700 [thread overview]
Message-ID: <20010419080545.C1111@sink.san.rr.com> (raw)
In-Reply-To: <EFEAIMDCOOOHIEPHDNFJOEFGCMAA.stefan.roese@esd-electronics.com>; from stefan.roese@esd-electronics.com on Thu, Apr 19, 2001 at 10:07:55AM +0200
On Thu, Apr 19, 2001 at 10:07:55AM +0200, Stefan Roese wrote:
>
> > On Thu, Apr 19, 2001 at 10:44:08AM +0900, Hideo Noda wrote:
> > > Has anyone tried PCI cards with BUS MASTER operations for Walnut
> > > PPC405GP?
> >
> > I have tried and failed. I have other things to work on right now
> > so I have just delayed looking into it anymore until the 2.0 CDK
> > comes out. I think that should be by the end of the month.
> >
> > I think there is a problem with the virt_to_phys matching the
> > PTM1/BAR1. In the preliminary 405gp docs that I have Fig 17-59
> > on page 17-62 give a good overview on how things need to be
> > setup on the chip, but I am not sure on what the values
> > need to be.
>
> Which bootloader/firmware are you using? The pci configuration should be
> done within the bootloader. If you are using PPCBoot, I am not shure if the
> configuration is correct regarding the busmaster setup (although I did the
> port based on the IBM OpenBios). The bus master functionality was never
> tested - sorry for that.
I am just using the OpenBios for now. We will be spinning our own board
within the year so I was going to delay looking into doing the PPCBoot
code until then. I was able to look at the PCI registers when the kernel
booted and they appeared to be OK. For the hell of it I tried to change them
in the kernel and it hung during boot. I did not see in the docs the constraints
on when I could change those registers. Is it possible to do it very early in
the Linux boot code?
Thanks
--
Andrew May
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-04-19 15:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-19 1:44 PPC405GPWalnutPciBusMaster Hideo Noda
2001-04-19 2:36 ` PPC405GPWalnutPciBusMaster andrew may
2001-04-19 8:07 ` AW: PPC405GPWalnutPciBusMaster Stefan Roese
2001-04-19 15:05 ` acmay [this message]
2001-05-14 10:44 ` PPC405GPWalnutPciBusMaster machael thailer
2001-05-16 5:58 ` PPC405GPWalnutPciBusMaster John Cagle
-- strict thread matches above, loose matches on Subject: below --
2001-04-19 15:06 PPC405GPWalnutPciBusMaster Cagle, John
[not found] <fc.106ccf27106ccf2715ebed273b9aca00.25700d@mutoh.co.jp>
2001-05-15 23:46 ` PPC405GPWalnutPciBusMaster Hideo Noda
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=20010419080545.C1111@sink.san.rr.com \
--to=acmay@acmay.homeip.net \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=stefan.roese@esd-electronics.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).