On Fri, Dec 11, 2020 at 5:56 PM Ioana Ciornei wrote:
>
> On Fri, Dec 11, 2020 at 04:29:14PM +, Daniel Thompson wrote:
> > On Fri, Dec 11, 2020 at 02:01:28PM +, Ioana Ciornei wrote:
> > > On Thu, Dec 10, 2020 at 08:06:36PM +0200, Ioana Ciornei wrote:
> > > > [Added also the netdev mailing
On Thu, Dec 10, 2020 at 7:08 PM Ioana Ciornei wrote:
>
> [Added also the netdev mailing list, I haven't heard of linux-netdev
> before but kept it]
>
> On Thu, Dec 10, 2020 at 05:31:56PM +, Daniel Thompson wrote:
> > Hi Ioana
>
> Hi Daniel,
>
> >
> > On Mon, Jun 29, 2020 at 06:47:11PM +,
On Mon, Dec 7, 2020 at 7:12 PM Robin Murphy wrote:
>
> On 2020-12-02 10:29, Laurentiu Tudor wrote:
> > Hi Robin,
> >
> > Sorry for the late reply, we had a few days of over here. Comments inline.
> >
> > On 11/25/2020 8:10 PM, Robin Murphy wrote:
> >> On 2020-11-25 15:50, laurentiu.tu...@nxp.com
On Mon, Jul 27, 2020 at 6:16 PM Alexandre Belloni
wrote:
>
> On 27/07/2020 17:55:50+0200, Jon Nettleton wrote:
> > > So, can we please have that discussion, it is pertinent to this patch.
> > >
> >
> > Thinking about this some more, I believe whether or not an
On Mon, Jul 27, 2020 at 5:43 PM Russell King - ARM Linux admin
wrote:
>
> On Mon, Jul 27, 2020 at 05:41:04PM +0200, Alexandre Belloni wrote:
> > On 27/07/2020 16:24:39+0100, Russell King - ARM Linux admin wrote:
> > > On Mon, Jul 27, 2020 at 04:49:38PM +0200, Alexandre Belloni wrote:
> > > > On
On Mon, Jul 27, 2020 at 4:17 PM Russell King - ARM Linux admin
wrote:
>
> On Mon, Jul 27, 2020 at 03:33:17PM +0200, Jon Nettleton wrote:
> > On Mon, Jul 27, 2020 at 11:46 AM Russell King - ARM Linux admin
> > wrote:
> > >
> > > On Thu, Jul 23, 2020 at 09:57
On Mon, Jul 27, 2020 at 11:46 AM Russell King - ARM Linux admin
wrote:
>
> On Thu, Jul 23, 2020 at 09:57:55PM +0200, Alexandre Belloni wrote:
> > On 23/07/2020 11:49:05-0600, Rob Herring wrote:
> > > On Mon, Jul 20, 2020 at 12:23:59PM +0100, miguelborgesdefrei...@gmail.com
> > > wrote:
> > > >
On Thu, Jul 23, 2020 at 10:41 PM Miguel Borges de Freitas
wrote:
>
> Hi Alexandre,
>
> Having a way to dynamically change the configuration would definitely
> be helpful in most cases. I decided to go with a DT property because
> in the case this patch tries to solve (the cubox-i) there isn't
On Fri, Jan 4, 2019 at 8:57 PM Andreas Kemnade wrote:
>
> Hi Marcel,
>
> On Fri, 4 Jan 2019 10:07:34 +0100
> Marcel Holtmann wrote:
>
> > Hi Andreas,
> >
> > Btw. I see nothing standing in the way of merging btuart.c driver and
> > then go from there. Either I dig this out and submit
On Sun, Apr 29, 2018 at 3:47 PM, Paul Kocialkowski wrote:
> Hi,
>
> Le dimanche 22 avril 2018 à 19:22 +0200, Paul Kocialkowski a écrit :
>> Are all CuBox-i units that have ever been sold supposed to have a
>> connector with a CD line? I find it hard to believe that it's broken
On Sun, Apr 29, 2018 at 3:47 PM, Paul Kocialkowski wrote:
> Hi,
>
> Le dimanche 22 avril 2018 à 19:22 +0200, Paul Kocialkowski a écrit :
>> Are all CuBox-i units that have ever been sold supposed to have a
>> connector with a CD line? I find it hard to believe that it's broken
>> specifically on
On Thu, Nov 5, 2015 at 7:43 AM, Jean-Michel Hautbois
wrote:
>
> Le 5 nov. 2015 05:23, "Jon Nettleton" a écrit :
>>
>> On Wed, Nov 4, 2015 at 8:33 PM, Jean-Michel Hautbois
>> wrote:
>> > 2015-11-04 18:04 GMT+01:00 Jon Nettleton :
>> >&g
On Wed, Nov 4, 2015 at 8:33 PM, Jean-Michel Hautbois
wrote:
> 2015-11-04 18:04 GMT+01:00 Jon Nettleton :
>> On Wed, Nov 4, 2015 at 5:52 PM, Jean-Michel Hautbois
>> wrote:
>>> Hi !
>>>
>>> I can see in FSL kernel that VPU is configurable to 352M (it
On Wed, Nov 4, 2015 at 5:52 PM, Jean-Michel Hautbois
wrote:
> Hi !
>
> I can see in FSL kernel that VPU is configurable to 352M (it defaults
> at 264MHz in mainline I think).
> In the TRM, it is even specified at 352MHz as a default frequency,
> with a maximum of 540MHz.
>
> Would it be possible
On Wed, Nov 4, 2015 at 8:33 PM, Jean-Michel Hautbois
<jean-michel.hautb...@veo-labs.com> wrote:
> 2015-11-04 18:04 GMT+01:00 Jon Nettleton <jon.nettle...@gmail.com>:
>> On Wed, Nov 4, 2015 at 5:52 PM, Jean-Michel Hautbois
>> <jean-michel.hautb...@veo-labs.com>
On Thu, Nov 5, 2015 at 7:43 AM, Jean-Michel Hautbois
<jean-michel.hautb...@veo-labs.com> wrote:
>
> Le 5 nov. 2015 05:23, "Jon Nettleton" <jon.nettle...@gmail.com> a écrit :
>>
>> On Wed, Nov 4, 2015 at 8:33 PM, Jean-Michel Hautbois
>> <jean-michel
On Wed, Nov 4, 2015 at 5:52 PM, Jean-Michel Hautbois
wrote:
> Hi !
>
> I can see in FSL kernel that VPU is configurable to 352M (it defaults
> at 264MHz in mainline I think).
> In the TRM, it is even specified at 352MHz as a default frequency,
> with a maximum
On Fri, Aug 21, 2015 at 12:30 AM, Clemens Gruber
wrote:
> Hi,
>
> I am experiencing massive RX packet loss on my i.MX6Q (Chip rev 1.3) on Linux
> 4.2-rc7 with a Marvell 88E1510 Gigabit Ethernet PHY connected over RGMII.
> I noticed it when doing an UDP benchmark with iperf3. When sending UDP
On Fri, Aug 21, 2015 at 12:30 AM, Clemens Gruber
clemens.gru...@pqgruber.com wrote:
Hi,
I am experiencing massive RX packet loss on my i.MX6Q (Chip rev 1.3) on Linux
4.2-rc7 with a Marvell 88E1510 Gigabit Ethernet PHY connected over RGMII.
I noticed it when doing an UDP benchmark with iperf3.
Victoria,
I was hoping you would join the conversation. I know you have a
series of patches in Freescale's 3.14 git repository. Have you
updated those for mainline and published them for review and inclusion
in the upstream kernel? If yes to any could you post a link?
-Jon
On Tue, Jun 16,
Victoria,
I was hoping you would join the conversation. I know you have a
series of patches in Freescale's 3.14 git repository. Have you
updated those for mainline and published them for review and inclusion
in the upstream kernel? If yes to any could you post a link?
-Jon
On Tue, Jun 16,
On Mon, Jun 15, 2015 at 5:59 PM, Steffen Trumtrar
wrote:
> Hi!
>
> I'm working on CAAM support for the ARM-based i.MX6 SoCs. The current
> drivers/crypto/caam driver only works for PowerPC AFAIK.
> Actually, there isn't that much to do, to get support for the i.MX6 but
> one patch breaks the
On Mon, Jun 15, 2015 at 5:59 PM, Steffen Trumtrar
s.trumt...@pengutronix.de wrote:
Hi!
I'm working on CAAM support for the ARM-based i.MX6 SoCs. The current
drivers/crypto/caam driver only works for PowerPC AFAIK.
Actually, there isn't that much to do, to get support for the i.MX6 but
one
23 matches
Mail list logo