All of lore.kernel.org
 help / color / mirror / Atom feed
From: stonepine <stonepine@126.com>
To: David Hawkins <dwh@ovro.caltech.edu>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: 11-16-05 2.6.14 on AMCC Yosemite boar d(PCI-IDE card boot error)
Date: Fri, 15 Sep 2006 01:52:59 +0800	[thread overview]
Message-ID: <450996FB.5050408@126.com> (raw)
In-Reply-To: <4508A606.90505@ovro.caltech.edu>

Hi Dave,
The problem was addressed with your help, and I do really appreciate your help.


David Hawkins wrote:

>Stephen Yee wrote:
>  
>
>>Hi All,
>>
>>I have tested and debuged the ELDK's kernel 2.6.14 with PDC20269 PCI-IDE
>>card, the system paniced when it run the 'ide_pci_setup_ports' funcation
>>[drivers/ide/setup_pci.c], the attached files included the entry log
>>messages, and ksysoops messages when the kernel paniced, and my kernel
>>configuration file and BDI2000 configuration file.
>>
>>would you please give some advice about this issue?
>>    
>>
>
>When I was testing this board, I received a machine check
>in earlier kernels due to;
>
>  The kernel header for the Yosemite board has an error that
>  incorrectly sets the base address for PCI I/O space. The define
>  for the 36-bit PCI I/O base address in the file
>  arch/ppc/platforms/4xx/yosemite.h needs to be set to
>
>#define YOSEMITE_PCI_IO_BASE 0x00000000e8000000ULL
>
>Check your kernel source, perhaps that is the issue.
>
>Stephan at Denx found and fixed this a while back (over 6 months
>ago). So when in doubt, use the latest-and-greatest kernel, eg.,
>use git and access the Denx repo.
>
>Dave
>
>
>
>
>  
>

  reply	other threads:[~2006-09-14 18:24 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-09-13  3:44 11-16-05 2.6.14 on AMCC Yosemite boar d(PCI-IDE card boot error) Stephen Yee
2006-09-13 20:11 ` Stephen Yee
2006-09-14  0:44   ` David Hawkins
2006-09-14 17:52     ` stonepine [this message]
2006-09-14 18:01       ` David Hawkins
2006-09-14  0:52   ` Wolfgang Denk
2006-09-20 15:55     ` Unable to mount jffs2 Mathews, Phil

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=450996FB.5050408@126.com \
    --to=stonepine@126.com \
    --cc=dwh@ovro.caltech.edu \
    --cc=linuxppc-embedded@ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.