All of lore.kernel.org
 help / color / mirror / Atom feed
From: Eric Nelson <eric.nelson@boundarydevices.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: "meta-freescale@yoctoproject.org" <meta-freescale@yoctoproject.org>
Subject: Re: [meta-fsl-arm][PATCH 3/3] imx6qsabrelite/defconfig: Enable devtmpfs
Date: Fri, 21 Dec 2012 12:12:18 -0700	[thread overview]
Message-ID: <50D4B492.8020401@boundarydevices.com> (raw)
In-Reply-To: <CAP9ODKqo20xYSoKuVE3AhLxRAHnrvrOZzK5hwPf63pp67qA30g@mail.gmail.com>

On 12/21/2012 11:41 AM, Otavio Salvador wrote:
> On Fri, Dec 21, 2012 at 4:37 PM, Eric Nelson
> <eric.nelson@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@mlbassoc.com> wrote:
>>>>
>>>> Recent versions of udev (182 in OE-core) need devtmpfs to operate
>>>> correctly
>>>>
>>>> Signed-off-by: Gary Thomas <gary@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:
>>          http://boundarydevices.com/i-mx6-ethernet/
>>
>> And in this patch:
>>
>> https://github.com/boundarydevices/linux-imx6/commit/38d622938f1352a6550a5e38c624b46b6929439f
>>
>> Without it, network receive performance can get really bad under
>> load.
>
> 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
handling.

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.

Please advise,


Eric


  reply	other threads:[~2012-12-21 19:12 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-21 16:25 [meta-fsl-arm][PATCH 0/3] SabreLite updates Gary Thomas
2012-12-21 16:25 ` [meta-fsl-arm][PATCH 1/3] xf86-video-imxfb-vivante: Update for new X server API Gary Thomas
2012-12-21 16:46   ` Daiane Angolini
2012-12-21 17:25     ` Andrei Gherzan
2012-12-21 16:25 ` [meta-fsl-arm][PATCH 2/3] xserver-xf86-config: SabreLite configuration Gary Thomas
2012-12-21 16:50   ` Daiane Angolini
2012-12-21 16:52     ` Gary Thomas
2012-12-21 17:16   ` Otavio Salvador
2012-12-21 17:22     ` Gary Thomas
2012-12-21 17:26       ` Otavio Salvador
2012-12-21 16:25 ` [meta-fsl-arm][PATCH 3/3] imx6qsabrelite/defconfig: Enable devtmpfs Gary Thomas
2012-12-21 16:51   ` Daiane Angolini
2012-12-21 17:25     ` Andrei Gherzan
2012-12-21 17:19   ` Otavio Salvador
2012-12-21 18:37     ` Eric Nelson
2012-12-21 18:41       ` Otavio Salvador
2012-12-21 19:12         ` Eric Nelson [this message]
2012-12-21 19:24           ` Otavio Salvador
2012-12-21 20:06             ` Eric Nelson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=50D4B492.8020401@boundarydevices.com \
    --to=eric.nelson@boundarydevices.com \
    --cc=meta-freescale@yoctoproject.org \
    --cc=otavio@ossystems.com.br \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.