linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: "Steven A. Falco" <sfalco@harris.com>
To: benh@kernel.crashing.org
Cc: linuxppc-dev@ozlabs.org
Subject: Re: Device tree question
Date: Mon, 11 Aug 2008 10:05:11 -0400	[thread overview]
Message-ID: <48A04717.4040102@harris.com> (raw)
In-Reply-To: <1218267682.24157.366.camel@pasglop>

[-- Attachment #1: Type: text/plain, Size: 1507 bytes --]

Benjamin Herrenschmidt wrote:
> On Thu, 2008-08-07 at 15:56 -0400, Steven A. Falco wrote:
>   
>> I have added a compact flash to the external bus of a Sequoia
>> (PPC440EPx) evaluation board.  It is wired to CS1, and U-boot is set to
>> configure CS1 to be at address 0xc1000000.  U-boot can access the
>> device, and reports the correct partition table, etc. so I believe the
>> hardware is ok.
>>
>> I've created a device-tree entry under the EBC0 section of the
>> sequoia.dts file:
>>
>>                 pata@1,0 {
>>                     compatible = "harris,hydra_temp-pata", "ata-generic";
>>                     bank-width = <2>;
>>                     reg = <1 0 20 1 80 20>;
>>                     reg-shift = <4>;
>>                     pio-mode = <4>;
>>                     interrupts = <27 4>;
>>                     interrupt-parent = <&UIC0>;
>>                 };
>>             };
>>
>> This seems to be correct, because if I turn on debug in prom_parse, I
>> see a translation that looks reasonable:
>>     
>
> Did you check that the resulting physical address was indeed where you
> device is supposed to be addressed ?
>
> Ben
>   

They were wrong - I misinterpreted the reg-shift to be like the "stride"
used by u-boot.  But u-boot uses it as a multiplier, and reg-shift is
truly a shift.  So, I changed the shift to "2", and now the addresses
are correct.  I'm still having problems, but I'll start a new thread,
because the new problem concerns interrupts.

    Thanks,
    Steve


[-- Attachment #2: Type: text/html, Size: 1911 bytes --]

  reply	other threads:[~2008-08-11 14:05 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-07 19:56 Device tree question Steven A. Falco
2008-08-09  7:41 ` Benjamin Herrenschmidt
2008-08-11 14:05   ` Steven A. Falco [this message]
  -- strict thread matches above, loose matches on Subject: below --
2007-09-18 20:43 device " Alan Bennett
2007-09-18 22:06 ` Scott Wood
2007-09-18 22:21   ` Alan Bennett
2007-09-18 22:36     ` Scott Wood
     [not found]       ` <bfa0697f0709181604i5758824foad67a86455f45d8e@mail.gmail.com>
     [not found]         ` <46F05BF7.6020906@freescale.com>
     [not found]           ` <bfa0697f0709190638r6894fab6gd31a5672a997e97@mail.gmail.com>
     [not found]             ` <46F16BD4.2000207@freescale.com>
     [not found]               ` <bfa0697f0709191420x5a6aed9dx499fe4a8cf6b1b2d@mail.gmail.com>
     [not found]                 ` <46F19326.7050507@freescale.com>
2007-09-20 17:53                   ` Alan Bennett
2007-09-20 18:31                     ` Scott Wood
2007-09-20 21:38                       ` Alan Bennett
2007-09-20 21:43                         ` Scott Wood

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=48A04717.4040102@harris.com \
    --to=sfalco@harris.com \
    --cc=benh@kernel.crashing.org \
    --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).