indy has quit [Ping timeout: 244 seconds]
indy has joined #linux-exynos
ssvb has quit [Ping timeout: 255 seconds]
afaerber_ has quit [Quit: Verlassend]
afaerber has joined #linux-exynos
afaerber has quit [Remote host closed the connection]
afaerber has joined #linux-exynos
James_T has quit [Ping timeout: 245 seconds]
James_T has joined #linux-exynos
James_T has quit [Ping timeout: 252 seconds]
James_T has joined #linux-exynos
ssvb has joined #linux-exynos
James_T has quit [Ping timeout: 252 seconds]
Tenkawa has joined #linux-exynos
<
Tenkawa>
greetings all
<
Tenkawa>
time for some more kernel fighting this morning
<
Wizzup>
what device do you have again?
<
Tenkawa>
chromebook 1 xe303c12
<
Wizzup>
I have mainline + some patches working on my snow at least
<
Tenkawa>
I've got 3.8.11 kernel's in 500 different varieties signed and working
<
Wizzup>
Ah, chromeos
<
Tenkawa>
I'd be happy with a newer chromeos tree kernel
<
Tenkawa>
3.8 is just ancient
<
Tenkawa>
and my 3.18 mainline attempts have been miserable failures
<
Tenkawa>
it boots however I get no video output
<
Wizzup>
if you ping me in ~6 hours I can see if I can send you my kernel / steps
<
Tenkawa>
thanks. I'll definitely try to d that
<
Tenkawa>
Wizzup: if there is a way to self sign and "not" use nv-uboot I'd prefer that
James_T has joined #linux-exynos
<
Tenkawa>
I've been signing all of my kernels and using standard boot procs
<
Wizzup>
well, you can do that if you prefer
<
Wizzup>
kernel stuff is similar
<
Wizzup>
I use nv-uboot though, for the record
<
Tenkawa>
yeah most people do..
<
Tenkawa>
I just figure if the signing is working why not use it
<
Tenkawa>
my goal today is to trim what I dont need out of my config
<
Wizzup>
I always start with the simplest ways: get to a point where it works, then complicate it
<
Wizzup>
and signing is a complication
<
Tenkawa>
oh... for me its all scripted to where the signing validates it all went ok
<
Tenkawa>
I just really dont like being stuck on such an old tree
<
Tenkawa>
especially with this being my main development box
<
Tenkawa>
I use it for all of my other arm devel work
<
Tenkawa>
mind you most of my work is on rpi's
<
Tenkawa>
and beaglebone;s
<
Tenkawa>
I still think that arm has so much potential that we havent even hit yet
James_T has quit [Ping timeout: 240 seconds]
Nemykal has quit [Ping timeout: 255 seconds]
Tenkawa has quit [Quit: leaving]
James_T has joined #linux-exynos
Tenkawa has joined #linux-exynos
ssvb has quit [Ping timeout: 245 seconds]
<
Tenkawa>
lets see if the 3.14 branch works
<
javier__>
Tenkawa: the chromeos-3.14 branch on Snow?
<
Tenkawa>
javier__: yeah
<
javier__>
Tenkawa: that won't work
<
Tenkawa>
oh why not?
<
Tenkawa>
is there one specific thing that breaks it?
<
javier__>
Tenkawa: none of the platform support from 3.8 is in the other branches
<
javier__>
Tenkawa: so what you will have is the mainline support that was in 3.14 which is almost nothing
<
Tenkawa>
well darn
<
javier__>
Tenkawa: if your goal is to use a newer kernel then linux-next + some posted patches is your only option
<
Tenkawa>
I just need to say forget their src completely and get mainline 3.18 working however I really don't want to use nv-uboot
Nemykal has joined #linux-exynos
<
Tenkawa>
missed that branch completely
<
Tenkawa>
let me go do some investigating
<
javier__>
Tenkawa: you don't need nv-uboot, although is more convenient imho
<
Tenkawa>
I thought I read I "had" to use it because of the fb if I wanted to use mainline
<
javier__>
Tenkawa: no, you need to use it if you want to use simplefb so the kernel uses the framebuffer setup by the bootloader
<
javier__>
Tenkawa: but linux-next already have the patches that adds proper kms/drm support for Snow
<
Tenkawa>
I'm looking in linux-next now
<
Tenkawa>
which tag should I use
<
Tenkawa>
they appear to almost/match up with the non-next one
<
Tenkawa>
at least from just browsing
<
Tenkawa>
chromiumos/third_party/kernel-next says dead on the chromium git descrips
<
javier__>
Tenkawa: I meant git://git.kernel.org/pub/scm/linux/kernel/git/next/linux-next.git
<
javier__>
display and wifi support for Snow are not in 3.19 but are in linux-next
<
Tenkawa>
oh thats better
<
Tenkawa>
thank you
<
Tenkawa>
now time for clone and reconfig again
<
Tenkawa>
haahaaahaa
<
Tenkawa>
javier__: is there a good defconfig or do I have to get in there and piece it together?
<
Tenkawa>
if theres a defconfig I'll start there and tweak as I go
<
Tenkawa>
my checkout is almost done
<
Tenkawa>
er clonw rather
* Tenkawa
notes this brings back memory of his first kernel builds back in 1994
<
Tenkawa>
heheheheh
<
Tenkawa>
oh an devicetree..
<
Tenkawa>
which dts should I use?
<
Tenkawa>
nm found it
<
Wizzup>
find arch/arm/boot/ | grep snow ;-)
<
Tenkawa>
Wizzup: some of the trees had multiple snow versions
<
Tenkawa>
this one did not fortunately
<
javier__>
Tenkawa: exynos_defconfig should be a starting point but it does not have HDMI and the needed options for wifi enabled
<
Tenkawa>
s/versions/revisions rather
<
Wizzup>
Tenkawa: the chromeos ones had yeah
<
Tenkawa>
javier__: thats ok .. I'll add those in a piece at a time
<
Tenkawa>
I just want to get a baseline working then tune
<
Tenkawa>
i have some usb wireless cards to use if needed too
<
Tenkawa>
its compiling.. .now I wait
javier_ has joined #linux-exynos
<
Tenkawa>
this old cb1 still is pretty speed for compiling..
javier_ has quit [Client Quit]
liquidAcid has joined #linux-exynos
ssvb has joined #linux-exynos
<
Tenkawa>
ok re we go
<
Tenkawa>
wish me luck
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<
Tenkawa>
it boots...
<
Tenkawa>
blinks and no output though
<
Tenkawa>
the video output to the console has been my problem
<
Tenkawa>
am I possibly passing it the wrong console=?
javier_ has joined #linux-exynos
<
Tenkawa>
javier_: hey did you see my last msgs about the testing/
<
Tenkawa>
brb though... testing one more thing
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<
Tenkawa>
yeah.. just cannot get it to output to the internal display... seems to be fine otherwise
<
Tenkawa>
doesnt appear to be able to find any video hardware
<
Tenkawa>
brb.. going to cleanup some logs and get some data
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
javier__ has quit [Quit: Coyote finally caught me]
javier_ has quit [Quit: leaving]
javier__ has joined #linux-exynos
nashpa has quit [Ping timeout: 245 seconds]
<
si1v3r>
Linux-next booted on my peachpit with no tweakage at all.
<
Tenkawa>
can you post me your /proc/cmdline?
<
Tenkawa>
are you using simplefb nv-uboot?
<
Tenkawa>
I'm trying to avoid nv-ubooot
<
Tenkawa>
well darn...
<
Tenkawa>
si1v3r: any theories?
<
si1v3r>
Uh, I'm pretty sure simplefb is not required or desired anymore
<
si1v3r>
Since this latest kernel is supposed to have exynos drm code merged in
<
Tenkawa>
ok trying a diff tweak
<
Tenkawa>
si1v3r: oh..... i just noticed you said peachpit
<
Tenkawa>
i'm on snow
<
si1v3r>
Snow should work even better
<
Tenkawa>
I wonder if the devicetree needs a tweaj
<
Tenkawa>
it definitely seems to know its there
<
Tenkawa>
it just doesnt seem to direct the output properly
<
si1v3r>
I've been using nvuboot so I can do tweaks easier.
<
Tenkawa>
let me plug up my hdmi port and see if thats where it might be ahoving it
<
Tenkawa>
er shoving
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<
Tenkawa>
this thing hates me
<
Tenkawa>
now it wont boot from sd again.. even after re dd'ing the parts and resetting cgpt
<
Tenkawa>
immediately beeps..
Tenkawa has quit [Client Quit]
nashpa has joined #linux-exynos
afaerber has quit [Quit: Verlassend]
liquidAcid has quit [Quit: Leaving]