Well I'm not sure if it's RCN camped out too close to the eggnog or me
sitting too close to the mulled wine, but happy holidays regardless!  :)

Seriously, the issues with the BeagleBone and kernels goes back to
before the Linus device-tree rant:

http://article.gmane.org/gmane.linux.ports.arm.omap/55060

...and the 'Bone community (and the rest of the ARM ecosystem) has been
trying to deal with the fall-out ever since.

I think with the conversion to using device-tree, and the acceptance of
device-tree changesets into mainline, things are _finally_ going to
stabilize (fingers crossed!), but there's still probably a bit of churn
we'll have to live through for the near term.

As the Chinese curse goes: "May you live in interesting times"!

On 12/27/2014 7:10 PM, Thorsten von Eicken wrote:
> Thanks for the links! Much preferred over Robert's sarcasm. I know I'm not 
> part of the BBB's "in" crowd. I don't have time for it, however interesting 
> it is. I want to buy BBBs and use them and if I can't use them, I will buy 
> something else, as simple as that...
> 
> On Saturday, December 27, 2014 2:36:33 PM UTC-8, Charles Steinkuehler wrote:
>>
>> On 12/27/2014 4:15 PM, Robert Nelson wrote: 
>>> On Fri, Dec 26, 2014 at 5:55 PM, Thorsten von Eicken 
>>> <[email protected] <javascript:>> wrote: 
>>>> On Wednesday, December 10, 2014 5:53:42 AM UTC-8, RobertCNelson wrote: 
>>>>>
>>>>> I'm not really planning to document v3.14.x further, as something 
>>>>> special is planned to be merged for v3.19-rc1. (if your following the 
>>>>> device-tree mainline list) 
>>>>
>>>> Can you kindly point me to any info about what 3.19 is going to bring? 
>>>> Thanks! 
>>>
>>> Where's the fun in that! ;) It's what "everyone" has been bugging me 
>>> about personally and on this list for over a year. ;) if you can't 
>>> find it on the device-tree mailing list, you "didn't" want it bad 
>>> enough!!! ;) 
>>>
>>> (Sarcasm!!! ;)) 
>>
>> A late holiday present, since RCN seems to be camped out a bit too close 
>> to the eggnog!  :) 
>>
>> It's device-tree changesets.  This is basically what cape manager was 
>> trying to do, but with the full support of the kernel developers behind 
>> it which will hopefully result in fewer kernel crashes!  :) 
>>
>> ...some links to get you started: 
>>
>>
>> http://beagleboard.org/blog/2014-08-27-device-tree-overlay-support-lands-upstream/
>>  
>>
>>
>> http://lxr.free-electrons.com/source/Documentation/devicetree/changesets.txt 
>>
>> -- 
>> Charles Steinkuehler 
>> [email protected] <javascript:> 
>>
> 


-- 
Charles Steinkuehler
[email protected]

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to