From: "Steven A. Falco" <sfalco@harris.com>
To: Josh Boyer <jwboyer@gmail.com>
Cc: linuxppc-dev@ozlabs.org
Subject: Re: PPC440EPx on Sequoia: /proc/iomem acts weird
Date: Fri, 09 Nov 2007 13:46:20 -0500 [thread overview]
Message-ID: <4734AAFC.8080907@harris.com> (raw)
In-Reply-To: <20071109123522.072bc1d8@weaponx>
[-- Attachment #1: Type: text/plain, Size: 1166 bytes --]
I am using the Denx 2.6.32 kernel, which does have powerpc/sequoia.
Xenomai is a real-time kernel built on Adeos/Ipipe. I'll dig into it
further.
Steve
Josh Boyer wrote:
> On Fri, 09 Nov 2007 13:30:03 -0500
> "Steven A. Falco" <sfalco@harris.com> wrote:
>
>
>> If I cat /proc/iomem on a Sequoia board, it never stops printing. Here
>> are the first 10 lines:
>>
>> bash-3.00# head -10 /proc/iomem
>> e0000100-e000017f : usb
>> e0000100-e000017f : musbhsfc_udc
>> e0000300-e000038f : ehci_hcd
>> 180000000-18fffffff : /plb/pci@1eec00000
>> 1d0000000-1d0001fff : ndfc
>> 1d0000000-1d0001fff : ndfc
>> 1d0000000-1d0001fff : ndfc
>> 1d0000000-1d0001fff : ndfc
>> 1d0000000-1d0001fff : ndfc
>> 1d0000000-1d0001fff : ndfc
>>
>> Basically, the last line (regarding the nand flash) keeps repeating
>> "forever".
>>
>> Is anyone else seeing this behavior? My kernel is 2.6.23 with Xenomai
>> patched in.
>>
>
> Erm.. 2.6.23? There is no Sequoia support in arch/ppc or arch/powerpc
> for 2.6.23 in the official trees. What is Xenomai? You should
> probably talk to them.
>
> josh
>
>
[-- Attachment #2: Type: text/html, Size: 1626 bytes --]
next prev parent reply other threads:[~2007-11-09 18:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-09 18:30 PPC440EPx on Sequoia: /proc/iomem acts weird Steven A. Falco
2007-11-09 18:35 ` Josh Boyer
2007-11-09 18:46 ` Steven A. Falco [this message]
2007-11-10 13:03 ` Stefan Roese
2007-11-12 15:36 ` Steven A. Falco
2007-11-12 19:25 ` Steven A. Falco
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=4734AAFC.8080907@harris.com \
--to=sfalco@harris.com \
--cc=jwboyer@gmail.com \
--cc=linuxppc-dev@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;
as well as URLs for NNTP newsgroup(s).