From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Wolfgang Grandegger" <wg@grandegger.com>
Cc: linuxppc-embedded <linuxppc-embedded@ozlabs.org>
Subject: Re: PCI on Lite5200/Icecube, known issues?
Date: Thu, 25 Oct 2007 10:24:46 -0600 [thread overview]
Message-ID: <fa686aa40710250924u155d5644u535fc17c56983473@mail.gmail.com> (raw)
In-Reply-To: <4720C27B.7020408@grandegger.com>
On 10/25/07, Wolfgang Grandegger <wg@grandegger.com> wrote:
> Wolfgang Grandegger wrote:
> > Grant Likely wrote:
> >> On 10/25/07, Wolfgang Grandegger <wg@grandegger.com> wrote:
> >>> Hello,
> >>>
> >>> The access to PCI memory space does not to work (I allways read 0xff) on
> >>> my Icecube-Eval-Board. Are there any known issues/bugs with using the
> >>> PCI on the Lite5200/Icecube board with 2.6.23? Has it been tested? I
> >>> realized, that CONFIG_PCI is not set in the default configuration.
> >> arch/ppc or arch/powerpc?
> >>
> >> I'm not a PCI expert, but I just fired up my Lite5200 with a couple of
> >> eth adapters plugged in and the devices are usable. This is a
> >> 2.6.24-rc1 arch/powerpc kernel.
> >
> > I'm using a 2.6.23 arch/powerpc kernel. And my eepro100 card does not
> > work either:
> >
> > e100: probe of 0000:00:18.0 failed with error -11
> >
> > It looks like that 2.6.23 needs some more patches.
>
> Indeed, it works with 2.6.24-rc1:
>
> e100: eth0: e100_probe: addr 0xa0000000, irq 16, MAC addr 00:0e:0c:74:8c:f2
Okay, when I get a chance I'll try 2.6.23 on my lite5200
Cheers,
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
grant.likely@secretlab.ca
(403) 399-0195
prev parent reply other threads:[~2007-10-25 16:24 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-25 14:20 PCI on Lite5200/Icecube, known issues? Wolfgang Grandegger
2007-10-25 14:45 ` Grant Likely
2007-10-25 15:11 ` Wolfgang Grandegger
2007-10-25 16:21 ` Wolfgang Grandegger
2007-10-25 16:24 ` Grant Likely [this message]
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=fa686aa40710250924u155d5644u535fc17c56983473@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wg@grandegger.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).