linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
* 750/107 - PCI or Interrupt problem?
@ 2003-08-04 17:54 Richard Danter
  2003-08-05 11:03 ` 750/107 - PCI or Interrupt problem? - FIXED Richard Danter
  0 siblings, 1 reply; 2+ messages in thread
From: Richard Danter @ 2003-08-04 17:54 UTC (permalink / raw)
  To: linuxppc-embedded


Hi All,

I have made some progress in porting Linux 2.4.x to a wrPPMC7xx board.
Yipee!

But now I have hit another problem...

It seems the kernel finds the ethernet card plugged into one of the PCI
slots. All the diagnostics seem to work too. In fact, it even sends out
a BOOTP request, as I can see it logged on my server.

The problem is it does not seem to be getting the BOOTP reply. It
eventually times out. But I can see from my server that a reply is being
sent.

At the moment I think the problem is most likely in my <board>_pci.c
code or <board>_setup.c. I don't get any hardware interrupts (ie setting
a hardware breakpoint on 0x0500 does not stop the CPU) and I would have
expected that... or am I way off track here?? I am also unsure if I have
set up my pci_irq_table or <board>_openpic_initsenses structures correctly.

Any suggestions where I should be looking in the code??

Hopefully if this part works then I get an IP address and can mount my
NFS root filesystem...

Thanks
Rich


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: 750/107 - PCI or Interrupt problem? - FIXED
  2003-08-04 17:54 750/107 - PCI or Interrupt problem? Richard Danter
@ 2003-08-05 11:03 ` Richard Danter
  0 siblings, 0 replies; 2+ messages in thread
From: Richard Danter @ 2003-08-05 11:03 UTC (permalink / raw)
  To: linuxppc-embedded


Hi all,

FYI, fixed it - it was an incorrect IRQ number pci_irq_table. :)

Rich


Richard Danter wrote:
>
> Hi All,
>
> I have made some progress in porting Linux 2.4.x to a wrPPMC7xx board.
> Yipee!
>
> But now I have hit another problem...
>
> It seems the kernel finds the ethernet card plugged into one of the PCI
> slots. All the diagnostics seem to work too. In fact, it even sends out
> a BOOTP request, as I can see it logged on my server.
>
> The problem is it does not seem to be getting the BOOTP reply. It
> eventually times out. But I can see from my server that a reply is being
> sent.
>
> At the moment I think the problem is most likely in my <board>_pci.c
> code or <board>_setup.c. I don't get any hardware interrupts (ie setting
> a hardware breakpoint on 0x0500 does not stop the CPU) and I would have
> expected that... or am I way off track here?? I am also unsure if I have
> set up my pci_irq_table or <board>_openpic_initsenses structures correctly.
>
> Any suggestions where I should be looking in the code??
>
> Hopefully if this part works then I get an IP address and can mount my
> NFS root filesystem...
>
> Thanks
> Rich
>
>
>
>


--

Richard Danter
Product Specialist - Tools
EMEA Customer Support Team

Wind River UK Ltd.
Freephone: 00 800 4977 4977
e-mail: support-uk@windriver.com


** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-08-05 11:03 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-08-04 17:54 750/107 - PCI or Interrupt problem? Richard Danter
2003-08-05 11:03 ` 750/107 - PCI or Interrupt problem? - FIXED Richard Danter

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).