> No, because as I said, res->start is relative to the start of IO-space.
> The in/out functions add isa_io_base to the address.
>
Hi Scott,
please allow me to insist a little bit more on this.
1. As far as the device tree is concerned, it is defined that the first 3
numbers in every line
Scott Wood <[EMAIL PROTECTED]> said:
> Alexandros Kostopoulos wrote:
> > I've noticed the following: In function pci_process_bridge_OF_ranges,
> > when parsing the ranges for MEM and I/O space, the res->start for mem
> > is correctly set to ranges[na+
Hi all,
I've noticed the following: In function pci_process_bridge_OF_ranges, when
parsing the ranges for MEM and I/O space, the res->start for mem is
correctly set to ranges[na+2], which is the cpu address in the ranges
property. However, in I/O related code, res->start is set to ranges[2],
On Wed, 08 Aug 2007 14:42:34 +0300, Alexandros Kostopoulos
<[EMAIL PROTECTED]> wrote:
> On Tue, 07 Aug 2007 18:20:12 +0300, Scott Wood <[EMAIL PROTECTED]>
> wrote:
>
>> Alexandros Kostopoulos wrote:
>>> Except from some macros arch/powerpc/include/asm/io.h
On Tue, 07 Aug 2007 18:20:12 +0300, Scott Wood <[EMAIL PROTECTED]>
wrote:
> Alexandros Kostopoulos wrote:
>> Except from some macros arch/powerpc/include/asm/io.h / mpc8260_pci9.h,
>> I can seem to find anywhere the code regarding PCI Erratum 9. The
>> define
;> On Fri, Aug 03, 2007 at 05:58:56PM +0300, Alexandros Kostopoulos wrote:
>>> Hi all,
>>> in the old arch/ppc tree, there was a function called
>>> pq2ads_setup_pci()
>>> that set up PCI regs for 8272xx, in m82xx_pci.c. I was wandering, where
>>&
Hi all,
in the old arch/ppc tree, there was a function called pq2ads_setup_pci()
that set up PCI regs for 8272xx, in m82xx_pci.c. I was wandering, where
are these registers configured now in arch/powerpc? I can't seem to find
these code now.
Also, I can see that now bus 0, dev 0 (which I thi
rote:
> On Fri, Jul 27, 2007 at 03:24:08PM +0300, Alexandros Kostopoulos wrote:
>> In your patch for the pq2fads support, the device tree seems to be
>> missing
>> a memory node, for which dtc complains loudly. Is this board tested to
>> boot with these patches (becaus
Hello Scott and all,
In your patch for the pq2fads support, the device tree seems to be missing
a memory node, for which dtc complains loudly. Is this board tested to
boot with these patches (because I'm now using this as a template for my
board - with your patchset applied to Paul's git)
t
01 +0300, Alexandros Kostopoulos
<[EMAIL PROTECTED]> wrote:
> Oops! I've just noticed in your previous mail that I need to apply the
> patches to Paul's tree...Sorry 'bout that... my mistake
>
> alex
>
>
> On Thu, 26 Jul 2007 13:42:46 +0300, Alexandr
Oops! I've just noticed in your previous mail that I need to apply the
patches to Paul's tree...Sorry 'bout that... my mistake
alex
On Thu, 26 Jul 2007 13:42:46 +0300, Alexandros Kostopoulos
<[EMAIL PROTECTED]> wrote:
> Hello Scott,
>
> Thanks for your resp
od <[EMAIL PROTECTED]>
wrote:
> On Wed, Jul 25, 2007 at 05:22:40PM +0300, Alexandros Kostopoulos wrote:
>> 1) When mdiobus_register() called from mii-bitbang.c
>> (fs_enet_mdio_probe()
>> function) attemps to do a device_register for the mdio bus, it actually
>>
Hi all,
I'm trying to make FCC ethernet work with my board, based on an MPC8275
processor. I'm using kernel 2.6.22.1
I have the following problems:
1) When mdiobus_register() called from mii-bitbang.c (fs_enet_mdio_probe()
function) attemps to do a device_register for the mdio bus, it actuall
Hm, it seems that, after all, cpm_uart works fine without any board
specific code whatsoever. Sorry about the fuss. My mistake
Regards
Alex
On Tue, 17 Jul 2007 14:55:30 +0300, Alexandros Kostopoulos
<[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I was wondering, since arch/power
Hi all,
I was wondering, since arch/powerpc is now based on device trees,
shouldn't the cpm_uart driver (or at least a branch of it for
arch/powerpc) be changed to use of_platform_bus_type instead of
platform_bus_type? In my opinion, cpm_uart driver should take all its
configuration (uart
Hello all,
I am trying to port kernel 2.6.22.1 to my own platform, which incorporates
an mpc8275 chip. I'm using platform code for mpc82xx_ads as a template (is
this right in the first place?). I have a couple of questions:
1. mpc82xx_ads.c uses init_scc_ioports function to initialize the scc
16 matches
Mail list logo
