linux-kernel - Re: [PATCH v1 11/15] serial: imx: initialized DMA w/o HW flow enabled

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20150413080637.GA1537@breakpoint.cc>
Date:	Mon, 13 Apr 2015 10:06:37 +0200
From:	Sebastian Andrzej Siewior <sebastian@...akpoint.cc>
To:	jiwang <jiada_wang@...tor.com>
Cc:	gregkh@...uxfoundation.org, jslaby@...e.cz,
	linux-serial@...r.kernel.org, linux-kernel@...r.kernel.org,
	anton_bondarenko@...tor.com, dirk.behme@...bosch.com,
	bigeasy@...utronix.de
Subject: Re: [PATCH v1 11/15] serial: imx: initialized DMA w/o HW flow enabled

On Mon, Apr 13, 2015 at 04:40:15PM +0900, jiwang wrote:
> Hi Sebastian
Hi Jiada,

> >My question is how was this tested. Before your patch none of my boards
> >were using DMA because RTS/CTS is not in use and this was a key
> >requirement. Now SDMA goes crazy. Is there a SDMA firmware required for
> >this to work?
> We tested the patch set with our modified kernel tree,
> and I find upstream kernel is not building SDMA firmware,
> I will submit another patch to add it.

Please make sure it is tagged stable. There is no hint that this is required
and as of it now, it breaks v4.0.
One question, where do you have the firmware from? I picked the one from FSL's
v3.10 SDK and I ended up with FIFO-overflows so it was clearly the wrong one
(and the built-in SDMA firmware does not work as expected as you mentioned).

Is this firmware only required the imx6 series or also for older versions like
imx5?

> Thanks,
> Jiada

Sebastian
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/