linux-kernel - Re: [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4

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]

Date:	Thu, 06 Jun 2013 10:03:42 +0400
From:	Aida Mynzhasova <aida.mynzhasova@...tlab.ru>
To:	Paul Walmsley <paul@...an.com>
CC:	linux-omap@...r.kernel.org, tony@...mide.com,
	linux@....linux.org.uk, linux-arm-kernel@...ts.infradead.org,
	linux-kernel@...r.kernel.org
Subject: Re: [PATCH 0/5] Broken DM816x support in Linux 3.10-rc4

On 06.06.2013 07:54, Paul Walmsley wrote:
> здравствуйте,
>
> On Wed, 5 Jun 2013, Aida Mynzhasova wrote:
>
>> Not so long ago I tried to boot Linux 3.10-rc4 kernel on DM816x EVM
>> board. Unfortunately, my attempts were failed by reason of poor
>> support of DM81xx-based devices in new kernels.
>
> Yeah, TI pretty much gave up on trying to get support for that chip
> upstream a few years ago.  Same for DM814x.
>
>> So, I suggest you this patch series, which fixes that kernel crush and
>> adds new functions/structures, required for early initialization on
>> DM816x (power and clock domains, hwmods). After applying these patches
>> the kernel is able to successfully continue booting till clock
>> initialization (will be added later).
>
> OK, it will be great to get my DM8168EVM booting on mainline.  But there
> are a few preliminary issues with the patches:
>
> 1. All new chip and board support needs to be DT-only.  So, no new board
> files.  Also, all the hwmod data shouldn't have IRQ, DMA, etc. data - that
> should come from DT.  See for example the recently posted patch "[PATCH
> 13/14] ARM: AM33XX: hwmod data: irq, dma and addr info clean up"
>
> 2. Looks like patch 2 is missing from the list.  If it's too big for the
> list, please break it down into smaller patches.
>
> 3. Did you write this code and data, hwmods, etc., or did it come from a
> TI kernel?  Please note this clearly in the patch descriptions.
>
>
> - Paul
>

Hi!

Thanks for reply!
ok, I'll rewrite code by means of DT and add some additional notes to 
patch description.

Aida.
--
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/