ssvb has quit [Ping timeout: 265 seconds]
ssvb has joined #linux-exynos
Tenkawa has joined #linux-exynos
<Tenkawa> hi all
<Tenkawa> I'm back
<Tenkawa> now I got 2 computers to try to work on this boot
<si1v3r> That's helpful.
<Tenkawa> I can't seem to get boot.env/txt right
<si1v3r> Are your changes picked up at all?
<Tenkawa> is there a simple way to test boot a kernel in nv-uboot syntax
<si1v3r> qemu comes to mind
<Tenkawa> yes but I see old references too
<Tenkawa> oooh
<Tenkawa> should boot be an ext2 or msdos part btw?
<Tenkawa> getting a ton of fatload errors
<si1v3r> needs to be ext2 for snow
<Tenkawa> ahh
<si1v3r> scripts (p12) needs to be fat
<Tenkawa> hmmm
<Tenkawa> let me check
<Tenkawa> ok xe303c12 setup as chromeoskernel, ext2,ext4 parts
<Tenkawa> my boot scripts are all listing fatloads
<si1v3r> I used to have a snow. Have a peachpit now
<Tenkawa> I may not have a good boot script
<si1v3r> you don't need one at all
<si1v3r> do it manually. Take a picture, then try it.
<Tenkawa> if I dont it tries mmc0 instead of 1
<si1v3r> repeat until it boots
<Tenkawa> o
<Tenkawa> k
<si1v3r> I've got a pic of my setup on reddit somewhere but its blurry. :)
<Tenkawa> is there a list of the minimum steps needed to test?
<si1v3r> God I wish there was.
<Tenkawa> ie uboot commands
<Tenkawa> heheh
<Tenkawa> I'm worried my load addresses are all off too
<Tenkawa> no way to tell though
<Tenkawa> ok here goes attempt 4000
<Tenkawa> I feel like I'm so close
<Tenkawa> hmm typos in there somewhere
<Tenkawa> syntax errors
<si1v3r> its 40800 I think
<Tenkawa> and a lot of wrong image format for bootm
<si1v3r> 400800
<si1v3r> yeah that means bad jump I bet
<si1v3r> the load addr is listed in the uimage options
<Tenkawa> hehehe
<Tenkawa> mine is trying to load zimage only// no uimage
liquidAcid has quit [Quit: Leaving]
<si1v3r> I was only able to boot by making with
<si1v3r> LOADADDR=0x400800 make uImage modules
<si1v3r> if I recal last august right
<Tenkawa> ok
<Tenkawa> let me take a looik
<Tenkawa> er look
<si1v3r> then I grabbed the uimage from arch/arm/uImage and the dtb from arch/arm/dtbs/exynos something
<Tenkawa> running
<si1v3r> notably the kernel outputs a "uImage" file, and u-boot wants vmlinux.uimg
<Tenkawa> this will take a while
<Tenkawa> hmm mine tries grabbing zImage
<Tenkawa> I'll make sure I copy vmlinux.uimg
<Tenkawa> ok
<Tenkawa> done.. copying
<Tenkawa> lets see what happens
<Tenkawa> hmm
<si1v3r> We need a nice screenshots section in the wiki. heh
<Tenkawa> indeed
<Wizzup> that too, as well as pictures of the devices
<Tenkawa> doh
<Tenkawa> it may have been loading bad stuff
* Wizzup is going to try to get it up to shape before fosdem :)
<Tenkawa> I will be so thrilled if I get this going
<si1v3r> Wizzup: let me know what you need help with.
<Tenkawa> can this be done with a zImage only or does it need a uImage
<Tenkawa> hmmm
<Wizzup> si1v3r: ack, right now I just need to sleep and I doubt anyone can help me with that ;)
<Wizzup> Tenkawa: typically, without proper context right now, uImage
<Tenkawa> ok
<Tenkawa> I think these settings may be for a diff model.. let me check
<Tenkawa> these look like the wrong addresses
<Tenkawa> and they are the ones on linux-exynos.org in the u-boot environment page
<Tenkawa> is that possibly for a diff model
<Tenkawa> ?
<Tenkawa> oh hoh
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-exynos
<Tenkawa> now I see one big problem
<Tenkawa> bad typo
<Tenkawa> ugghg
<Tenkawa> I'm so close
<tyler-baker> Tenkawa, if you want to compare load addr's you can have a look here: http://kernelci.org/boot/?peach
<Tenkawa> that applicable for snow too?
<tyler-baker> Tenkawa, I have one for snow too, http://kernelci.org/boot/?snow
<Tenkawa> thanks
<Tenkawa> let me take a look
<tyler-baker> Tenkawa, if you click a the magnifying glass by a specific build, it will show you the details you may want to compare
<tyler-baker> Tenkawa, also there are logs attached with uboot configs etc
<Tenkawa> no graphics here
<Tenkawa> I hate it when I know I'm so close...
<tyler-baker> :)
<Tenkawa> anyone got the precompiled .its file handy?
<tyler-baker> I'm not familiar with an .its file do you mean .dtb?
<Tenkawa> no its the signed image file
<tyler-baker> ah ok
<Tenkawa> def
<Tenkawa> I just need to get a simple boot env file to import than uses mmc1
<Tenkawa> then I'd be set I do think
<tyler-baker> I can pull my files, one second
<Tenkawa> thanks
<tyler-baker> waiting for my kvm guest to shutdown, don't have the vfat driver enabled in the kernel..
<Tenkawa> ahh\
<Tenkawa> found a typo
<Tenkawa> ugggj
<Tenkawa> uggh
<Tenkawa> didnt see it when I imported this file
<Tenkawa> thanks.. let me grab that
<tyler-baker> alright I'm signing off for the night, gl
<Tenkawa> cheers
<tyler-baker> cheers
Tenkawa has quit [Quit: leaving]
James_T has quit [Ping timeout: 265 seconds]
James_T has joined #linux-exynos
James_T has quit [Remote host closed the connection]
James_T has joined #linux-exynos
James_T has quit [Ping timeout: 244 seconds]
James_T has joined #linux-exynos
D1337d has quit [Ping timeout: 245 seconds]
libv has quit [Ping timeout: 240 seconds]
libv has joined #linux-exynos
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-exynos
amitk has joined #linux-exynos
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-exynos
James_T has quit [Quit: Ohh Noes i dieded :'(]
D1337d has joined #linux-exynos
James_T has joined #linux-exynos
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-exynos
dlezcano has quit [Ping timeout: 265 seconds]
dlezcano has joined #linux-exynos
dlezcano has quit [Ping timeout: 244 seconds]
daniels has quit [Ping timeout: 250 seconds]
daniels has joined #linux-exynos
dlezcano has joined #linux-exynos
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-exynos
Nemykal has quit [Ping timeout: 244 seconds]
Nemykal has joined #linux-exynos
prometheanfire has quit [Ping timeout: 245 seconds]
James_T has quit [Ping timeout: 255 seconds]
James_T has joined #linux-exynos
daniels has quit [Read error: Connection reset by peer]
daniels has joined #linux-exynos
James_T has quit [Ping timeout: 244 seconds]
James_T has joined #linux-exynos
dlezcano has quit [Remote host closed the connection]
Tenkawa has joined #linux-exynos
<Tenkawa> hi ll
<Tenkawa> anyone awake yet?
<Tenkawa> I made some progress
<Tenkawa> nw the kernel just panics
<Tenkawa> (or never finished booting) last line is/l
<Tenkawa> er :
<Tenkawa> Stashed 20 records
<Tenkawa> might just be a bad kernel config
<Tenkawa> building a new one now
<Tenkawa> anyone got a known good .config?
<javier__> Tenkawa: what is your device and which tree and branch are you using?
<Tenkawa> snow chromebook xe303c12 3.14.0
<javier__> why 3.14.0?
<Tenkawa> was starting with the one on the webpage
<Tenkawa> got a recommendation?
<javier__> Tenkawa: yes, 3.18 + my topic branches
<Tenkawa> oh
<Tenkawa> i'm checking /topic and all I see is Wizzup's
<javier__> branches wip/exynos/dp-integ and wip/exynos/wifi from git://cgit.collabora.com/git/user/javier/linux.git will give your working display and wifi
<Tenkawa> oh sweet
<Tenkawa> you got a defconfig in there too?
<javier__> sorry I meant git://git.collabora.co.uk/git/user/javier/linux.git
<javier__> yes, exynos_defconfig
<Tenkawa> nice
<Tenkawa> ok let me try that out
<Tenkawa> got 2 computers out which makes this a lot easier
<Tenkawa> cloning now
<Tenkawa> (git)
<Tenkawa> javier__: any gotchas to watch for?
<javier__> not really, it should just work
<Tenkawa> sweet
<Tenkawa> I so want to try out something newer than 3.8 on this box
<Tenkawa> I really use this a lot
<Tenkawa> I'm also working on getting linux support working in a Winbook TW100
<Tenkawa> Intel Baytrail with the efi bug :(
<Tenkawa> otherwise it would run fine
<Tenkawa> only got 9% of the files so far :(
<Tenkawa> heheh
dlezcano has joined #linux-exynos
dlezcano has quit [Ping timeout: 245 seconds]
dlezcano has joined #linux-exynos
dlezcano has quit [Ping timeout: 245 seconds]
<Tenkawa> javier__: this is not a great speed day for my connection
<Tenkawa> or the collabora one
<Tenkawa> one of them heeehee
dlezcano has joined #linux-exynos
<javier__> don't know tbh, I've a good data transfer rate here :)
<Tenkawa> yeah I'm in usa
<Tenkawa> heh
<Tenkawa> got 358 mb transferred so far
indy_ has joined #linux-exynos
indy has quit [Excess Flood]
indy_ is now known as indy
dlezcano has quit [Ping timeout: 244 seconds]
dlezcano has joined #linux-exynos
<Tenkawa> still pulling
<Tenkawa> less than 100mb to go I think
<Tenkawa> or something close
<Tenkawa> whoah
<Tenkawa> speed majorly picked up
<Tenkawa> yay
<Tenkawa> delta changing
<Tenkawa> fun fun
<Tenkawa> er checking
dlezcano has quit [Ping timeout: 255 seconds]
dlezcano has joined #linux-exynos
<Tenkawa> building now
<Tenkawa> ummm
<Tenkawa> whats the git checkout tag I need to use?
<Tenkawa> it comes out as 3.14.0-rc2 default for me
<Tenkawa> git --tag doesnt list 3.18 in there
<Tenkawa> unless I did something bad wrong
<Wizzup> git checkout -t origin/dp-integ
<Tenkawa> ok let me try that
<Tenkawa> not happy about that at all
<Wizzup> ?
<Tenkawa> let me get the output
<Tenkawa> I shoudve cloned via git clone git://git.collabora.co.uk/git/user/javier/linux.git or did I completely mess it up
<Tenkawa> no branches listed in my repo either
<sjoerd> what does git branch -r tell you ?
<Tenkawa> ahh haaa
<Tenkawa> its origin/ip/exynos/.....
<Tenkawa> r wip
<Tenkawa> ok thats looking a lot better
<Tenkawa> sjoerd: thanks
<Tenkawa> bit rusty on git
<Tenkawa> its checking out the changes now
<sjoerd> normally git would figure out it needs it from the remote
afaerber has joined #linux-exynos
<Tenkawa> weird
<Tenkawa> sjoerd: well at least now its going :)
dlezcano has quit [Ping timeout: 252 seconds]
<Tenkawa> reminds me of my source code control admin days in the early 90
<Tenkawa> 's
<Tenkawa> ooh that looks a lot better
<Tenkawa> build time
<javier__> Tenkawa: I haven't updated the master branch in my remote for a while
<Tenkawa> ahhh
<javier__> Tenkawa: that's why I told you the branches you had to checkout :)
<Tenkawa> DOH
<Tenkawa> it got blocked out by server messages
<Tenkawa> in my scrollback
<Tenkawa> my apologies
<javier__> Tenkawa: git clone -b $foo git://.. would had made the trick
<Tenkawa> i didnt see the wip at all until I looked at my chan log
<javier__> but I usually just do git remote add foo git://foo & git remote update foo
<Tenkawa> uggh
<Tenkawa> I hate when it does that visual override
<Tenkawa> my bad
<Tenkawa> Its compiling now :)
<javier__> cool
<javier__> gotta leave for today, bye!
<Tenkawa> this is going to be so cool if it works
<Tenkawa> cheers. thanks again for all the help
dlezcano has joined #linux-exynos
afaerber_ has joined #linux-exynos
amitk has quit [Quit: leaving]
<Tenkawa> anyone know what loadaddr I should use offhand for the build?
<Tenkawa> I think its 0x400800 (at least thats what i have
afaerber has quit [Ping timeout: 252 seconds]
<Tenkawa> here we go
<Tenkawa> lets see if it will boot
<si1v3r> good luck!
<Tenkawa> it starts kernel then appears to have same panic/hang
<si1v3r> can't mount root?
<Tenkawa> letI dont get to the kernel even yet.. let me make sure my dtb is updated
<Tenkawa> well thats "closer"
<Tenkawa> it loads up the uImage then reboots
<Tenkawa> never does hit the kernel though
<Tenkawa> hmm
<Tenkawa> I wonder if my boot cmdline is wrong
<Tenkawa> anyone got an example handy?
<si1v3r> Mine should be on the wiki
<Tenkawa> let me take a look
<Tenkawa> darn.. just resets
<Tenkawa> let me take out the bootargs and see if I can get it to panic
<Tenkawa> i see it flash by the device tree then it reboots
<Tenkawa> i see it flash by the device tree then it reboots
<Tenkawa> oops
<Tenkawa> si1v3r: I should be using the uImage even with nv-uboot right
<Tenkawa> ?
<si1v3r> uimage for uboot
<si1v3r> yes
<Tenkawa> it seems the devicetree changes what it does
<si1v3r> yes that's the attempt at using one kernel for more than one device
<Tenkawa> I wonder If I'm using the wrong one
<si1v3r> it's built at the same time as the kernel
<Tenkawa> yeah
<Tenkawa> that appears to match up
<si1v3r> brb
<Tenkawa> its going to be something tiny
<Tenkawa> I can almost gurantee
<Tenkawa> so close to reading what it says
<Tenkawa> let me see if I vid it
<Tenkawa> er I can
<Tenkawa> got it!!
<Tenkawa> failed to add board information to fdt: fdt_err_notfound
<Tenkawa> fdt_system_setup() failed before
<Tenkawa> wow thats awesom
<Tenkawa> cantb believe this camera grabbed it quick enough
<Tenkawa> now to troubleshoot
<Tenkawa> probably got an address wrong
jnettlet97 has joined #linux-exynos
jnettlet97 has quit [Remote host closed the connection]
jnettlet has quit [Remote host closed the connection]
jnettlet has joined #linux-exynos
jnettlet has quit [Remote host closed the connection]
jnettlet has joined #linux-exynos
<Tenkawa> darnit
<Tenkawa> i wish I could igure out why fdt is erroring
<Tenkawa> I feel like I'm so close
<Tenkawa> does it matter I'm not fatloading any of this and doing it all with ext2load?
<Tenkawa> oooh
<Tenkawa> I think I might know why
<Tenkawa> maybe not :9
<Tenkawa> thought my dtb may have been skewed
<Tenkawa> hmmmmm
<si1v3r> Is there an error on the screen when it fails?
<Tenkawa> tI typed it above
liquidAcid has joined #linux-exynos
<Tenkawa> that FDT one
<Tenkawa> it reboots immeditely
<Tenkawa> I had to photo that
<si1v3r> gotcha
<Tenkawa> I got a feeling I'm so close.....
<si1v3r> Are you doing two ex2loads and a bootm?
<Tenkawa> yes
<si1v3r> you might want to run mkimage on your kernel image and see if it has the dtb built in
<Tenkawa> I just did
<si1v3r> are you loading the dtb to 400000
<si1v3r> ?
<Tenkawa> got the same stating kernel then bunch of timer summary then accumjulated time finally stashed 21 records
<Tenkawa> no
<Tenkawa> 00400800
<Tenkawa> I was wondering about that too
<si1v3r> 400800 is for the kernel
<si1v3r> the dtb is loaded to another address
<Tenkawa> right
<Tenkawa> just a sec
<Tenkawa> let me check what they are set to
<Tenkawa> I got rid of the dtb error
<Tenkawa> by making a vmlinux.uimg with mkimage
<Tenkawa> now it boots up to that old panic
<Tenkawa> o
<Tenkawa> k
<Tenkawa> dt - 0x43000000
<Tenkawa> fdtaddr - bda3dbdc
<Tenkawa> need any more
<Tenkawa> ?
<si1v3r> those look wrong to me
<si1v3r> but I can't get to my notes at the moment
<Tenkawa> well darn
<Tenkawa> ok.. let me google a bit
<Tenkawa> hmmmmmm
<Tenkawa> just a sec
<Tenkawa> minimally ftaddr appeared to not match up
<si1v3r> I don't think the actual value is important as long as it's in the right range and is consistant.
<Tenkawa> I think its my loadaddr
liquidAcid has quit [Read error: Connection reset by peer]
<Tenkawa> if I move it I can switch the behaviour
<Tenkawa> uggh
<si1v3r> you only have 3 moving parts, so it's not impossible
<Tenkawa> I just wish I could explain this weird error
<si1v3r> link a picture
<Tenkawa> nothing to send it with
<Tenkawa> long story
<javier__> Tenkawa: can you please share your u-boot bootcmd and the command you are using to create the uImage?
<Tenkawa> sure
<Tenkawa> let me type them out
<Tenkawa> mkimage -A arm -O linux -T script -C none -d boot.scr boot.scr.uimg
<Tenkawa> boot.scr:
<Tenkawa> setenv bootargs 'cros_legacy console=tty1 console=ttySAC3,115200 debug earlyprintk ignore_loglevel oops=panic panic=30 root=/dev/mmcblk1p3 rootwait rw init=/sbin/init fbcon=scrollback:512k'
<Tenkawa> ext2load mmc 1:2 ${loadaddr} /vmlinux.uimg
<Tenkawa> bootm ${loadaddr}
<Tenkawa> thats all
<Tenkawa> the image loads
<Tenkawa> starting kernel... then boom
<Tenkawa> at least it does reflect 3.18
<javier__> you pasted the command that you are using to generate your boot.scr, not your uImage...
<Tenkawa> I'm using make uImage in the kernel source.. oh
<Tenkawa> just a sec
<Tenkawa> got to reboot
<Tenkawa> thank goodness for fast booting
<javier__> Tenkawa: the problem you have is because you are not passing a device tree to the kernel
<si1v3r> I had my tweak/compile/reboot loop time down to 15 minutes in september or so. heh
<Tenkawa> LOADADDR=0x400800 make uImage modules dtbs
<si1v3r> javier__: yes he either needs loadaddrs for uboot or a working script for a fit image.
<Tenkawa> that provide any insight?
<javier__> si1v3r: well, he can use a FIT but for u-boot he needs to either load a FDT and pass the address to bootm or use an appended DTB
<Tenkawa> I'm willing to try any experimemtd
<si1v3r> found my notes
<Tenkawa> ooh... time to read
<javier__> Tenkawa: what I said, you need to load a device tree from your media and pass it to bootm or append the DTB to the zImage and then generate the uImage
LanDi has joined #linux-exynos
<Tenkawa> Ahhhh
<javier__> Tenkawa: you have also to check the value of your ${loadaddr} u-boot env var and be sure that the address to load the FDT makes sense
<Tenkawa> so do the cat dtb >>zImage trick then generate a new uImage?
<javier__> yes, that's an option if you don't want to change your current u-boot commands
<Tenkawa> ok
<javier__> the exynos_defconfig has all the needed kconfig symbols enabled to make that work
<Tenkawa> let me try it... ifit works I'll make the nvram changes
<javier__> Tenkawa: you can't build the uImage with make though since you need that intermediate step so build a zImage, append and then generate the uImage with mkimage
<javier__> passing your load and entry point address as mkimage arguments
<Tenkawa> yep
<Tenkawa> got it
liquidAcid has joined #linux-exynos
<Tenkawa> trying .....
<Tenkawa> fdt and efi are not my friends
<si1v3r> 100% different beasts.
<si1v3r> by completely different flavors of idiots....
<Tenkawa> no no.. i mean just in general
<Tenkawa> ok here goes the next test
<Tenkawa> nope
<Tenkawa> let me try to add the fdt to the boot line
<Tenkawa> Think I found it!!
<Tenkawa> loadaddr typo
<Tenkawa> omg i hope this is it
<Tenkawa> should it be 0x400800 or 0x40008000?
<Tenkawa> I assume this matters
<si1v3r> super important
<Tenkawa> would explain my load problem
<Tenkawa> omg I think this is it
<Tenkawa> find out shortly
<si1v3r> great success?
<Tenkawa> sstill recombining dts/kernek
<Tenkawa> er l
<Tenkawa> is 0x40008000 the right value?
<si1v3r> was for me but I didn't combine
<Tenkawa> a
<Tenkawa> h\
LanDi has quit [Remote host closed the connection]
<Tenkawa> YSY!!!!!
<Tenkawa> WOOOHOOOOOOOO
<Tenkawa> SUCCESS!!
<Tenkawa> (sorry)
<Tenkawa> that missing 0
<Tenkawa> 2 0's was the whole problem
<Wizzup> awesome!
<si1v3r> shoopdewhoop
<Tenkawa> sorry... I'm really excited
<Tenkawa> now I can do some heavy kernel work
<si1v3r> dude. totally.
<Tenkawa> I am so sorry i missed that there was a 0 missing
<si1v3r> worry about buggin javier not me. heh
<si1v3r> he's the kernel dev
* Wizzup is going to do snow tonight as well
<Tenkawa> javier__: thank you
<Tenkawa> javier__: thank you
<Wizzup> hopefully ;)
<si1v3r> i just play with penguins and make giggly sounds.
* si1v3r repos ubuntu installer issues for werk
<Tenkawa> I really wanted to get this box back to being able to do hardware work
<Tenkawa> I just can't believe 2 0's
<Tenkawa> thats all it was
<Tenkawa> uggh
<Wizzup> write down your steps :)
<Tenkawa> haahaa I will try
<Tenkawa> I am not committing anything to mmc and nvram yet so I should be able to
<si1v3r> No scroll back, copy them, strip the crap, paste somewhere. :D
<si1v3r> holy. crap. If you attempt to manually install ANY package at 14.04 server install time, it dies.
<javier__> Tenkawa: glad that you go it working
<Tenkawa> now I need to tune this kernel some (wifi is currently missing)
<javier__> Tenkawa: if you cherry-pick the first patches of my wip/exynos/wifi, you should get wifi working on snow
<Tenkawa> ok
<Tenkawa> switching it to use faster storage for root
<Tenkawa> thats better
<Tenkawa> much better :)
<Wizzup> (p.s. if you document it, you can initially start under a user page on the wiki0
<Wizzup> wiki)
<Tenkawa> ok. lets see if I can find these wifi patches
<Tenkawa> since I have 0 connectivity atm
<si1v3r> I used a usb wifi stick the whole time. :/
<si1v3r> it was aweful.
<Tenkawa> I've got 4 sitting around.. might just do that too
<Tenkawa> until I get comfortable
<si1v3r> Backups and snapshots.
<Tenkawa> yeah yeah.. heehee
<si1v3r> I moved old kernels out of the way and datestamped their names so I could roll back easily.
<Tenkawa> what was that git command to pull in the wifi branch?
<si1v3r> git merge?
<Tenkawa> ah
<Wizzup> I think he suggested cherry pick
<si1v3r> (I think)
<Tenkawa> oh so pull them somewhere else and trial and error.. ok
<Tenkawa> better hook up my usb dongle for now
<Wizzup> no, it's quite simple, but only if you know some git-fu :)
<si1v3r> did you compile the module for your dongle? hehe
<Tenkawa> no.. getting ready to
<Tenkawa> building modules now
<Tenkawa> this is already more fun
<Tenkawa> yes I know.. I'm a geek
<Tenkawa> modules dont need a loadaddr right?
<si1v3r> no
<si1v3r> they are not loaded raw like that
<Tenkawa> ok good
<Tenkawa> feeling jittery
<Tenkawa> symbol errrs related to ewma
<Tenkawa> I'll fix by hand for now
<javier__> Wizzup: yes, the wifi patches have to be cherry-picked since the branches don't have the same base...
<Wizzup> Yep, I got that :)
<Tenkawa> si1v3r: did you add references for the ewma functions that were missing?
<javier__> tbh, these branches are mostly for my personal use/dev, I should get some time to create an integration tree for others to use
<si1v3r> Tenkawa: I did not modify source.
<Tenkawa> odd
<Tenkawa> oh I know why
<Tenkawa> nm
<Wizzup> javier__: yes, would be cool, I could perhaps do that on github as well, but my spare time is quite variadic
<si1v3r> Used torvalds plain jane latest and only messed around in menuconfig
<Tenkawa> haahaa
<Tenkawa> darn module dependecies
<Tenkawa> er dependencies
<Tenkawa> oh this is nice
<Tenkawa> and I run in console mode only so no graphics stuff to fix
<Tenkawa> yay
<Wizzup> Do you have a /dev/fb0?
<Tenkawa> yeppers
<Wizzup> or does kms actually work?
<Wizzup> slash modesetting
<Tenkawa> I'm also setting fbcon at boot though
<Tenkawa> if that matters
<Tenkawa> well my module is running
<Tenkawa> not connecting very well yet
<Tenkawa> rather at all
<Tenkawa> oops
<si1v3r> cfg80211?
<Tenkawa> yeah thats what I'm thinking too
<si1v3r> It's required for ifconfig to work
<si1v3r> might be for other stuff
<si1v3r> *iwconfig
<Tenkawa> no wireless extensions
<Tenkawa> well darn
<Tenkawa> this is the part I like tweaking though
<Tenkawa> heheh
<Tenkawa> going to reduce my kernel size a bit first
<Tenkawa> "maybe"
<si1v3r> make it work then make it right
<Tenkawa> yep
<Tenkawa> woops
<Tenkawa> missed that selection
<Tenkawa> for extensions
<Tenkawa> oops
<Tenkawa> if I get it stable enough I'll be moving to it for my irc chta
<Tenkawa> uggh chat
<Tenkawa> thanks for all the help.. bbl possibly
<Tenkawa> cheers
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<Tenkawa> woohoo!!!!
<Tenkawa> wireless up and running
<Tenkawa> now its time for fun
<Tenkawa> I have scripts in place now to easily redo my boot usb
<Tenkawa> wow this thing feels faster
<Wizzup> :)
<si1v3r> stock kernel is a dog
<si1v3r> Tenkawa: I have some stuff in github that may help you.
<si1v3r> No working scripts, but lots of useful snips.
<Tenkawa> I'm going to start tuning now
<Tenkawa> time to shrink this kernel a bit
<Wizzup> si1v3r: no it's not @ gentoo ;)
<Tenkawa> so far this is nice....
<Wizzup> do you have a wiki acc?
<Tenkawa> not yet
<Wizzup> I can create one if you like (normal reg disabled b/c of spam)
<Tenkawa> Let me review my notes and I'll contact you all tomorrow
<Wizzup> (there's more people who got it to work, btw)
<Tenkawa> I want to try a few more things from scratch tonight to try to clean up the process
<si1v3r> sweeet
<si1v3r> https://github.com/5ilver has some crap I wrote for snow
<Tenkawa> someone should build a stock image for testing
<si1v3r> all we care about is testing new kernels. :D
<Wizzup> Tenkawa: yes!
<Wizzup> I am planning to create some binaries
<Tenkawa> ahh
<Wizzup> like we have for u-boot
<Tenkawa> interesting
<Wizzup> Swabbles: do you recall the place of the dl links? ;)
<Tenkawa> finding a gcc internal bug
<Tenkawa> in vt_ioctl.c
<Tenkawa> intriguing
<Tenkawa> heh made a one bit change and it compiled
Tenkawa has quit [Quit: Lost terminal]
<si1v3r> I bumped into that same thing and couldn't fix it...
<si1v3r> I just recompiled until it worked.
Tenkawa has joined #linux-exynos
<Tenkawa> almost got my kernel tuned down
<Tenkawa> ok time to really get risky
<si1v3r> ...put.... put doom in it......
<Tenkawa> haaahaa
Tenkawa has quit [Quit: Lost terminal]
<Wizzup> so that's yet another one having snow mainline running without documenting it :)
<Wizzup> at least for now
* Wizzup is building a kernel now
<Wizzup> see how far I'll get
liquidAcid has quit [Quit: Leaving]