linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Pradyumna Sampath" <pradyumna.sampath@gmail.com>
To: "Nicholas Hickman" <nhickman@dtechlabs.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: mpc8270 & Intel 82551ER on 2.6.17.14
Date: Fri, 29 Jun 2007 13:42:29 +0530	[thread overview]
Message-ID: <f87351060706290112o407f75e5h9dffd9939ab80ef9@mail.gmail.com> (raw)
In-Reply-To: <8140AAF341CC904BA92C3D6A5A1909782A2FA3@ditech-1.ditechllc.com>

Hi Nicholas,

On 6/29/07, Nicholas Hickman <nhickman@dtechlabs.com> wrote:
>
>
> I am having trouble getting two 82551ER Ethernet controllers running in
> Linux.  I am able to scan the PCI bus and see the devices and I was even
> able to program the EEPROM from U-boot.
>
> In the kernel I mapped the IRQ's through /arch/ppc/m82xx_pci.c.  I've been
> using the e100 drive that comes with the 2.6.17.14 kernel and have also
> tried the driver directly from Intel.  Both give the same results.  The PCI
> scan shows the correct output for how the device should be configured.
<snip..>

I have the same, exact same problem. But there are some of the
differences with the setup though. I have an MPC5200B and the other
difference is that I have a 2.6.21-rt3. However its the same ethernet
controller.

I am trying out a few things here, some of them being complete
guesses. But if I hit something, I will let this list know. Anyone
else had similar issues ? Request you to please holler.

regards
prady
-- 
htp://prady.livejournal.com

  reply	other threads:[~2007-06-29  8:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-28 22:53 mpc8270 & Intel 82551ER on 2.6.17.14 Nicholas Hickman
2007-06-29  8:12 ` Pradyumna Sampath [this message]
2007-07-02 18:41   ` Nicholas Hickman
  -- strict thread matches above, loose matches on Subject: below --
2007-06-29 16:48 Muruga Ganapathy
2007-06-29 16:54 ` Nicholas Hickman

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=f87351060706290112o407f75e5h9dffd9939ab80ef9@mail.gmail.com \
    --to=pradyumna.sampath@gmail.com \
    --cc=linuxppc-embedded@ozlabs.org \
    --cc=nhickman@dtechlabs.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).