Re: [yocto] systemd - how do I wait for a driver to load?
Am 26.08.2014 22:51, schrieb Chris Tapp: On 26 Aug 2014, at 21:02, Sven Ebenfeld sven.ebenf...@gmail.com wrote: You should look at ConditionPathExists= Options of systemd-units. Thanks, that looks like it would do the job. I was hoping not to hard code paths as they may change if a configuration file is changed, but... Otherwise if udev is loading your device module, you could add the device-unit to Requires= option. This sounds better. Is there an easy way to tell if udev did load the module? There's nothing obvious in the syslog. If you didn't load the module by hand it's probably udev. If you didn't run modprobe or insmod. Then you should try to create a device-unit for the device. For /dev/dvb/adaptor the unit should probably be something like dev-dvb-adaptor.device . Am 26.08.2014 21:52, schrieb Chris Tapp: I've got a service running under systemd that will only start once a kernel module has loaded and created its /dev/dvb/adaptor nodes. Unfortunately, it doesn't load until after the service has failed and gone into an error state due to too many restarts. I could fix this by increasing the restart interval, but is there a way of adding a dependancy on the kernel module? -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- Chris Tapp opensou...@keylevel.com www.keylevel.com -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] building a hierarchical poky variable glossary, noting what's missing
On Tue, 26 Aug 2014, Rifenbark, Scott M wrote: Robert, I can see your link being referenced from the YP ref-manual to augment variable descriptions and explanations. Also, your compilation could act as another source of information similar to the list of other information items that currently are shown at the front of the dev-manual. this whole thing will come in fits and spurts, and may even be redesigned completely if i think of a better way but, for the time being, if you're bored :-), you can always peruse it from time to time and note the variables that aren't included either in documentation.conf or the ref manual and do something about them: http://www.crashcourse.ca/wiki/index.php/Poky_Variable_Glossary of course, it's impossible to document *every* variable but in some cases, it's obvious that some variables deserve documentation. rday -- Robert P. J. Day Ottawa, Ontario, CANADA http://crashcourse.ca Twitter: http://twitter.com/rpjday LinkedIn: http://ca.linkedin.com/in/rpjday -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Image that depends on another image
On Thu, Aug 21, 2014 at 7:25 PM, Christopher Larson clar...@kergoth.com wrote: On Thu, Aug 21, 2014 at 5:08 PM, Seth Bollinger seth.b...@gmail.com wrote: Our device requires two images to be built. Is there any way to have the first image depend on the second image? do_rootfs[depends] += some-other-image:do_rootfs would probably do. I hate to resurrect this thread, but after testing this out and using it we ran into a small hiccup. Since we're using the second image to generate a second partition, a lot of the dependencies actually need to be injected into the first image (users, utilities, etc.). Is there a way to do this? Thanks again! Seth -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Force recipe to provide specific file
On Fri, 22 Aug 2014 11:07:41 +0200 Anders Darander and...@chargestorm.se wrote: What happens for example if do_install_append is already defined in the recipe? No issue at all. The do_install_append's will just be appended one after each other. Thanks you for this info! Maybe it would be a good idea to add it to the documentation somewhere ;-) regards, richard signature.asc Description: PGP signature -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Build dts alone
Hello, After changing the kernel dts file (directly in work directory) I would like to build just the dtb file from yocto (without rebuilding entire virtual/kernel target). Is it possible to do so? Regards, Anooj -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build dts alone
On Wednesday 27 of August 2014 15:57:40 Anooj Gopi wrote: Hello, After changing the kernel dts file (directly in work directory) I would like to build just the dtb file from yocto (without rebuilding entire virtual/kernel target). Is it possible to do so? First: bitbake -c devshell virtual/kernel Within the shell: make dtbs Or just build particular dtb if you know the name. -- Maciej Borzęcki Senior Software Engineer Open-RnD Sp. z o.o. www.open-rnd.pl, Facebook, Twitter mobile: +48 telefon, fax: +48 42 657 9079 Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. This message, including any attachments hereto, may contain privileged or confidential information and is sent solely for the attention and use of the intended addressee(s). If you are not an intended addressee, you may neither use this message nor copy or deliver it to anyone. In such case, you should immediately destroy this message and kindly notify the sender by reply email. Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] Build dts alone
Thank you very much... devshell is really cool. It would be nice if we could mention this info some where in http://www.yoctoproject.org/docs/current/kernel-dev/kernel-dev.html On Wed, Aug 27, 2014 at 4:05 PM, Maciej Borzecki maciej.borze...@open-rnd.pl wrote: On Wednesday 27 of August 2014 15:57:40 Anooj Gopi wrote: Hello, After changing the kernel dts file (directly in work directory) I would like to build just the dtb file from yocto (without rebuilding entire virtual/kernel target). Is it possible to do so? First: bitbake -c devshell virtual/kernel Within the shell: make dtbs Or just build particular dtb if you know the name. -- Maciej Borzęcki Senior Software Engineer Open-RnD Sp. z o.o. www.open-rnd.pl, Facebook, Twitter mobile: +48 telefon, fax: +48 42 657 9079 Niniejsza wiadomość wraz z załącznikami może zawierać chronione prawem lub poufne informacje i została wysłana wyłącznie do wiadomości i użytku osób, do których została zaadresowana. Jeśli wiadomość została otrzymana przypadkowo zabrania się jej kopiowania lub rozsyłania do osób trzecich. W takim przypadku uprasza się o natychmiastowe zniszczenie wiadomości oraz poinformowanie nadawcy o zaistniałej sytuacji za pomocą wiadomości zwrotnej. Dziękujemy. This message, including any attachments hereto, may contain privileged or confidential information and is sent solely for the attention and use of the intended addressee(s). If you are not an intended addressee, you may neither use this message nor copy or deliver it to anyone. In such case, you should immediately destroy this message and kindly notify the sender by reply email. Thank you. -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
Re: [yocto] [yocto-autobuilder] buildsteps/RunOeSelftest.py: change the way oe-selftest is called
On Wed, Aug 20, 2014 at 5:57 AM, Corneliu Stoicescu corneliux.stoice...@intel.com wrote: A recent patch went in poky master that added command line parsing and options to the oe-selftest script. Changing the way oe-selftest is called by the autobuilder to account for these changes. Signed-off-by: Corneliu Stoicescu corneliux.stoice...@intel.com --- lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py b/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py index 0efddd7..3d95583 100644 --- a/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py +++ b/lib/python2.7/site-packages/autobuilder/buildsteps/RunOeSelftest.py @@ -22,5 +22,5 @@ class RunOeSelftest(ShellCommand): self.description = Running oe-selftest self.timeout = 10 kwargs['timeout']=self.timeout -self.command = if [ -d meta-selftest ]; then . ./oe-init-build-env; oe-selftest; else echo 'Skipping step - no meta-selftest layer here'; fi +self.command = if [ -d meta-selftest ]; then . ./oe-init-build-env; oe-selftest --run-all-tests; else echo 'Skipping step - no meta-selftest layer here'; fi ShellCommand.__init__(self, **kwargs) -- 1.8.3.2 -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto Pulled into master. Pushing into Production this afternoon. Thanks! -- Elizabeth Flanagan Yocto Project Build and Release -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[yocto] Add the new driver in yocto
Hi, I am using yocto for wandboard. I have written one I2C driver for my I2C device. *The procedure which I followed to add and build the driver in yocto is as* : 1) Make the entry of my driver in Makefile and Kconfig in build directory. 2) Replace the defconfig (present in source directory) with .config (present in build directory). 3) Add the driver information in device tree file. Then I run the *bitbake linux-imx -c compile -f* to compile the kernel and face some errors. So is there any way (like to add as a patch *(patch of conf file and driver source code*) in some .bbappend file or something equivalent to it) through which I can add and compile my driver successfully *But during compilation I faced the below errors:* *vinod@vinod:~/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/git$ bitbake linux-imx -c compile -fLoading cache: 100% || ETA: 00:00:00Loaded 1820 entries from dependency cache.NOTE: Resolving any missing task queue dependenciesBuild Configuration:BB_VERSION= 1.22.0BUILD_SYS = x86_64-linuxNATIVELSBSTRING = Ubuntu-12.04TARGET_SYS= arm-poky-linux-gnueabiMACHINE = imx6qsabresdDISTRO= pokyDISTRO_VERSION= 1.6.1TUNE_FEATURES = armv7a vfp neon callconvention-hard cortexa9TARGET_FPU= vfp-neonmeta meta-yocto = (nobranch):8e05d5e3fe04face623c4f9fb08b12f13c22edabmeta-oe = (nobranch):ee24939c4c70b63a9fb7e93a58889a3231d3d367meta-fsl-arm = (nobranch):d91871446d6baee8397522c4fa10d45985aa8645meta-fsl-arm-extra = (nobranch):456c27085a70bb1385a4c2e28ba80ac74d6f533emeta-fsl-demos= (nobranch):27fdb2f2642ecd55d5633bde880dd4c37acd0d42NOTE: Preparing runqueueNOTE: Tainting hash to force rebuild of task /home/vinod/vvdn/VSTI_PoSX/yocto_src/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb http://linux-imx_3.10.17.bb, do_compileNOTE: Executing SetScene TasksNOTE: Executing RunQueue TasksERROR: Function failed: do_compile (log file is located at /home/vinod/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/temp/log.do_compile.28793)ERROR: Logfile of failure stored in: /home/vinod/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/temp/log.do_compile.28793Log data follows:| DEBUG: Executing shell function do_compile| NOTE: make -j 4 uImage CC=arm-poky-linux-gnueabi-gcc -mno-thumb-interwork -marm LD=arm-poky-linux-gnueabi-ld.bfd LOADADDR=0x10008000| HOSTCC scripts/basic/fixdep| HOSTCC scripts/kconfig/conf.o| HOSTCC scripts/kconfig/zconf.tab.o| HOSTLD scripts/kconfig/conf| scripts/kconfig/conf --silentoldconfig Kconfig| ***| *** Configuration file .config not found!| ***| *** Please run some configurator (e.g. make oldconfig or| *** make menuconfig or make xconfig).| ***| make[2]: *** [silentoldconfig] Error 1| make[1]: *** [silentoldconfig] Error 2| make: *** No rule to make target `include/config/auto.conf', needed by `include/config/kernel.release'. Stop.| ERROR: oe_runmake failed| WARNING: exit code 1 from a shell command.| ERROR: Function failed: do_compile (log file is located at /home/vinod/vvdn/VSTI_PoSX/yocto_src/build/tmp/work/imx6qsabresd-poky-linux-gnueabi/linux-imx/3.10.17-r0/temp/log.do_compile.28793)ERROR: Task 4 (/home/vinod/vvdn/VSTI_PoSX/yocto_src/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb http://linux-imx_3.10.17.bb, do_compile) failed with exit code '1'NOTE: Tasks Summary: Attempted 247 tasks of which 246 didn't need to be rerun and 1 failed.Summary: 1 task failed: /home/vinod/vvdn/VSTI_PoSX/yocto_src/sources/meta-fsl-arm/recipes-kernel/linux/linux-imx_3.10.17.bb http://linux-imx_3.10.17.bb, do_compileSummary: There was 1 ERROR message shown, returning a non-zero exit code.* -- ___ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
[linux-yocto] [PATCH] BFQ: Support Budget Fair Queueing (BFQ) Storage-I/O Scheduler
From: Jianchuan Wang jianchuan.w...@windriver.com BFQ: Support Budget Fair Queueing (BFQ) Storage-I/O Scheduler Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com --- meta/cfg/kernel-cache/features/bfq/bfq-enable.scc | 1 + meta/cfg/kernel-cache/features/bfq/bfq.cfg| 2 ++ 2 files changed, 3 insertions(+) create mode 100644 meta/cfg/kernel-cache/features/bfq/bfq-enable.scc create mode 100644 meta/cfg/kernel-cache/features/bfq/bfq.cfg diff --git a/meta/cfg/kernel-cache/features/bfq/bfq-enable.scc b/meta/cfg/kernel-cache/features/bfq/bfq-enable.scc new file mode 100644 index 000..c75a014 --- /dev/null +++ b/meta/cfg/kernel-cache/features/bfq/bfq-enable.scc @@ -0,0 +1 @@ +kconf non-hardware bfq.cfg diff --git a/meta/cfg/kernel-cache/features/bfq/bfq.cfg b/meta/cfg/kernel-cache/features/bfq/bfq.cfg new file mode 100644 index 000..df82ebc --- /dev/null +++ b/meta/cfg/kernel-cache/features/bfq/bfq.cfg @@ -0,0 +1,2 @@ +CONFIG_IOSCHED_BFQ=y +CONFIG_CGROUP_BFQIO=y -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 3/3] block, bfq: add Early Queue Merge (EQM) to BFQ-v7r5 for 3.14.0
From: Mauro Andreolini mauro.andreol...@unimore.it
Original patch taken from:
http://algo.ing.unimo.it/people/paolo/disk_sched/patches/3.14.0-v7r5
A set of processes may happen to perform interleaved reads, i.e.,requests
whose union would give rise to a sequential read pattern. There are two
typical cases: in the first case, processes read fixed-size chunks of
data at a fixed distance from each other, while in the second case processes
may read variable-size chunks at variable distances. The latter case occurs
for example with QEMU, which splits the I/O generated by the guest into
multiple chunks, and lets these chunks be served by a pool of cooperating
processes, iteratively assigning the next chunk of I/O to the first
available process. CFQ uses actual queue merging for the first type of
rocesses, whereas it uses preemption to get a sequential read pattern out
of the read requests performed by the second type of processes. In the end
it uses two different mechanisms to achieve the same goal: boosting the
throughput with interleaved I/O.
This patch introduces Early Queue Merge (EQM), a unified mechanism to get a
sequential read pattern with both types of processes. The main idea is
checking newly arrived requests against the next request of the active queue
both in case of actual request insert and in case of request merge. By doing
so, both the types of processes can be handled by just merging their queues.
EQM is then simpler and more compact than the pair of mechanisms used in
CFQ.
Finally, EQM also preserves the typical low-latency properties of BFQ, by
properly restoring the weight-raising state of a queue when it gets back to
a non-merged state.
Signed-off-by: Mauro Andreolini mauro.andreol...@unimore.it
Signed-off-by: Arianna Avanzini avanzini.aria...@gmail.com
Signed-off-by: Paolo Valente paolo.vale...@unimore.it
Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com
---
block/bfq-iosched.c | 736
block/bfq-sched.c | 28 --
block/bfq.h | 46 +++-
3 files changed, 556 insertions(+), 254 deletions(-)
diff --git a/block/bfq-iosched.c b/block/bfq-iosched.c
index 0cbb182..452f477 100644
--- a/block/bfq-iosched.c
+++ b/block/bfq-iosched.c
@@ -571,6 +571,57 @@ static inline unsigned int bfq_wr_duration(struct bfq_data
*bfqd)
return dur;
}
+static inline unsigned
+bfq_bfqq_cooperations(struct bfq_queue *bfqq)
+{
+ return bfqq-bic ? bfqq-bic-cooperations : 0;
+}
+
+static inline void
+bfq_bfqq_resume_state(struct bfq_queue *bfqq, struct bfq_io_cq *bic)
+{
+ if (bic-saved_idle_window)
+ bfq_mark_bfqq_idle_window(bfqq);
+ else
+ bfq_clear_bfqq_idle_window(bfqq);
+ if (bic-saved_IO_bound)
+ bfq_mark_bfqq_IO_bound(bfqq);
+ else
+ bfq_clear_bfqq_IO_bound(bfqq);
+ if (bic-wr_time_left bfqq-bfqd-low_latency
+ bic-cooperations bfqq-bfqd-bfq_coop_thresh) {
+ /*
+* Start a weight raising period with the duration given by
+* the raising_time_left snapshot.
+*/
+ if (bfq_bfqq_busy(bfqq))
+ bfqq-bfqd-wr_busy_queues++;
+ bfqq-wr_coeff = bfqq-bfqd-bfq_wr_coeff;
+ bfqq-wr_cur_max_time = bic-wr_time_left;
+ bfqq-last_wr_start_finish = jiffies;
+ bfqq-entity.ioprio_changed = 1;
+ }
+ /*
+* Clear wr_time_left to prevent bfq_bfqq_save_state() from
+* getting confused about the queue's need of a weight-raising
+* period.
+*/
+ bic-wr_time_left = 0;
+}
+
+/*
+ * Must be called with the queue_lock held.
+ */
+static int bfqq_process_refs(struct bfq_queue *bfqq)
+{
+ int process_refs, io_refs;
+
+ io_refs = bfqq-allocated[READ] + bfqq-allocated[WRITE];
+ process_refs = atomic_read(bfqq-ref) - io_refs - bfqq-entity.on_st;
+ BUG_ON(process_refs 0);
+ return process_refs;
+}
+
static void bfq_add_request(struct request *rq)
{
struct bfq_queue *bfqq = RQ_BFQQ(rq);
@@ -602,8 +653,11 @@ static void bfq_add_request(struct request *rq)
if (!bfq_bfqq_busy(bfqq)) {
int soft_rt = bfqd-bfq_wr_max_softrt_rate 0
+ bfq_bfqq_cooperations(bfqq) bfqd-bfq_coop_thresh
time_is_before_jiffies(bfqq-soft_rt_next_start);
- idle_for_long_time = time_is_before_jiffies(
+ idle_for_long_time = bfq_bfqq_cooperations(bfqq)
+bfqd-bfq_coop_thresh
+ time_is_before_jiffies(
bfqq-budget_timeout +
bfqd-bfq_wr_min_idle_time);
entity-budget = max_t(unsigned long, bfqq-max_budget,
@@ -624,11 +678,20 @@ static void bfq_add_request(struct request *rq)
[linux-yocto] [PATCH 1/3] block: cgroups, kconfig, build bits for BFQ-v7r5-3.14
From: Paolo Valente paolo.vale...@unimore.it Original patch taken from: http://algo.ing.unimo.it/people/paolo/disk_sched/patches/3.14.0-v7r5 Update Kconfig.iosched and do the related Makefile changes to include kernel configuration options for BFQ. Also add the bfqio controller to the cgroups subsystem. Signed-off-by: Paolo Valente paolo.vale...@unimore.it Signed-off-by: Arianna Avanzini avanzini.aria...@gmail.com Signed-off-by: Jianchuan Wang jianchuan.w...@windriver.com --- block/Kconfig.iosched | 32 block/Makefile| 1 + include/linux/cgroup_subsys.h | 4 3 files changed, 37 insertions(+) diff --git a/block/Kconfig.iosched b/block/Kconfig.iosched index 421bef9..0ee5f0f 100644 --- a/block/Kconfig.iosched +++ b/block/Kconfig.iosched @@ -39,6 +39,27 @@ config CFQ_GROUP_IOSCHED ---help--- Enable group IO scheduling in CFQ. +config IOSCHED_BFQ + tristate BFQ I/O scheduler + default n + ---help--- + The BFQ I/O scheduler tries to distribute bandwidth among + all processes according to their weights. + It aims at distributing the bandwidth as desired, independently of + the disk parameters and with any workload. It also tries to + guarantee low latency to interactive and soft real-time + applications. If compiled built-in (saying Y here), BFQ can + be configured to support hierarchical scheduling. + +config CGROUP_BFQIO + bool BFQ hierarchical scheduling support + depends on CGROUPS IOSCHED_BFQ=y + default n + ---help--- + Enable hierarchical scheduling in BFQ, using the cgroups + filesystem interface. The name of the subsystem will be + bfqio. + choice prompt Default I/O scheduler default DEFAULT_CFQ @@ -52,6 +73,16 @@ choice config DEFAULT_CFQ bool CFQ if IOSCHED_CFQ=y + config DEFAULT_BFQ + bool BFQ if IOSCHED_BFQ=y + help + Selects BFQ as the default I/O scheduler which will be + used by default for all block devices. + The BFQ I/O scheduler aims at distributing the bandwidth + as desired, independently of the disk parameters and with + any workload. It also tries to guarantee low latency to + interactive and soft real-time applications. + config DEFAULT_NOOP bool No-op @@ -61,6 +92,7 @@ config DEFAULT_IOSCHED string default deadline if DEFAULT_DEADLINE default cfq if DEFAULT_CFQ + default bfq if DEFAULT_BFQ default noop if DEFAULT_NOOP endmenu diff --git a/block/Makefile b/block/Makefile index 20645e8..cbd83fb 100644 --- a/block/Makefile +++ b/block/Makefile @@ -16,6 +16,7 @@ obj-$(CONFIG_BLK_DEV_THROTTLING) += blk-throttle.o obj-$(CONFIG_IOSCHED_NOOP) += noop-iosched.o obj-$(CONFIG_IOSCHED_DEADLINE) += deadline-iosched.o obj-$(CONFIG_IOSCHED_CFQ) += cfq-iosched.o +obj-$(CONFIG_IOSCHED_BFQ) += bfq-iosched.o obj-$(CONFIG_BLOCK_COMPAT) += compat_ioctl.o obj-$(CONFIG_BLK_DEV_INTEGRITY)+= blk-integrity.o diff --git a/include/linux/cgroup_subsys.h b/include/linux/cgroup_subsys.h index 7b99d71..4e8c0ff 100644 --- a/include/linux/cgroup_subsys.h +++ b/include/linux/cgroup_subsys.h @@ -39,6 +39,10 @@ SUBSYS(net_cls) SUBSYS(blkio) #endif +#if IS_SUBSYS_ENABLED(CONFIG_CGROUP_BFQIO) +SUBSYS(bfqio) +#endif + #if IS_SUBSYS_ENABLED(CONFIG_CGROUP_PERF) SUBSYS(perf) #endif -- 1.9.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 0/2] Make TTY dependency for 8250 config fragments explicit
This patchset adds CONFIG_TTY to the cfg/8250 config fragment, as well as the common-pc-drivers config fragment; without it, the 8250 config options won't take effect if CONFIG_TTY defaults to 'n', as it does for things like 'tiny'. This is a fix for [YOCTO #6353] The following changes since commit 3c987080bc943b8eae37fb6672368bb74978e484: meta: features/ieee802154: add configuration fragment for IEEE 802.15.4 (2014-08-19 14:12:46 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/3.14-meta-add-tty-config http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=tzanussi/3.14-meta-add-tty-config Tom Zanussi (2): meta: Add CONFIG_TTY to 8250.cfg meta: Add CONFIG_TTY to common-pc-drivers.cfg meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers.cfg | 1 + meta/cfg/kernel-cache/cfg/8250.cfg| 1 + 2 files changed, 2 insertions(+) -- 1.8.3.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/2] meta: Add CONFIG_TTY to 8250.cfg
The 8250 config options aren't available if CONFIG_TTY isn't 'y', so make sure TTY is enabled for them. Signed-off-by: Tom Zanussi tom.zanu...@linux.intel.com --- meta/cfg/kernel-cache/cfg/8250.cfg | 1 + 1 file changed, 1 insertion(+) diff --git a/meta/cfg/kernel-cache/cfg/8250.cfg b/meta/cfg/kernel-cache/cfg/8250.cfg index 5a1cf7a..1aeb439 100644 --- a/meta/cfg/kernel-cache/cfg/8250.cfg +++ b/meta/cfg/kernel-cache/cfg/8250.cfg @@ -1,3 +1,4 @@ +CONFIG_TTY=y CONFIG_SERIAL_8250=y CONFIG_SERIAL_8250_CONSOLE=y CONFIG_SERIAL_8250_PCI=y -- 1.8.3.1 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
[linux-yocto] [PATCH 1/1] meta: common-pc: add support for booting via EFI
If common-pc actually means Common PC, this is appropriate, as EFI is pretty common in PCs these days. This is also the most expediant way to get qemux86 and qemux86-64 booting via EFI, which is a prerequisite for [YOCTO #5654]. Signed-off-by: Max Eliaser max.elia...@intel.com --- meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc | 2 ++ 1 file changed, 2 insertions(+) diff --git a/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc b/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc index 205ba0a..3c06890 100644 --- a/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc +++ b/meta/cfg/kernel-cache/bsp/common-pc/common-pc.scc @@ -4,6 +4,8 @@ kconf hardware common-pc-eth.cfg kconf hardware common-pc-gfx.cfg kconf hardware common-pc-wifi.cfg +include cfg/efi-ext.scc + include cfg/x86.scc include features/usb/ehci-hcd.scc include features/usb/uhci-hcd.scc -- 1.8.3.2 -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 1/2] yaffs: Avoid setting any ACL releated xattr
On 2014-08-27, 1:34 AM, Zhang Xiao wrote:
YAFFS doesn't sopport ACL yet, it must refuse any related settings.
I've grabbed these two patches and staged them for my next updates.
Thanks!
Bruce
Signed-off-by: Zhang Xiao xiao.zh...@windriver.com
---
fs/yaffs2/yaffs_vfs.c | 6 ++
1 file changed, 6 insertions(+)
diff --git a/fs/yaffs2/yaffs_vfs.c b/fs/yaffs2/yaffs_vfs.c
index 13de856..d372a4e 100644
--- a/fs/yaffs2/yaffs_vfs.c
+++ b/fs/yaffs2/yaffs_vfs.c
@@ -931,6 +931,12 @@ static int yaffs_setxattr(struct dentry *dentry, const
char *name,
yaffs_trace(YAFFS_TRACE_OS, yaffs_setxattr of object %d, obj-obj_id);
+ /* Currently we don't support posix ACL so never accept any settings
+* start with system.posix_acl_.
+*/
+ if (strncmp(name, system.posix_acl_, 17))
+ error = -EOPNOTSUPP;
+
if (error == 0) {
int result;
dev = obj-my_dev;
--
___
linux-yocto mailing list
linux-yocto@yoctoproject.org
https://lists.yoctoproject.org/listinfo/linux-yocto
Re: [linux-yocto] [PATCH 0/2] Make TTY dependency for 8250 config fragments explicit
On 2014-08-27, 10:38 AM, Tom Zanussi wrote: This patchset adds CONFIG_TTY to the cfg/8250 config fragment, as well as the common-pc-drivers config fragment; without it, the 8250 config options won't take effect if CONFIG_TTY defaults to 'n', as it does for things like 'tiny'. Thanks Tom. I've staged this for 3.10, 3.14 and -dev. It'll get pushed out tomorrow with the rest of my updates. Bruce This is a fix for [YOCTO #6353] The following changes since commit 3c987080bc943b8eae37fb6672368bb74978e484: meta: features/ieee802154: add configuration fragment for IEEE 802.15.4 (2014-08-19 14:12:46 -0400) are available in the git repository at: git://git.yoctoproject.org/linux-yocto-contrib.git tzanussi/3.14-meta-add-tty-config http://git.yoctoproject.org/cgit/cgit.cgi/linux-yocto-contrib/log/?h=tzanussi/3.14-meta-add-tty-config Tom Zanussi (2): meta: Add CONFIG_TTY to 8250.cfg meta: Add CONFIG_TTY to common-pc-drivers.cfg meta/cfg/kernel-cache/bsp/common-pc/common-pc-drivers.cfg | 1 + meta/cfg/kernel-cache/cfg/8250.cfg| 1 + 2 files changed, 2 insertions(+) -- ___ linux-yocto mailing list linux-yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/linux-yocto
