Linux ARM, Xscale -- Amba device porting


Amba device porting
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

To: <linux-arm@xxxxxxxxxxxxxxxxxxx>
Subject: Amba device porting
From: <roman.tereshonkov@xxxxxxxxx>
Date: Tue, 22 Dec 2009 13:33:54 +0100
Accept-language: en-US
Acceptlanguage: en-US
Thread-index: AcqDAwYUGxp0/5J2SP+IzeNyMM4xQA==
Thread-topic: Amba device porting

Hi,

I planned to port the omap3 SDTI (Serial Debug Trace Interface) driver to amba based interface.

SDTI memory map is two part composed:

0x54500000 0x5450FFFF 4KB SDTI module (configuration) - coresight based format.

0x54510000 0x545FFFFF 1984KB Reserved

0x54600000 0x546FFFFF 1MB SDTI module (window)

But amba interface seems to support only one memory region resource.

Is there any way to pass two memory regions?

Regards

Roman Tereshonkov

_______________________________________________
linux-arm mailing list
linux-arm@xxxxxxxxxxxxxxxxxxx
http://lists.infradead.org/mailman/listinfo/linux-arm

Follow-Ups:
- Avoiding #ifdefs
  - From: CoDeBrEaKeR

Prev by Date: sdcard driver porting to linux 2.6.25 from 2.6.19 problem - help needed - Freescale IMX 27 processor
Next by Date: gstreamer comilation for ARM
Previous by thread: sdcard driver porting to linux 2.6.25 from 2.6.19 problem - help needed - Freescale IMX 27 processor
Next by thread: Avoiding #ifdefs
Index(es):
- Date
- Thread

[Linux ARM] [Linux ARM MSM] [Linux ARM Kernel] [Fedora ARM] [IETF Annouce] [Security] [Bugtraq] [Linux] [Linux OMAP] [Linux MIPS] [ECOS] [Asterisk Internet PBX] [Linux API]

Add to Google

Follow linuxarm on Twitter