Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-07 Thread Henrik Nordström
fre 2013-06-07 klockan 09:02 +0100 skrev luke.leighton: > ok. so. we come back to the question again: what shall i propose to > them that they consider doing, and what benefit would it be to them to > do so? Just tell them that the kernel is moving to a different configuration syntax called De

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-06 Thread Henrik Nordström
tor 2013-06-06 klockan 13:22 +0100 skrev luke.leighton: > idea: hook into devicetree gpio functions to allow script-fex gpio functions to gain access in a separate module? that sort of thing. No. Drop FEX from the kernel, use DT. There is no reason why the kernel shold care about the FEX format

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-06 Thread Henrik Nordström
tor 2013-06-06 klockan 13:19 +0100 skrev luke.leighton: > mass-volume tablet, mass-volume IPTV box. android OS, nothing else. Which still includes a number of possible configurations with different i2c, spi, usb etc devices connected on the board. Because Allwinner is not using mainline methods

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 23:20 +0100 skrev luke.leighton: > ok: great. so we have something that i can potentially propose to > them. now: what reason can i give that they should accept this? > what's the biggest incentive for them, here, to make these changes? > what would they gain? Mainly a

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
tor 2013-06-06 klockan 00:54 +0100 skrev luke.leighton: > > Not really the case. Actually the opposite. DT have this as well, and > > integrated in device probing. Allwinner need to hack every driver used > > to add their gpio requests to have pinmuxing triggered. > > augh. ok. solutions. wha

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
tor 2013-06-06 klockan 00:52 +0100 skrev luke.leighton: > > How is the Allwinner kernel going to load the driver for the pca9532? > > The mainline pca9532 driver does not understand fex so it can't read > > the necessary initialization data. > > jon: you're immediately outside of the target marke

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
tor 2013-06-06 klockan 00:26 +0100 skrev luke.leighton: > no john - they've only added it to the multiplexed sections of the > drivers which they themselves have written. such as > drivers/usb/sun{N}i_usb/*.[ch], drivers/block/nand/sun{N}_i, > arch/arm/mach-sun{N}i and so on. And a number of SP

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 16:54 -0600 skrev Stephen Warren: > 1) Put all the parameters in the U-Boot configuration header. This is > normal. Yes, we do so today for U-Boot SPL. But this won't fit very well with the Allwinner ODM workflow where one binary image works on a wide range of board configu

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 22:15 +0100 skrev Luke Kenneth Casson Leighton: > what we do not want to happen is that they see upstream patches being > submitted, they merge them into their internal tree (which to date has > had zero upstream changes: they're currently only just getting round > to doing

Re: [Arm-netbook] getting allwinner SoC support upstream (was Re: Uploading linux (3.9.4-1))

2013-06-05 Thread Henrik Nordström
ons 2013-06-05 klockan 22:24 +0100 skrev Luke Kenneth Casson Leighton: > And Then Some, stephen. there are two versions of u-boot being used: > one is the community-assembled [GPL-compliant] one, and the other > includes a [as-of-a-few-days-ago-but-no-longer, yay!] > formerly-GPL-violating one f