All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Bas Mevissen" <abuse@basmevissen.nl>
To: Andrey Zhizhikin <andrey.z@gmail.com>
Cc: Otavio Salvador <otavio.salvador@ossystems.com.br>,
	Terry Barnaby <terry@beam.ltd.uk>,
	meta-freescale@lists.yoctoproject.org
Subject: Re: [meta-freescale] imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx?
Date: Thu, 25 Feb 2021 13:55:15 +0100	[thread overview]
Message-ID: <78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl> (raw)
In-Reply-To: <CAHtQpK4iOyjz027pBiLQrwKkztQS64Anfpxm26A=16WB7SNWUw@mail.gmail.com>

On 2021-02-25 13:32, Andrey Zhizhikin wrote:
> Hello Bas,
> 
> On Thu, Feb 25, 2021 at 1:18 PM Bas Mevissen <abuse@basmevissen.nl> 
> wrote:
>> 
>> On 2021-02-25 12:21, Otavio Salvador wrote:
>> > Em qui., 25 de fev. de 2021 às 06:53, Terry Barnaby
>> > <terry@beam.ltd.uk> escreveu:
>> >>  From what I am seeing I will have to use a NXP fsl-* based
>> >> distribution
>> >> to support the imx hardware video processing features. I have built
>> >> such
>> >> a distro with both linux-fslc-imx and limux-imx kernels (I think!) for
>> >> the Wandboard, which boots and runs but the HDMI display was not
>> >> functional. I will persevere looking at that.
>> >
>> > No, you don't. You can use linux-fslc (mainline) and fslc-* distros as
>> > i.MX6 has full mainline support. At O.S. Systems we have been using
>> > Linux mainline with many customers with great success.
>> >
>> 
>> Wouldn't make sense to first evaluate the performance of the platform
>> (as Terry plans to do) first on an NXP fsl-* distro? In that case one
>> can get direct support from NXP if required. After that, derive your 
>> own
>> distro from fslc-*.
> 
> This might not be quite indicative, as the NXP kernel might have some
> "shortcuts" to boost performance in certain areas, sacrificing
> conformance of the source code.
> 

At least you get an idea of what the HW platform can do.

> You might experience the situation that video performs quite well, but
> then after opting for NXP kernel - you might find that some other
> areas are not working as expected (some other domains). This would put
> you in a situation that you've already committed to choose and deploy
> the NXP-based BSP and would leave you to solve the issues in those
> domains on your own efforts.
> 
> This is my pure speculation here, so take it with a grain of salt 
> though. :)
> 
IMHO, you should never base your *product* on FSL. It is (at least, that 
is what was told me by (then) Freescale field engineers) only there to 
demonstrate the platform. Maybe that has changed over time.

When there is a huge performance difference between fsl and fslc, it 
needs to be resolved.

> IMHO, this should be considered and before the final product receives
> commitment to use either of BSP flavors - all areas should be
> validated, not only the performance aspects of Multimedia domain.
> 

Yes, when you have decided on the hardware to use. If you are evaluating 
the hardware to see whether it meets your requirements, you might want 
to take the option that gives you the best impression of the performance 
that can be achieved without too much of a hassle.
(it is an important step to do, at a stage of the development where time 
is usually very limited, so you want a quick but reliable result).

>> 
>> BTW Would kernel.org stable kernel work as well on i.MX6 if you need
>> graphics and video? I used it successfully for headless IOT
>> applications.
> 
> As Fabio already indicated - this is possible.
> 

Fabio said "mainline". I'm not sure whether meant linux-fslc (as Otavio 
used it) or kernel.org.
So I wanted to check that.

>> 
>> Bas.
>> 
> 
> --
> Regards,
> Andrey.
> 
> 
> 

  reply	other threads:[~2021-02-25 12:55 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25  8:40 imx6dl dunfell and kernel: linux-fslc or linux-fslc-imx? Mauro Ziliani
2021-02-25  8:47 ` [meta-freescale] " Andrey Zhizhikin
2021-02-25  9:00   ` Terry Barnaby
2021-02-25  9:29     ` Andrey Zhizhikin
2021-02-25  9:53       ` Terry Barnaby
2021-02-25 11:21         ` Otavio Salvador
2021-02-25 11:50           ` Terry Barnaby
2021-02-25 12:24             ` Andrey Zhizhikin
2021-02-25 12:18           ` Bas Mevissen
2021-02-25 12:32             ` Andrey Zhizhikin
2021-02-25 12:55               ` Bas Mevissen [this message]
2021-02-25 13:01                 ` Fabio Estevam
2021-02-25 13:12                   ` Bas Mevissen
2021-02-25 13:04                 ` Andrey Zhizhikin
2021-02-25 13:22                   ` Bas Mevissen
2021-02-25 14:00                     ` Andrey Zhizhikin
2021-02-26  9:36                       ` eremenok.k.by
2021-02-26 10:03                         ` Bas Mevissen
2021-02-26 10:16                           ` Константин Еременок
2021-02-25 11:47       ` Fabio Estevam
2021-02-25 11:57         ` Terry Barnaby
2021-02-25 12:02           ` Fabio Estevam
2021-02-26 10:26             ` Terry Barnaby
2021-02-26 11:27               ` Bas Mevissen

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=78459aa4ec6360c05752a8bc1d44eac5@basmevissen.nl \
    --to=abuse@basmevissen.nl \
    --cc=andrey.z@gmail.com \
    --cc=meta-freescale@lists.yoctoproject.org \
    --cc=otavio.salvador@ossystems.com.br \
    --cc=terry@beam.ltd.uk \
    /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.