[meta-freescale] [meta-fsl-arm][PATCH 3/3] imx6qsabrelite/defconfig: Enable devtmpfs
eric.nelson at boundarydevices.com
Fri Dec 21 11:12:18 PST 2012
On 12/21/2012 11:41 AM, Otavio Salvador wrote:
> On Fri, Dec 21, 2012 at 4:37 PM, Eric Nelson
> <eric.nelson at boundarydevices.com> wrote:
>> On 12/21/2012 10:19 AM, Otavio Salvador wrote:
>>> On Fri, Dec 21, 2012 at 2:25 PM, Gary Thomas <gary at mlbassoc.com> wrote:
>>>> Recent versions of udev (182 in OE-core) need devtmpfs to operate
>>>> Signed-off-by: Gary Thomas <gary at mlbassoc.com>
>>> Merged to master with reworded commit log and bump PR.
>> Hi Otavio,
>> I have a configuration patch to make, adding CONFIG_FEC_NAPI.
>> Should I submit it with a bump in PR as you did, or without, so
>> that you can coordinate that?
> Please do it with bump in PR so it is easier for me.
>> The patch itself is to prevent network performance from cratering
>> under load as discussed in this blog post:
>> And in this patch:
>> Without it, network receive performance can get really bad under
> Very nice! However you might like to simply sync the patch for your
> boundary tree (the patch compares FSL branch with Bondary ones) so
> this would be included. Or this should be applied in all boards?
Well... I was thinking that I'd just push this one, since it has a much
bigger impact than the patches we made to flow control and error
I think I was a bit mistaken though. I didn't catch that this line was
itself in a patch file:
+# CONFIG_FEC_NAPI is not set
I also didn't catch and don't quite understand how the defconfig file
is applied in the build process. Is 'nitrogen6x_defconfig' even used?
I don't see CONFIG_FEC in the defconfig. Does that file somehow get
applied on top of a base configuration to apply Yocto specifics?
There are some things in our boundary-L3.0.35_12.09.01_GA tree that
I was hoping to clean up before submitting
In particular, we set things up to allow a single image to boot on
Quad->Solo that the Freescale team didn't like, so we'll probably
revert it as we migrate to the 2012-10 branch, which will take a
couple of weeks.
I'm not really sure how to proceed.
More information about the meta-freescale