On Thu, 2012-11-29 at 09:46 +0200, Stefan Kristiansson wrote:

> That said, your master tree on openrisc.net has a lot of 'goodies'
> that aren't upstreamed (like drivers for SPI etc), so to bounce your
> question back at you, why aren't those upstreamed?

Yes, I'm aware that there's a couple of things lingering there:

i)  SPI driver is not upstreamable because the driver is not 'generic';
specifically, it relies on 'struct cpuinfo' for openrisc.  The fix for
this depends on reworking OpenRISC to use the common clock framework.  I
did this work about a month ago, but haven't had time to finish it off
and I think I won't push it until 3.9; but once that's done, the SPI
driver can go upstream.

ii)  There's a couple of patches for the ethernet driver (ethoc): these
aren't upstream due to... sloth!

iii)  What else?  The rest should be initramfs stuff and that's not
going upstream.

And while we're at it, there's other stuff floating around that needs
submitting.

i)  ORSoC hasn't submitted the devicetree for their dev-board despite
shipping a modified kernel for it for more than a year.  I haven't
checked what other modifications they've made, but there's no reason
this stuff should not be upstream.

ii)  We're missing the devicetree for AAC's OBC500.

iii)  There's a bunch of common/consumer boards in use for which there's
no reason not to provide a default upstream configuration and
devicetree.

iv)  ...and I know of several cores in use for which there are no
upstream drivers despite the users being "open source friendly".

> I know, I'm throwing stones in a glass house accusing you for
> throwing stones in a glass house, I have stuff like that laying around as
> well, consider it a bit 'tongue-in-cheek'.

What fun are stones if you can't throw them?  Fire away...!

> 
> But the fact remains, that's the tree that's easiest to "get going",
> that's what people are most likely going to use, not Torvalds tree.

Yes, and it's "stable"... since 3.4! ;)

/Jonas

_______________________________________________
Linux mailing list
[email protected]
http://lists.openrisc.net/listinfo/linux

Reply via email to