From: "machael thailer" <dony.he@huawei.com>
To: "Hideo Noda" <Hideo_Noda@mutoh.co.jp>,
<linuxppc-embedded@lists.linuxppc.org>
Subject: Re: PPC405GPWalnutPciBusMaster
Date: Mon, 14 May 2001 18:44:31 +0800 [thread overview]
Message-ID: <003601c0dc62$dbce25c0$8021690a@huawei.com> (raw)
In-Reply-To: 3ADE42E8.6552066B@mutoh.co.jp
Now I have the same problem as you meet before.
Have you find a good solutions?
Thank you very mcuh.
machael
>
> Hi,
>
> I am trying to install Intel eepro100 onto WalnutPPC405GP.
> Basic PCI settings seem good but no frame is transmitted.
> The environment is WalnutPPC305GP with HardHatLinux 2.4.2 from
> MonraVista.
>
> I can read or write eepro configuration registers and other control
> registers via PCI memory space.
> But Bus Master operations do not seem functional. I am confirmed that
> MASTER operation bit in eepro100 is enabled.
> I think some more settings are needed for PPC405GP built-in PCI control
> registers and/or Walnut board jumpers/dipswitches.
>
> Has anyone tried PCI cards with BUS MASTER operations for Walnut
> PPC405GP?
>
> Thanks in advance,
>
> Hideo
>
>
>
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-05-14 10:44 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 ` PPC405GPWalnutPciBusMaster acmay
2001-05-14 10:44 ` machael thailer [this message]
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='003601c0dc62$dbce25c0$8021690a@huawei.com' \
--to=dony.he@huawei.com \
--cc=Hideo_Noda@mutoh.co.jp \
--cc=linuxppc-embedded@lists.linuxppc.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 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).