de for their explicit
> > permission. Legally it is a huge difference between actively
> > confirming approval and not reacting at all.
> >
>
> All people (except Freescale and NXP employees) contributed to this code
> are in the CC list. Please give y
Compiled the CONFIG_TARGET_MPC8548CDS target and verified that no
additional instructions were emitted related to this patch.
Booted an image on a MPC8541 based board successfully.
Signed-off-by: Curt Brune c...@cumulusnetworks.com
---
drivers/ddr/fsl/ctrl_regs.c | 10 +-
1 file changed
Hello,
I am curious about the setting of the SS_EN bit in the
DDR_SDRAM_CLK_CNLT register:
Source synchronous enable. This bit field must be set during
initialization. See Section 9.6.1, “DDR SDRAM Initialization
Sequence,” for details.
0 - Reserved
1 - The address and command
- Original Message -
Have a look at DUTS [1]; the test cases implemented there serve a
double purpose: 1) they help testing (some of) the functionality of
U-Boot (and Linux) on a specific board, and 2) they generate the
needed include files to produce a board-specific version of the
Hello,
I have some questions about how U-Boot regression testing works. I am
assuming some regression testing happens during the release period
across some representative sample of boards and architectures.
I know people check for compilation failures with MAKEALL, but I am
wondering about
Hi,
What does u-boot expect to find in the device tree for a system with
multiple CPU sockets (not multi-core, but multiple physical CPUs) ?
For example if you have a two socket system, with a dual-core CPU per
socket would there just be 4 nodes in cpus {} with reg = 0, 1, 2, 3 or
is there
Hi -
Looking for suggestions on how to identify a particular USB mass storage device
on my platform.
My platform has a P2020 SoC. The SoC USB controller is connected to an on
board USB hub. The hub has 3 connections as follows:
+-+
| |---[USB flash controller, fronting a
Hello -
I want to pass a number of arguments from u-boot to the booted kernel.
The arguments are needed by user space applications, not the kernel.
I can think of two ways:
1. append args by setting bootargs.
2. add nodes to the dtb before booting.
Is there a preferred way to pass
On 01/08/2013 02:37 PM, Stephen Warren wrote:
Besides, it seems that storing a bunch of *.dtb in /boot is far easier
than screwing around with FIT images, which just seem like a hopeless
mess to me; why put a filesystem inside a file when there's already a
/boot filesystem that you could
Hello,
I am following up on this thread:
Merging device trees at runtime for module-based systems
http://lists.denx.de/pipermail/u-boot/2012-November/139618.html
I do not have a modular based system, so I do not need the full
flexibility of merging DT fragments at runtime. However, I am very
On 01/07/2013 10:36 AM, Stephen Warren wrote:
On 01/07/2013 11:01 AM, Curt Brune wrote:
Hello,
I am following up on this thread:
Merging device trees at runtime for module-based systems
http://lists.denx.de/pipermail/u-boot/2012-November/139618.html
I do not have a modular based system, so
On 01/07/2013 12:12 PM, Wolfgang Denk wrote:
Dear Curt Brune,
In message 50eb0d92.2020...@cumulusnetworks.com you wrote:
What I would love is to have a single multi-file uImage I could use on
all my platforms. The idea is to introduce a new image type that is a
list of device tree blobs
12 matches
Mail list logo
