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: <87h9tc6pd8.fsf@free.fr>
Date:	Mon, 23 Mar 2015 10:21:23 +0100
From:	Robert Jarzmik <robert.jarzmik@...e.fr>
To:	Arnd Bergmann <arnd@...db.de>
Cc:	linux-arm-kernel@...ts.infradead.org,
	Vinod Koul <vinod.koul@...el.com>,
	Jonathan Corbet <corbet@....net>,
	Daniel Mack <daniel@...que.org>,
	Haojian Zhuang <haojian.zhuang@...il.com>,
	dmaengine@...r.kernel.org, linux-kernel@...r.kernel.org,
	linux-doc@...r.kernel.org
Subject: Re: [PATCH 0/5] Driver for pxa architectures

Arnd Bergmann <arnd@...db.de> writes:

> On Saturday 21 March 2015, Robert Jarzmik wrote:
>> It is as well one of the last steps (or so I hope) for pxa architure to be part
>> of the multiplatform ARM architecture, and at the same time keep its legacy
>> platforms operational. It will kill arch/arm/plat-pxa/dma.c in the long term.
>> 
>
> Hi Robert,
>
> as much as I like this series, I think you still have a long way to go before
> PXA can really be multiplatform. Other parts that would need to be solved
> include the various cpu_is_pxa*() checks in drivers, the per-board header
> files, the way that the I/O space is mapped in the PCMCIA drivers and
> the XIP support.
Ah yes, now you mention it ...  And still that doesn't frighten me that much,
and certainly much less than clocks or dma stuff. Only the headers might be
troublesome, and pxafb will certainly be a big rework, but that's for the next
step :)

As for the per-board header files, as long as they're used only within mach-pxa
and not outside (ie. not in drivers) I must admit I don't see what might be a
problem.

As for XIP support, I don't have a clear view if it's a requirement for
multiplatform nor if it works in these builds.

> I think all of them are theoretically doable, but I wasn't expecting
> to ever get there.
Well, that makes me a goal to reach, doesn't it ? I'll stick to optimism here,
and we'll see within a year how far I manage to go :)

Cheers.

-- 
Robert
--
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ