From: Josh Boyer <jwboyer@linux.vnet.ibm.com>
To: Roderick Colenbrander <thunderbird2k@gmail.com>
Cc: linux-fbdev-devel@lists.sourceforge.net, adaplas@gmail.com,
Suneel <suneelg@xilinx.com>,
linuxppc-dev@ozlabs.org,
Suneel <"[mailto:suneel.garapati@xilinx.com]"@xilinx.com>,
akonovalov@ru.mvista.com, John Linn <john.linn@xilinx.com>
Subject: Re: [PATCH] Xilinx : Framebuffer Driver: Add PLB support (non-DCR)
Date: Thu, 9 Apr 2009 10:33:19 -0400 [thread overview]
Message-ID: <20090409143319.GG18304@zod.rchland.ibm.com> (raw)
In-Reply-To: <c8485d470904090706t4fd2893tdeaf3710b19bd0f1@mail.gmail.com>
On Thu, Apr 09, 2009 at 04:06:56PM +0200, Roderick Colenbrander wrote:
>On Thu, Apr 9, 2009 at 2:46 PM, Josh Boyer <jwboyer@linux.vnet.ibm.com>wrote:
>> > #define NUM_REGS 2
>> > #define REG_FB_ADDR 0
>> >@@ -112,6 +123,11 @@ struct xilinxfb_drvdata {
>> >
>> > struct fb_info info; /* FB driver info record */
>> >
>> >+ u32 regs_phys; /* phys. address of the control
>> >+ registers */
>>
>> Is this driver usable on the 440 based Xilinx devices? If so, is it
>> possible
>> to have the physical address of the registers above 4GiB, so is common with
>> almost all the I/O on the other 440 boards?
>>
>>
>The driver works fine on 440 based Xilinx boards (the ML510 I use has a 440
>core). It might be nice to move physical addresses above 4GB for devices but
>in all Xilinx tools and reference designs addresses below 4GB are used for
>periperhals and I think even below 2GB (or even below 1GB). It depends on
>the design.
Right. The "depends on the design" part is what I'm worried about. Perhaps
using resource_size_t here is more appropriate, given that designs can change
and put the regs above 4GiB. That way you can set the Kconfig option
appropriately for both cases.
josh
next prev parent reply other threads:[~2009-04-09 14:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-08 21:11 [PATCH] Xilinx : Framebuffer Driver: Add PLB support (non-DCR) John Linn
2009-04-09 1:51 ` Stephen Rothwell
2009-04-09 14:16 ` John Linn
2009-04-09 14:30 ` Grant Likely
2009-04-09 15:36 ` Dale Farnsworth
2009-04-09 15:38 ` John Linn
2009-04-09 12:46 ` Josh Boyer
2009-04-09 14:06 ` Roderick Colenbrander
2009-04-09 14:33 ` Josh Boyer [this message]
2009-04-09 14:34 ` Grant Likely
2009-04-09 14:36 ` John Linn
2009-04-09 14:34 ` John Linn
2009-04-09 14:41 ` John Linn
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=20090409143319.GG18304@zod.rchland.ibm.com \
--to=jwboyer@linux.vnet.ibm.com \
--cc="[mailto:suneel.garapati@xilinx.com]"@xilinx.com \
--cc=adaplas@gmail.com \
--cc=akonovalov@ru.mvista.com \
--cc=john.linn@xilinx.com \
--cc=linux-fbdev-devel@lists.sourceforge.net \
--cc=linuxppc-dev@ozlabs.org \
--cc=suneelg@xilinx.com \
--cc=thunderbird2k@gmail.com \
/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