| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
|
|
| |
ridiculous. This is the first step for a common and generic ARM port
for ARMv7 SoCs.
|
| | |
|
| |
|
|
| |
found by and ok jsg@
|
| |
|
|
|
|
| |
functions for now.
ok bmercer@
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Renamed `ahb' to `omap' and extended it to configure the on-chip
devices directly, based a board-specific table instead of trying to
maintain addresses, interrupt numbers and such for two OMAP variants
in the same config file.
This may be an intermediate step, but should provide us some relief
already. :)
Suggestions from deraadt and drahn; ok drahn@
|
| |
|
|
|
| |
point. So add it's card id and handle it like the beagleboard.
ok drahn@, miod@
|
| |
|
|
| |
to allow panda to share the port.
|
| |
|
|
|
|
| |
out of the register input. (with a beagle_start.S fix from uwe@)
Devices now detect device_id from u-boot and decide to enable/disable
themselves in the device match routine. ok uwe@
|
| |
|
|
|
|
|
| |
hierarchy. Everything attached to a single root node anyway, so at
best we had a bush.
"i think it is good" deraadt@
|
| |
|
|
|
|
|
| |
Bogus chunks pointed out by matthew@ and miod@. No cookies for
marco@ and jasper@.
ok deraadt@ miod@ matthew@ jasper@ macro@
|
| |
|
|
| |
ok miod@
|
|
|
however other omap system may be supportable. Not functional until armv7
core changes are complete.
|