<czr>
(as in, is there somewhere I could branch off easily)
<zrafa>
czr: yes, use OE and build jlime muffinman for nn. That should work
<czr>
cool. now if I only would understand even 50% of those words ;-).
<czr>
jlime muffinman is somekind compatible device?
<zrafa>
czr: do you want to build/develop OE or do you want to use a distribution OE based?
<czr>
ah, google is my friend.
<czr>
thanks zrafa
<zrafa>
if you just want to use an OE distro for nanonote use jlime
<czr>
well, I actually want to torture myself and use yocto to build something for the nano. probably replace the whole image in the process too
<czr>
yocto = poky4 = oe-derivative.
<czr>
zrafa, how does jlime relate to oe btw?
<czr>
(technically I mean)
<zrafa>
czr: jlime is part of OE, if you use OE you can find jlime there. Two jlime devs are working doing muffinman into OE. It is for several devices, nanonote as target as well
<czr>
nods
<czr>
I'm reading the docs as we speak.
<zrafa>
well, jlime is not part of OE, it is an independent project, but the distro muffinman is part of OE
<czr>
ah. so jlime is more of a "umbrella" project for various OE distros?
<czr>
various as in specific set of hp pdas and the nanonote.
<zrafa>
for serveral devices, mainly HP Jornadas
<czr>
nods
<czr>
I wish I either had 5 clones of myself, or there'd be 5*24 hours for each day..
<B_Lizzard>
czr, jlime = angstrom as far as OE goes.
<B_Lizzard>
We are a distro using OpenEmbedded
<B_Lizzard>
Just like Angstrom can build opie-image, gpe-image, whatever-image for various devices using various kernels, so do we.