When setenv complains that it can't set a device parameter, then print
which parameter it tried to set.
Signed-off-by: Sascha Hauer
---
common/env.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/common/env.c b/common/env.c
index 80d3f7ab50..323a82223e 100644
--- a/common/en
Sometimes for communication with a simple I2C devices
(e.g. PCF8574 or TM1650) it's necessary to send only
one data byte into the I2C device.
Current i2c_write command makes this impossible because
you can't just pass 'device address' and 'register number'
(or 'device address' and 'one data byte')
Leaving the flags field unitialized can lead to performing
read operation instead of write operation.
Signed-off-by: Antony Pavlov
---
drivers/i2c/i2c.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/i2c/i2c.c b/drivers/i2c/i2c.c
index e9e7575585..608f8289bf 100644
--- a/drivers/i2c
On Tue, Feb 06, 2018 at 05:43:40PM +0100, Aleksander Morgado wrote:
> >>
> >> The first patches (1-5) break the current RATP API, by introducing
> >> the concept of requests, responses and indications:
> >> * Requests sent to one endpoint are expected to be replied with
> >>a response by the p
On Tue, Feb 06, 2018 at 05:49:10PM +0100, Aleksander Morgado wrote:
> >> +
> >> +#define BAREBOX_RATP_CMD_START(_name)
> >>\
> >> +extern const struct ratp_command __barebox_cmd_##_name;
> >>\
> >
> > Yo
On Tue, Feb 06, 2018 at 05:51:59PM +0100, Aleksander Morgado wrote:
> On Tue, Feb 6, 2018 at 10:33 AM, Sascha Hauer wrote:
> > On Fri, Feb 02, 2018 at 12:14:39PM +0100, Aleksander Morgado wrote:
> >> Signed-off-by: Aleksander Morgado
> >> ---
> >> commands/Makefile| 1 +
> >> commands/ratp-
