On Thu, May 22, 2014 at 12:04 PM, Alexander Graf ag...@suse.de wrote:
On 22.05.14 09:52, Alon Bar-Lev wrote:
Hi,
Trying to run the qemu-ppce500 within qemu. I am using -bios u-boot.bin and
no luck, I get live signal.
I am using latest u-boot master and qemu master.
Command:
$
This enables relocation of initrd to the end of available DDR before Linux
kernel start-up as it is done in other architectures.
Signed-off-by: Alexey Brodkin abrod...@synopsys.com
---
arch/arc/include/asm/config.h | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arc/include/asm/config.h
Dear Wolfgang,
Thank you very much for pointing out the issue of address conflict.
I tried loading the standalone app considering your remarks, however, the
app hangs at the following after a bootm command :
Hi Michal,
On Wed, 14 May 2014 08:09:36 +0200, Michal Simek
michal.si...@xilinx.com wrote:
Hi Albert,
here is the set of patches I have capture for Xilinx Zynq.
I am sending it now because this patchset was based on
fpga changes I have done and which were merged yesterday.
I have also
Hi Nobuhiro,
On Wed, 21 May 2014 10:20:10 +0900, Nobuhiro Iwamatsu
iwama...@nigauri.org wrote:
Dear Albert Aribaud,
Please pull u-boot-sh/rmobile into u-boot-arm/master.
The following changes since commit 05d134b084590684bcf4d832c0035952727b7cd9:
Merge remote-tracking branch
Hi Tom,
On Fri, 23 May 2014 19:52:11 -0400, Tom Rini tr...@ti.com wrote:
Hello,
The following changes since commit 05d134b084590684bcf4d832c0035952727b7cd9:
Merge remote-tracking branch 'u-boot/master' (2014-05-20 10:05:42 +0200)
are available in the git repository at:
Hi Michal,
On Tue, 20 May 2014 15:21:55 +0200, Michal Simek mon...@monstr.eu
wrote:
Hi Albert,
based on your pull request to Tom here
http://lists.denx.de/pipermail/u-boot/2014-May/179841.html
and our IRC last week I am sending updated pull request
where I have added 5 more patches from
Hi Michal,
On Sat, 24 May 2014 10:38:37 +0200, Albert ARIBAUD
albert.u.b...@aribaud.net wrote:
Hi Michal,
≤ [...]
Applied to u-boot-arm/master, thanks!
Disregard -- V2 was applied, not this V1.
Amicalement,
--
Albert.
___
U-Boot mailing list
Hello Tom (and sorry for the duplicate),
The following changes since commit
10dc77716f41979e03baf3b847b97dc7279ef30d:
esdhc/usdhc: Fix warning when CONFIG_SYS_FSL_ESDHC_USE_PIO is not set
(2014-05-23 09:19:05 -0400)
are available in the git repository at:
git://git.denx.de/u-boot-arm
On Fri, May 23, 2014 at 03:57:34PM -1000, Simon Glass wrote:
Hi Tom,
On 21 May 2014 10:46, Tom Rini tr...@ti.com wrote:
On Wed, May 21, 2014 at 10:10:50PM +0200, Wolfgang Denk wrote:
Dear Tom Rini,
In message 20140521195824.GE1752@bill-the-cat you wrote:
Something that Rob
Am 19.05.2014 11:21, schrieb Prafulla Wadaskar:
-Original Message-
From: Bastien ROUCARIÈS
[mailto:roucaries.bast...@gmail.com]
Sent: 18 May 2014 21:51
To: u-boot@lists.denx.de
Cc: Jamie Lentin; Prafulla Wadaskar; Albert ARIBAUD;
Stefan Herbrechtsmeier
Subject: [PATCH 4/4] kirkwood:
Am 22.05.2014 21:13, schrieb Bastien ROUCARIÈS:
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Hi,
A rebase of an old patch set from Jamie Lentin.
Source is available here:
http://jamie.lentin.co.uk/devices/dlink-dns325/
Please apply
Changelog:
Dear mazen.e,
In message 1400920322709-180612.p...@n7.nabble.com you wrote:
I tried loading the standalone app considering your remarks, however, the
app hangs at the following after a bootm command :
Hello All,
I am using a custom ARM based development board running u-boot
from PNOR memory. However, it does not have support for the Micron SPI flash
memory (N25Q064A). I have added support for the micron memory in
drivers/mtd/spi/stmicro.c file and included the flag
Hello All,
I am using a custom ARM based development board running u-boot
from PNOR memory. However, it does not have support for the Micron SPI flash
memory (N25Q064A). I have added support for the micron memory in
drivers/mtd/spi/stmicro.c file and included the flag
On Sat, May 24, 2014 at 10:27 PM, Amit Mahadik amitmahadi...@yahoo.com wrote:
Hello All,
I am using a custom ARM based development board running
u-boot from PNOR memory. However, it does not have support for the Micron SPI
flash memory (N25Q064A). I have added support for the
On Thursday, May 22, 2014 at 12:43:06 PM, Heiko Schocher wrote:
resync with linux:
commit 455c6fdbd219161bd09b1165f11699d6d73de11c
Author: Linus Torvalds torva...@linux-foundation.org
Date: Sun Mar 30 20:40:15 2014 -0700
Linux 3.14
Needed for the MTD/UBI/UBIFS resync
On Friday, May 23, 2014 at 12:05:02 PM, mazen.e wrote:
Is it possible to load a bare-metal standalone application by using uboot,
Yes
and let the standalone app load a kernel and FS
If you pass control to it, yes.
, could you please propose a
hint on how to it?
As you gave no hints on
On Wednesday, May 21, 2014 at 04:08:09 PM, jkrause wrote:
I was wondering about the following warnings while bootings linux
3.15.0-rc5:
[0.998885] nand: device found, Manufacturer ID: 0x98, Chip ID: 0xd1
[1.005485] nand: Toshiba NAND 128MiB 3,3V 8-bit
[1.010165] nand: 128MiB,
On Wednesday, May 21, 2014 at 04:01:55 AM, Peter Schumann wrote:
This patch makes it possible to boot from battery on olinuxino Boards
from Olimex.
We should not set DOUBLE_FETS in HW_POWER_MINPWR
Please explain how you arrived to this conclusion.
, it makes my system
reset with in
Am Samstag, 19. April 2014, 23:52:19 schrieb Michael Walle:
Am 2014-04-01 20:09, schrieb Michael Walle:
Move addresses for kernel, ramdisk and fdt blob to own variables. Add
dtb
blob loading to all existing boot scripts, dtb filenames were taken
from
vanilla kernel. Introduce new boot
+ u-boot ML
On Sat, May 24, 2014 at 11:48 PM, Amit Mahadik amitmahadi...@yahoo.com wrote:
Hello Sir,
Please find attached my driver file. The function
spi_flash_alloc_base declaration was added to include/spi_flash.h and
definition to drivers/mtd/spi/spi_flash.c.
Yes - It's
Amit,
If you can, place a SPI protocol analyzer on the bus and trace its transactions.
I recently debugged a similar symptom and discovered that I was not driving
the Tx FIFO consistently enough to maintain the appearance of a single
transaction on the ID request to the flash.
How is your SPI
On Sat, May 24, 2014 at 11:32:00AM +0200, Albert ARIBAUD wrote:
Hello Tom (and sorry for the duplicate),
The following changes since commit
10dc77716f41979e03baf3b847b97dc7279ef30d:
esdhc/usdhc: Fix warning when CONFIG_SYS_FSL_ESDHC_USE_PIO is not set
(2014-05-23 09:19:05 -0400)
Hello Simon,
On vr, 2014-05-23 at 15:37 -1000, Simon Glass wrote:
On 9 May 2014 12:31, Jeroen Hofstee dasub...@myspectrum.nl wrote:
Hello,
tools/Makefile uses the following substitution
HOST_EXTRACFLAGS += -include $(srctree)/include/libfdt_env.h \
$(patsubst
This series adds support for a serial uclass, enabling serial drivers to be
converted to use driver model.
Unfortunately this is quite a complicated process for a number of reasons:
- serial is used before relocation, but driver model does not support this
- stdio member functions are not passed
Add a new method which removes and unbinds all drivers.
Signed-off-by: Simon Glass s...@chromium.org
---
drivers/core/root.c | 8
include/dm/root.h | 8
2 files changed, 16 insertions(+)
diff --git a/drivers/core/root.c b/drivers/core/root.c
index 9fff164..4873e7b 100644
There is a spelling mistake and two functions are missing comments
altogether. Also the flags declaration is correct, but doesn't follow
style. Finally, the uclass_get_device() function has some errors in
its documentation.
Fix these problems.
Signed-off-by: Simon Glass s...@chromium.org
---
These don't really server any purpose in the modern age, IMO. On the
other hand they show up as annoying control characters in my editor, which
then happily removes them.
I believe we can drop these characters from the file.
Signed-off-by: Simon Glass s...@chromium.org
---
common/dlmalloc.c |
The lifecycle of a device is an important part of driver model. Add to the
existing documentation and clarify it.
Thanks for Jon Loeliger j...@jdl.com for helping with the text and
suggesting improvements.
(Jon please comment/adjust to help clarify things further)
Reported-by: Jon Loeliger
Make both dm enumeration commands support showing whether a driver is active
or not, and use a consistent indicator (an asterisk).
Signed-off-by: Simon Glass s...@chromium.org
---
test/dm/cmd_dm.c | 11 ++-
1 file changed, 6 insertions(+), 5 deletions(-)
diff --git a/test/dm/cmd_dm.c
If the sandbox device tree is provided to U-Boot (with the -d flag) then it
will use the device tree version in preference to the built-in device. The
only difference is the colour.
Signed-off-by: Simon Glass s...@chromium.org
---
arch/sandbox/dts/sandbox.dts | 11 +++
1 file changed,
Drivers are supposed to be able to close down cleanly. To set a good example,
make sandbox shut down its driver model drivers and remove them before exit.
It may be desirable to do the same more generally once driver model is more
widely-used. This could be done during bootm, before U-Boot jumps
Since driver model registers itself with the stdio subsystem, and we
want to avoid delayed registration and other complexity associated with
the current serial console, move the stdio subsystem init earlier when
driver model is used for serial.
This simplifies the implementation. Should there be
If we are to have driver model before relocation we need to support some
way of calling memory allocation routines.
The standard malloc() is pretty complicated:
1. It uses some BSS memory for its state, and BSS is not available before
relocation
2. It supports algorithms for reducing memory
If the console is not present, we try to reduce overhead by stopping any
output in vprintf(), before it gets to putc(). This is dubious merit in
general, but in the case of sandbox it is incorrect, since we have a
fallback console which reports errors very early in U-Boot. If this is
defeated
Initialise devices marked 'pre-reloc' and make them available prior to
relocation. Note that this requires pre-reloc malloc() to be available.
Signed-off-by: Simon Glass s...@chromium.org
---
common/board_f.c | 30 ++
common/board_r.c
Serial devices support simple byte input/output and a few operations to find
out whether data is available. Add a basic uclass for serial devices to be
used by drivers that are converted to driver model.
Signed-off-by: Simon Glass s...@chromium.org
---
drivers/serial/Makefile| 4 +
There is no point in setting a structure memory to NULL when it has already
been zeroed with memset().
Also, there is no need to create a stub function for stdio to call - if the
function is NULL it will not be called.
This is a clean-up, with no change in functionality.
Signed-off-by: Simon
The root device should be probed just like any other device. The effect of
this is to mark the device as activated, so that it can be removed (along
with its children) if required.
Signed-off-by: Simon Glass s...@chromium.org
---
drivers/core/root.c | 3 +++
test/dm/core.c | 2 +-
2 files
Where there are serveral device options that can be chosen, often one is
preferred. This can normally be handled by aliases in the device tree.
However, when a device can be specified either with platform data or
with a device tree node, which one should dm use? This situation happens
with
Driver model currently only operates after relocation is complete. In this
state U-Boot typically has a small amount of memory available. In adding
support for driver model prior to relocation we must try to use as little
memory as possible.
In addition, on some machines the memory has not be
The current sandbox serial driver is a pretty trivial example and does not
have the featues that might be needed for other board serial drivers. To
help provide a better example, add a text colour property to the device
tree for sandbox. This uses platform data, a device tree node, driver
private
The current functions for adding and removing devices require a device name.
This is not convenient for driver model, which wants to store a pointer to
the relevant device. Add new functions which provide this feature and adjust
the old ones to call these.
Signed-off-by: Simon Glass
At present stdio device functions do not get any clue as to which stdio
device is being acted on. Some implementations go to great lengths to work
around this, such as defining a whole separate set of functions for each
possible device.
For driver model we need to associate a stdio_dev with a
Enable this for sandbox so that we will be able to use driver model before
relocation.
Signed-off-by: Simon Glass s...@chromium.org
---
include/configs/sandbox.h | 4
1 file changed, 4 insertions(+)
diff --git a/include/configs/sandbox.h b/include/configs/sandbox.h
index fdc8b75..86ee70f
Adjust the sandbox serial driver to use the new driver model uclass. The
driver works much as before, but within the new framework.
Signed-off-by: Simon Glass s...@chromium.org
---
drivers/serial/sandbox.c | 67 +--
include/configs/sandbox.h | 3 +++
For sandbox we have a fallback console which is used very early during
U-Boot, before serial drivers are available. Rather than try to guess
when to switch to the real one, add a flag so we can be sure. This makes
sure that sandbox can always output a panic() message, for example, and
avoids
In current gpio_set_value() implementation, it always sets the gpio control bit
no matter the value argument is 0 or 1. Thus the GPIOs never set to low.
This patch fixes this bug.
The address bus is used as a mask on read/write operations, so that independent
software drivers can set their GPIO
Hello Sir,
I will definetely try to trace the transactions.
--
On Sun 25 May, 2014 12:52 AM IST Jon Loeliger wrote:
Amit,
If you can, place a SPI protocol analyzer on the bus and trace its
transactions.
I recently debugged a similar symptom and
50 matches
Mail list logo
