<Tenkawa>
so... what "is" the newest kernel any of you are running on a series 3 xe303c12 anyway?
<Wizzup>
I am running 4.1-rc4 on snow
<Wizzup>
Anything before 4.1-rcX will not work well
<Wizzup>
as you found out
<Tenkawa>
i need to figure out why i'm still getting white screen
<Wizzup>
Are you getting that on 4.1?
<Tenkawa>
let me give it a compile and try
<Tenkawa>
which dtb should I use?
<Wizzup>
Please just don't use 4.0 / report bugs about it
<Wizzup>
there is only one dts to use for snow...
<Tenkawa>
oh good
<Tenkawa>
there use to be multiple revs
<Wizzup>
only in chrome trees afaik...
<Tenkawa>
and it was annoying
<Tenkawa>
nod
<Tenkawa>
did you say exyos_defconfig was a starting point?
<Tenkawa>
er exynos
<Tenkawa>
btw do I "have" to use nv-uboot?
<Tenkawa>
I really am use to signing and writing directly to part
<Wizzup>
I don't know. I just copy over the uImage w/ dtb and boot that. Much easier than all the signing stuff
<Tenkawa>
the signing i have down to an art
<Tenkawa>
heheh
<Tenkawa>
ok.. compiling
<Wizzup>
it's still annoying and useless (@ signing)
<Tenkawa>
rc5
<Tenkawa>
btw
<Tenkawa>
Wizzup: well nv-uboot config files get annoying
<Tenkawa>
this is the great usage for the sd slot though :)
<Tenkawa>
just in case of oops
<Tenkawa>
wow this is still one slow internal emmc
<Tenkawa>
ok compile now has really started
<Tenkawa>
haahaa
<Tenkawa>
ok kernel compiled.. lets see if it works
<Tenkawa>
omg
<Tenkawa>
it worked
<Tenkawa>
no wifi
<Tenkawa>
oh.. firmware failed
<Tenkawa>
let me fix that
<javier__>
Tenkawa: you need to build the mwifiex driver as a module
<Tenkawa>
oh...
<Tenkawa>
no more buildin eh?
<Wizzup>
javier__: isn't it good enough to just enable the fw loader fallback?
<javier__>
Tenkawa: please keep notes of what people tell you, I have to repeat myself many times
<Wizzup>
I don't think I have it as a module, but I may be wrong
<Tenkawa>
javier__: i dont use a module on my older kernels
<Tenkawa>
the one i just was running ran fine with it static
<javier__>
Tenkawa: yes, another option is to have CONFIG_FW_LOADER_USER_HELPER enabled
<Tenkawa>
yes. i know that
<javier__>
but that is a deprecated option and udev will not support it in the future
<Tenkawa>
it was off.. fixing it now
<Tenkawa>
I prefer to use it.. my point is I knew what you said before.
<Tenkawa>
it "will" work and as long as supported i'm going to use it
<javier__>
ok
<Tenkawa>
modules are great to have avail however some of us want veru specific configs and it just adds overhead
<Wizzup>
eudev may support it for way longer
<Wizzup>
Tenkawa: well ... 'overhead'...
<Tenkawa>
Wizzup: codesize
<javier__>
the built-in firmware loading is a special case
<Wizzup>
in any case, you mean binary size
<Tenkawa>
Wizzup: to be wording correct yes
<javier__>
since it expects the firmware to be available when the driver is probed and the driver has no way to know that the fw loading failed
<javier__>
not a way to retry
<Tenkawa>
and it does add some complexity
<javier__>
so a third option is to have the fw in a initialram fs
<Tenkawa>
oh please no initfs
<Tenkawa>
those are so annoying
<javier__>
I'm just mentioning the options, you can use whatever you want
<Tenkawa>
none of my socs use them anymore after a lot of tuning
<Tenkawa>
javier__: granted
<Tenkawa>
i agree with your viewpoint. in general.. just stating my specific use case is not normal
<Tenkawa>
I'm a weirdo
<javier__>
Tenkawa: you can also built the fw in your kernel binary
<javier__>
that's a 4th option
<Tenkawa>
either way it goes.. thanks for encouraging me to try 4.1.. .i think its going to go nicely
<Tenkawa>
javier__: thats what I'm doing now
<Tenkawa>
I like having it in the bin
<Tenkawa>
especially if I have a lot of identical pieces of hardware
<Tenkawa>
(got 4 rasperry pi's doing that due to a usb device each has)
<Tenkawa>
makes it nice to build and transfer one kernel to all
gallit has joined #linux-exynos
<Tenkawa>
now if I could find a soc that I really like
<Tenkawa>
anyone know why mips fell out of linux popularity?
<Tenkawa>
(not that it was ever popular)
<Tenkawa>
ok kernel attempt #2
<Tenkawa>
perfect :)
<Tenkawa>
hrmm...
<Tenkawa>
except having trouble conmecting..
<Tenkawa>
er connecting
<Tenkawa>
hm bunch of invalid args... more debugging to do.. thanks all.. cheers
Tenkawa has left #linux-exynos [#linux-exynos]
zombah has quit [Quit: Leaving]
<si1v3r>
Compiling mwifiex_sdio as a module works just fine for me thanks. :) Too bad it's not a suitable default.
<javier__>
si1v3r: is still not clear to me how the built-in fw loader is supposed to work with built-in drivers
<javier__>
I think it was added as a consequence of udev deprecating the user space fw loader but was not thought completely
<si1v3r>
Shouldn't it be possible to declare the root filesystem as a dependancy for initializing a driver with a firmware?
<javier__>
si1v3r: how so? the rootfs is mounted very late in the boot process
<javier__>
and there isn't a way to declare that dependency
<si1v3r>
I'm thinking like a sysadmin, not a kernel hacker. ha
<javier__>
si1v3r: fair enough :)
<javier__>
there isn't a way to declare that
<javier__>
if you want the driver to be registered after the rootfs has been mounted, then the option is to build it as a module and load it from user-space
<si1v3r>
I'll google a bit.
<si1v3r>
http://stackoverflow.com/questions/11642330/linux-built-in-driver-load-order mentions that the linker sorts drivers into levels and loads in that order. Are FS and wifi drivers on different levels? It also mentions you can manipulate initialization order by moving a drivers position in the Makefile, which I'm assuming would be done in .config.
<javier__>
si1v3r: yes but you can't rely on link order
<javier__>
si1v3r: and no, you can't change that in the .config
<javier__>
the .config just says which files are going to be built and as a module or built-in the kernel binary
<si1v3r>
ah
liquidAcid has joined #linux-exynos
Tenkawa has joined #linux-exynos
<Tenkawa>
ok.. got one last hiccup
<Tenkawa>
everything else is working great
<Tenkawa>
sound....
<Tenkawa>
alsa has like 30+ controls but none seem like the right one/having any effect on volume
<Tenkawa>
do i need codecs defined in the kernel?
<Tenkawa>
i feel like i'm missing something very small
<Tenkawa>
everything else though is working great
<Tenkawa>
with 4.1-rc5
<Tenkawa>
brb
Tenkawa has quit [Quit: leaving]
Tenkawa has joined #linux-exynos
<Tenkawa>
wow I'm really tempted to pick up a chromebook 2 now
<si1v3r>
I did. I love it.
<si1v3r>
It fixed every problem I had with the snow.
<Tenkawa>
heheheeh
<si1v3r>
Sound is working for me in 4.1 as well.
<Tenkawa>
there is a 11" version right?
<si1v3r>
yeah I have that one.
<Tenkawa>
I like the form factor of this one
<Tenkawa>
cool
<Tenkawa>
I just really am pulled to arm boxes
<Tenkawa>
all of my boxes are arm except for 2
gallit has quit [Remote host closed the connection]
<si1v3r>
I've only got two working arms. My chumby died and I haven't got my odroid to boot yet.
<Tenkawa>
which odroid model?
<Tenkawa>
thought about one of those
<si1v3r>
origen quad
<si1v3r>
not a common one. Was a thrift find for $5.