Hi Marek,
On Thu, Oct 9, 2014 at 8:59 PM, Marek Vasut ma...@denx.de wrote:
I agree that buildman solves the CI part nicely, but we also have the part
where one has to install the myriad of toolchains for all the architectures
to be able to do the compile testing. I wonder if this cannot be
Hi,
On 9 October 2014 20:06, Fabio Estevam feste...@gmail.com wrote:
Hi Marek,
On Thu, Oct 9, 2014 at 8:59 PM, Marek Vasut ma...@denx.de wrote:
I agree that buildman solves the CI part nicely, but we also have the part
where one has to install the myriad of toolchains for all the
On Thu, Oct 9, 2014 at 11:07 PM, Simon Glass s...@chromium.org wrote:
It's not really the builder that is the problem - we have one. It's
all the different toolchains that no one knows about. I still can't
build all the boards successfully.
Aren't all the toolchains U-boot need included in
On Friday, October 10, 2014 at 04:00:00 AM, Simon Glass wrote:
Hi Marek,
On 9 October 2014 17:59, Marek Vasut ma...@denx.de wrote:
On Thursday, October 09, 2014 at 08:04:29 PM, Simon Glass wrote:
Hi Marek,
Hi Simon,
[..]
I mean more continuous integration (build testing) of
On Thu, Oct 9, 2014 at 11:23 PM, Marek Vasut ma...@denx.de wrote:
What about [1], this is where we can source the more exotic toolchains from,
can we not? I think it was even you who pointed me to this site and it really
is a nice one ;-)
[1] https://www.kernel.org/pub/tools/crosstool/
Hi,
On 9 October 2014 20:26, Fabio Estevam feste...@gmail.com wrote:
On Thu, Oct 9, 2014 at 11:23 PM, Marek Vasut ma...@denx.de wrote:
What about [1], this is where we can source the more exotic toolchains from,
can we not? I think it was even you who pointed me to this site and it really
is
On 28 September 2014 09:13, Simon Glass s...@chromium.org wrote:
On 28 September 2014 07:52, Masahiro Yamada yamad...@jp.panasonic.com wrote:
The struct udevice stands for a device, not a driver.
The driver_info.name is a driver's name, which is referenced
to bind devices.
Signed-off-by:
On 28 September 2014 09:15, Simon Glass s...@chromium.org wrote:
On 28 September 2014 07:52, Masahiro Yamada yamad...@jp.panasonic.com wrote:
The function uclass_add() checks uc_drv-ops as follows:
if (uc_drv-ops) {
dm_warn(No ops for uclass id %d\n, id);
On 28 September 2014 12:49, Igor Grinberg grinb...@compulab.co.il wrote:
Hi Masahiro, Simon,
On 09/28/14 18:22, Simon Glass wrote:
Hi Masahiro,
On 28 September 2014 07:52, Masahiro Yamada yamad...@jp.panasonic.com
wrote:
if (strncmp(name, entry-name, len))
On 7 October 2014 22:14, Simon Glass s...@chromium.org wrote:
On 6 October 2014 23:48, Masahiro Yamada yamad...@jp.panasonic.com wrote:
The header file include/linker_lists.h uses __aligned();
therefore it depends on include/linux/compiler.h
Signed-off-by: Masahiro Yamada
On 7 October 2014 22:14, Simon Glass s...@chromium.org wrote:
On 6 October 2014 23:49, Masahiro Yamada yamad...@jp.panasonic.com wrote:
The header files include/dm/platdata.h and include/dm/uclass.h
use ll_entry_declare(); therefore they depend on
include/linker_lists.h.
Signed-off-by:
On 7 October 2014 22:14, Simon Glass s...@chromium.org wrote:
On 6 October 2014 23:49, Masahiro Yamada yamad...@jp.panasonic.com wrote:
Signed-off-by: Masahiro Yamada yamad...@jp.panasonic.com
Acked-by: Simon Glass s...@chromium.org
Applied to u-boot-dm/next, thanks!
On 7 October 2014 22:15, Simon Glass s...@chromium.org wrote:
On 6 October 2014 23:51, Masahiro Yamada yamad...@jp.panasonic.com wrote:
The driver model supports two ways for passing device parameters;
Device Tree and platform_data (board file).
Each driver should generally support both of
On 3 October 2014 20:40, Simon Glass s...@chromium.org wrote:
Hi Scott,
On 2 October 2014 18:54, Scott Wood scottw...@freescale.com wrote:
On Tue, 2014-09-30 at 20:25 -0600, Simon Glass wrote:
Hi Scott,
On 29 September 2014 10:22, Scott Wood scottw...@freescale.com wrote:
On Sun,
On 24 September 2014 05:49, Jagan Teki jagannadh.t...@gmail.com wrote:
On 24 September 2014 00:35, Simon Glass s...@chromium.org wrote:
This brings in a additional small fix which was missed in a recent update
to the README.
Suggested-by: Masahiro Yamada yamad...@jp.panasonic.com
On 3 October 2014 20:40, Simon Glass s...@chromium.org wrote:
Add an explanation for how to set up git so that patman can find the alias
file. Fix up the get_maintainers message too.
Reported-by: Scott Wood scottw...@freescale.com
Signed-off-by: Simon Glass s...@chromium.org
---
Commit 32d0192 broke the sandbox build - fix it.
Signed-off-by: Simon Glass s...@chromium.org
---
drivers/serial/serial-uclass.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/serial/serial-uclass.c b/drivers/serial/serial-uclass.c
index fd010ca..6dde4ea 100644
---
Hi,
On 8 October 2014 14:48, Przemyslaw Marczak p.marc...@samsung.com wrote:
This is the implementation of driver model regulator uclass api.
To use it, the CONFIG_DM_PMIC is required with driver implementation,
since it provides pmic devices I/O API.
The regulator framework is based on a
Hi,
On 8 October 2014 14:48, Przemyslaw Marczak p.marc...@samsung.com wrote:
This is an introduction to driver-model multi class PMIC support.
It starts with UCLASS_PMIC - a common PMIC class type for I/O, which
doesn't need to implement any specific operations and features beside
the
Hi,
On 8 October 2014 14:48, Przemyslaw Marczak p.marc...@samsung.com wrote:
This function call is required to init dm pmic framework
and drivers before call to power_init_board().
Signed-off-by: Przemyslaw Marczak p.marc...@samsung.com
---
common/board_r.c | 8
1 file changed, 8
Hi,
On 8 October 2014 14:48, Przemyslaw Marczak p.marc...@samsung.com wrote:
Signed-off-by: Przemyslaw Marczak p.marc...@samsung.com
---
doc/driver-model/dm-pmic-framework.txt | 450
+
1 file changed, 450 insertions(+)
create mode 100644
Hi,
On 8 October 2014 14:48, Przemyslaw Marczak p.marc...@samsung.com wrote:
In case of two pmic frameworks availability - enable support of both,
since the new pmic framework is not fully finished and some boards still
supports only the old framework.
Signed-off-by: Przemyslaw Marczak
Hi,
On 8 October 2014 14:48, Przemyslaw Marczak p.marc...@samsung.com wrote:
Changes required to support dm pmic and dm regulator api:
- move call to board_init_i2c() into exynos_init() - earlier init the i2c
- remove redundant ldo setup - default hardware configuration is proper
- adjust
Hi,
On 8 October 2014 14:48, Przemyslaw Marczak p.marc...@samsung.com wrote:
This change enables the configs required to init and setup
max77686 regulator driver, using the new driver model pmic API.
Enabled configs:
- CONFIG_DM_PMIC
- CONFIG_DM_PMIC_MAX77686
- CONFIG_DM_PMIC_I2C
-
HI Hans,
On 9 October 2014 02:13, Hans de Goede hdego...@redhat.com wrote:
Hi,
On 10/09/2014 09:59 AM, Ian Campbell wrote:
On Wed, 2014-10-08 at 13:27 -0600, Simon Glass wrote:
Any more comments on this series please? I have a few nits so could
respin.
I'm afraid I'm unlikely to get to
On 6 October 2014 06:33, Robert Baldyga r.bald...@samsung.com wrote:
Add proper initialization of GPIO pins used by software i2c.
Signed-off-by: Robert Baldyga r.bald...@samsung.com
---
Hi Simon,
This patch is intended for your gpio-working branch. It seems that this
is only thing which
Przemyslaw Marczak p.marc...@samsung.com wrote on 2014/10/09 18:23:54:
Hello Joakim,
On 10/09/2014 08:46 AM, Joakim Tjernlund wrote:
From: Przemyslaw Marczak p.marc...@samsung.com
The functions error's numbers are standarized - but the error
messages are not.
The errors are often
101 - 127 of 127 matches
Mail list logo
