linux/meta-fsl-ppc.git/recipes-core/udev, branch morty

eudev: make eudev bbappend version generic

2016-06-14T09:52:11+00:00

eudev_3.1.5.bbappend -> eudev_%.bbappend Signed-off-by: Zhenhua Luo

rename udev to eudev to align with change in poky

2016-03-03T03:03:34+00:00

Signed-off-by: Zhenhua Luo

udev-rules-qoriq: put patches to universe location

2016-01-08T09:22:31+00:00

Fix [Yocto: #8802] Signed-off-by: Ting Liu

udev-rules-qoriq: remove useless automount.rules

2015-12-23T06:21:57+00:00

Signed-off-by: Ting Liu Signed-off-by: Zhenhua Luo Acked-by: Otavio Salvador

udev-rules-qoriq: restrict COMPATIBLE_MACHINE to qoriq-ppc

2015-12-23T06:21:24+00:00

The autobuilder does a universe fetch with the meta-fsl-* layers enabled, and gets errors when MACHINE=qemux86. Restrict COMPATIBLE_MACHINE to skip this recipe. Fix [Yocto: #8802] Signed-off-by: Ting Liu Signed-off-by: Zhenhua Luo Acked-by: Otavio Salvador

udev-rules-qoriq: avoid conflict with udev-extraconf

2015-08-13T10:21:58+00:00

udev-extraconf installs file mount.blacklist too. rpm/ndb bits should go into udev-extraconf recipes, otherwise there will be file conflict. Signed-off-by: Ting Liu Acked-by: Otavio Salvador

t1023: name DPAA FMan eth port as fmN-macN

2015-07-20T09:16:36+00:00

Apply the rule which is the same with t1024 and all e6500 boards. Signed-off-by: Ting Liu Acked-by: Otavio Salvador

udev-extraconf: replace bbappend with own recipe

2015-01-08T10:14:15+00:00

* introduce variable RULE for DPAA FMan ethernet ports name rule. * use 72-fsl-dpaa-persistent-networking.rules for t1024, same as e6500. Signed-off-by: Ting Liu

udev-extraconf: not automount disk partitions

2014-08-06T03:07:56+00:00

There is a bug found in FSL SDK: kernel can't boot up (or hang for a long time) when board connects with a HDD (has extended partition) via pcie sata controller card. avoid auto-mounting disk partitions. user can do it via fstab. And move all the customized rules to qoriq-ppc folers. Signed-off-by: Ting Liu

udev-extraconf: not automount network block devices

2014-08-06T03:07:50+00:00

The nbd devices are set up loop devices, we first have dead device nodes, then later we attach stuff behind them. At the time of the udev creation event, nothing works at nbd devices. This avoids unnecessary boot error msg: | nbd0: Attempted send on closed socket | end_request: I/O error, dev nbd0, sector 0 Signed-off-by: Ting Liu