LinuxPPC-Dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Yoshio Kashiwagi <kashiwagi@co-nss.co.jp>
To: Jaap de Jong <jaap.dejong@nedap.com>, linuxppc-embedded@ozlabs.org
Subject: RE: Linuxppc-embedded Digest, Vol 26, Issue 13
Date: Wed, 11 Oct 2006 00:50:57 +0900	[thread overview]
Message-ID: <JP2006101100505710.12505093@co-nss.co.jp> (raw)
In-Reply-To: <6915D0AE8B9047438F320B466AE30FDD798359@nvs0003.nedap.local>

Hi,

Thanks for your advice.
Although I was not verifying "Digest Vol26 Issue13", cache needed to be
turned OFF for operating 2.4 kernels by Avnet v4fx12mm.
However, when the same kernel was operated by ML403, even if it did not
turn OFF cache, it was operating normally.

Although the default reference design is not verified by v4fx12mm
recently, it is operating normally by 2.6.17.3 kernel and MPMC2 now.

However, if there is fault of infalte in 2.6.17 kernels, there is E-Mail
of Dave-San. Since the ramdisk capacity is 2MB that initrd is operating
normally in my kernel.

Best Regards,

Yoshio Kashiwagi - Nissin Systems

> Not sure...
> I have not been playing with 2.6 kernels but this looks a lot like
> the problems I found when trying to get the 2.4 kernel to work.
> Default for the avnet v4fx12 is to use the opb bus as raminterface.
> You should explicitly select the plb bus...
> 
> Jaap de Jong
> 
> ----------------------------------------------------------------------
> 
> Message: 1
> Date: Fri, 06 Oct 2006 10:33:53 +0900
> From: Yoshio Kashiwagi <kashiwagi@co-nss.co.jp>
> Subject: Re: Problem with initrd
> To: Glenn.G.Hart@us.westinghouse.com, linuxppc-embedded@ozlabs.org
> Message-ID: <JF2006100610335316.6823078@co-nss.co.jp>
> Content-Type: text/plain; charset=ISO-2022-JP
> 
> Glenn-San,
> 
> Are you developing by the custom-made hardware of V4FX12?
> If the 16-bit memory controller is used, it may have a problem in the
> memory controller.
> 
> Can you try the memory controller of http://www.xilinx.com/mpmc2?
> I confirmed that the 16-bit memory controller of MPMC2 worked 
correctly
> by Linux. Or I can send the ramdisk image for 2.6.17.3 kernel which I 
am
> using to you.
> 
> Yoshio kashiwagi - Nissin Systems
> 
__________________________________________
> Linuxppc-embedded mailing list
> Linuxppc-embedded@ozlabs.org
> https://ozlabs.org/mailman/listinfo/linuxppc-embedded
> 

      reply	other threads:[~2006-10-10 15:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-06 13:44 Linuxppc-embedded Digest, Vol 26, Issue 13 Jaap de Jong
2006-10-10 15:50 ` Yoshio Kashiwagi [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=JP2006101100505710.12505093@co-nss.co.jp \
    --to=kashiwagi@co-nss.co.jp \
    --cc=jaap.dejong@nedap.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox