linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: ben.dooks@codethink.co.uk (Ben Dooks)
To: linux-arm-kernel@lists.infradead.org
Subject: v3.10 - big endian core support
Date: Fri, 12 Jul 2013 13:33:27 +0100	[thread overview]
Message-ID: <51DFF797.8080100@codethink.co.uk> (raw)
In-Reply-To: <20130712140643.2a3f1c68@skate>

On 12/07/13 13:06, Thomas Petazzoni wrote:
> Dear Ben Dooks,
>
> On Fri, 12 Jul 2013 12:58:45 +0100, Ben Dooks wrote:
>
>>> Yeah, the Thumb2 code is not supported by Ben Dooks patches, it's part
>>> of the TODO-list. I think Ben said he would probably not have much time
>>> to work on this. I might be able to spare some time on this, so just
>>> let me know if I should start working on this. If I remember correctly,
>>> it's mainly the fixup_pv_table code that needed some Thumb2/BE love.
>>>
>>> Will, is getting Thumb2 working a requirement to get the BE support
>>> merged, or can we for now make the BE option depends on !THUMB2_KERNEL ?
>>
>> I would like to sort out getting this code merged as it seems to have
>> been tested by several people now outside Codethink.
>
> I briefly talked with Will this week at LCE, and apparently he was
> generally ok with the patches. He only mentioned that the series should
> be split between core ARM stuff (that goes through Russell's tree), and
> the platform-specific changes, that go through the different
> maintainers tree.

The 311/be/core series which was the first posted has a few machine
specific bits in it (vexpress, highbank and mvebu) but is mainly the
ARM core code and bits of peripheral specific support which still live
under arch/arm.

I left there there as they're fairly small patches and would tend to get
lost. I can remove these before asking RMK to pull the core support and
possibly the atag/boot-endian patches.

>> I could try doing the THUMB2 support, but I do not have a lot of
>> experience with building THUMB2 kernels.
>
> Ok. Let me know if you need some help. I'd really like to see this BE
> work make it into 3.12.

Thanks for the testing. I'll see if I can get some time in early next
week to re-test and send against 3.11-rc series.

-- 
Ben Dooks				http://www.codethink.co.uk/
Senior Engineer				Codethink - Providing Genius

  reply	other threads:[~2013-07-12 12:33 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CALicx6u89THSiRa4FzGZrcoG8q+o_BD8qVEC4CYXEjPUVK_fJw@mail.gmail.com>
2013-07-12 11:47 ` v3.10 - big endian core support Thomas Petazzoni
2013-07-12 11:56   ` Vijay Kilari
2013-07-12 12:00     ` Ben Dooks
2013-07-15  2:50       ` jgq516 at gmail.com
2013-07-15  6:15         ` Vijay Kilari
2013-07-12 11:58   ` Ben Dooks
2013-07-12 12:06     ` Thomas Petazzoni
2013-07-12 12:33       ` Ben Dooks [this message]
2013-07-14 21:53     ` Will Deacon
2013-07-15  8:03       ` Ben Dooks
2013-07-15  8:36         ` Thomas Petazzoni
2013-07-15  9:02           ` jgq516 at gmail.com
2013-07-15 10:26           ` Ben Dooks
2013-07-15 13:17             ` Thomas Petazzoni
2013-07-16  8:00             ` jgq516 at gmail.com
2013-07-16 10:38               ` Ben Dooks
2013-07-01 11:03 Ben Dooks
2013-07-01 14:33 ` Thomas Petazzoni
2013-07-01 15:20   ` Ben Dooks
2013-07-08  5:39 ` jgq516 at gmail.com
2013-07-08  8:49   ` Will Deacon
2013-07-08  9:51     ` jgq516 at gmail.com
2013-07-08 11:02       ` Will Deacon
2013-07-08 17:03         ` Will Deacon
2013-07-09  1:18           ` jgq516 at gmail.com
2013-07-09  3:34             ` jgq516 at gmail.com
2013-07-09  7:45               ` Will Deacon
2013-07-09  9:55                 ` jgq516 at gmail.com
2013-07-09 10:04                   ` jgq516 at gmail.com
2013-07-09 15:36           ` Thomas Petazzoni
2013-07-08  9:58   ` Ben Dooks
2013-07-08 10:03     ` jgq516 at gmail.com
2013-07-08 11:10       ` Ben Dooks
2013-07-09  9:53         ` jgq516 at gmail.com
2013-07-09  9:59           ` Ben Dooks

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=51DFF797.8080100@codethink.co.uk \
    --to=ben.dooks@codethink.co.uk \
    --cc=linux-arm-kernel@lists.infradead.org \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).