<aswin_>
Duality: Did you follow the steps by RobertCNelson ? There may be some patches you are missing on the build.
<Duality>
aswin_: didn't know that
<Duality>
I'll look at it thanks
<Duality>
!
<zmatt>
Duality: have you tried rcn's kernel package instead of building a kernel from source?
<zmatt>
Duality: I'm seeing a ton of problems here
<zmatt>
the gpio controllers fail to register, the pinmux controller fails to probe
<zmatt>
so nothing will work
<Duality>
zmatt: yea tons of errors indeed :)
<Duality>
I figured if i build from source it would work
<zmatt>
Duality: I see you're using a custom device tree "KITT Engineering YIN2.X AM335x(4.19 Kernel)" ... there's been huge DT changes between 4.19 and 5.x
<Duality>
ah man
<Duality>
really?
<zmatt>
though most of them are in the am33xx.dtsi hence should be fixable by recompiling
<zmatt>
actually no, that's not entirely true
<Duality>
oh alright :)
<Duality>
well figuring out the device tree isn't the hardest thing to do
<zmatt>
(alternatively you could probably just revert that change)
aswin has joined #beagle
aswin_ has quit [Ping timeout: 264 seconds]
set_ has joined #beagle
<set_>
I made it!
<zmatt>
hurray?
<set_>
Oh!
<set_>
Hey and hello.
<set_>
This is a new start of something neat. Good on you, guys.
<set_>
Poor Freenode...it will never be the same.
<zmatt>
I wouldn't call this a "new start", it's just a move
<set_>
Oh. Okay. Movin' on up!
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
set_ has quit [Remote host closed the connection]
set_ has joined #beagle
aswin has quit [Quit: Lost terminal]
set_ has quit [Ping timeout: 264 seconds]
<GenTooMan>
that awkward moment of silence broken.
<GenTooMan>
why did Intel create yocto? It is a bit too complicated to use. Ugh.
<zmatt>
it doesn't seem like they did? "The project was announced by the Linux Foundation in 2010 and launched in March, 2011, in collaboration with 22 organizations, including OpenEmbedded."
<zmatt>
ah because the project architect was an Intel employee previously on "long term loan" to the Linux Foundation... that still doesn't sound quite the same as Intel "creating" yocto
<Duality>
anyone got experience making kernel images smaller ? (this is just a curiosity and a fun quest i am on right now :)
<zmatt>
Installed-Size: 17538
<zmatt>
that's not intensely stripped or anything, but still considerably smaller than rcn's packages
<zmatt>
I don't really care about the disk space used, I did it mainly to reduce compile time and reducing the size of the kernel image itself (as opposed to the total package size including modules) also helps with boot time
<zmatt>
my vmlinuz is 3.9M
<GenTooMan>
zmatt, I'm complaining mostly because of a yocto build for the RPI I would like to migrate to the beagle board series.
<Duality>
zmatt: that is awesome :)
<Duality>
mostely doing it to learn a bit more about the linux kernel configuration side and what it consists of (there is a lot in a kernel lol)
<GenTooMan>
Duality, yes the linux kernel is not a micro kernel design. fortunately the module system allows wider support without loading every possible driver into the kernel or just the drivers for the system. USB made this a necessary thing.
<zmatt>
Duality: going through the kernel config options is quite a journey
<zmatt>
though a nice side-effect of going through it is that you might discover cool features you didn't even know the kernel had (at least I did)