interfacing PXA255 with peripherals

From: banu (banu1118_at_hotmail.com)
Date: 08/11/03 

Date: 11 Aug 2003 04:26:45 -0700

hi,

                   iam working on project which requires both ehternet
controller and can controller, to be intefaced to the PXA255
processor.

                          and i thought of this proceedure for
interfacing.

1. memory map the can controller and ethernet controller to the pxa255
through using chip select signals of static memory or VLIO.

2. memory decoding to be implemented in order to select the right
controller.

                                   is that the right way to implement
interfacing of both controllers to the pxa255.

                                   does we require pcmcia controller
to implement pcmcia socket? i think pcmcia controller is in built in
processor

                                 please , provide me valuable
suggesstions .

thanks in advance,

with regards,
bhanu prakash.k
india.

Relevant Pages

  • [-mm PATCH 10/10] Memory controller add documentation
    ... Differentiate between RSS and Page Cache - Paul Menage ... The infrastructure allows easy addition of other types of memory to control ... +c. Provides *zero overhead* for non memory controller users ... a container on hitting a limit, ...
    (Linux-Kernel)
  • [PATCH 20/33] memory controller add documentation
    ... Enable control of both RSS and Page Cache pages ... The infrastructure allows easy addition of other types of memory to control ... +c. Provides *zero overhead* for non memory controller users ... a cgroup on hitting a limit, ...
    (Linux-Kernel)
  • Re: Sol-20 Helios problem
    ... you to 48k of memory. ... test and a tarbell disk controller boot command. ... solution than the Northstar controller. ...
    (comp.os.cpm)
  • PROBLEM: Serial error
    ... Latency: 64 ... Memory behind bridge: fda00000-feafffff ... 00:1f.1 IDE interface: Intel Corporation 82801BA IDE U100 Controller ...
    (Linux-Kernel)
  • Re: CLOS object clean-up
    ... The destructor is called when the AI controlled NPC ... and therefore causes the mesh (elsewhere in memory) to ragdoll. ... Your best bet is to actually model the ``death'' of the AI controller ... And then you add a garbage collector to C++ ...
    (comp.lang.lisp)