On 30 August 2015 at 16:55, Simon Glass <s...@chromium.org> wrote: > When a uclass definition is missing, no drivers in that uclass can operate. > This can happen if a board has a strange collection of options (e.g. the > driver is enabled but the uclass is not). > > Unfortunately this is very confusing at present. Starting up driver model > results in a -ENOENT error, which is pretty generic. Quite a big of digging > is needed to get to the root cause. > > To help with this, change the error to a very strange one with no other > users in U-Boot. Also add a debug message. > > Signed-off-by: Simon Glass <s...@chromium.org> > --- > > Changes in v5: None > Changes in v4: None > Changes in v3: None > Changes in v2: None > > drivers/core/device.c | 4 +++- > drivers/core/uclass.c | 7 ++++++- > 2 files changed, 9 insertions(+), 2 deletions(-)
Applied to u-boot-rockchip. _______________________________________________ U-Boot mailing list U-Boot@lists.denx.de http://lists.denx.de/mailman/listinfo/u-boot
